-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Requirement for label / prefLabel? #31
Comments
Fallback display label is 👍 from @hybox/drs-team |
I'm of the opinion that PCDM Works should require an rdfs:label for everything, for interop. |
I think requiring a label is good, but I'm not sure how to handle all the different predicates that might be used. Do we require rdfs:label? Or is there a set of predicates (rdfs:label, skos:prefLabel, dc:title, etc.) that are acceptable? |
To confirm, every resource needs a label. Including things like FileSet and Identifier. I'm happy with that if it's the decision ... I'd like to confirm that this was made with an understanding of the scope :) I would prefer to pick one and stick with it. As such, rdfs:label to me is the easiest. |
Backtracking ... for Concepts having a MUST for rdfs:label rather than prefLabel seems ludicrous. And once the door is open, then we might as well allow it elsewhere. MUST have at least one of rdfs:label, skos:prefLabel, dc:title ... in that order of preference? |
It seems that there's some fundamental choices to be made around labels for resources. Notably
In particular:
The text was updated successfully, but these errors were encountered: