Skip to content
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

Open
1 of 2 tasks
azaroth42 opened this issue Mar 23, 2016 · 5 comments
Open
1 of 2 tasks

Requirement for label / prefLabel? #31

azaroth42 opened this issue Mar 23, 2016 · 5 comments

Comments

@azaroth42
Copy link
Contributor

It seems that there's some fundamental choices to be made around labels for resources. Notably

In particular:

  • MUST every resource have a label? --> yes
  • Do we use rdfs:label or skos:prefLabel/skos:altLabel? or some set?
@no-reply
Copy link

Fallback display label is 👍 from @hybox/drs-team

@tpendragon
Copy link

I'm of the opinion that PCDM Works should require an rdfs:label for everything, for interop.

@escowles
Copy link

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?

@azaroth42
Copy link
Contributor Author

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.

@azaroth42
Copy link
Contributor Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants