Requirement for label / prefLabel?

hybox / models

Data Modeling repository for HyBox (ontologies, vocabularies, best practices, requirements, etc)

Apache License 2.0

5 stars 3 forks source link

Requirement for label / prefLabel? #31

Open azaroth42 opened 8 years ago

azaroth42 commented 8 years ago

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

In particular:

[x] MUST every resource have a label? --> yes
[ ] Do we use rdfs:label or skos:prefLabel/skos:altLabel? or some set?

no-reply commented 8 years ago

Fallback display label is :+1: from @hybox/drs-team

tpendragon commented 8 years ago

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

escowles commented 8 years ago

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 commented 8 years ago

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 commented 8 years ago

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?