search

SEMICeu / style-guide

SEMIC style guide to create reusable vocabularies and application profiles
https://semiceu.github.io/style-guide/
Creative Commons Attribution 4.0 International
9 stars 2 forks source link

rdfs:label vs skos:prefLabel #20

Closed skodapetr closed 1 year ago

skodapetr commented 1 year ago

This one is more of a developer concern. Quote In OWL, - the original label is adopted as is (e.g. either rdfs:label or skos:prefLabel)

In OWL, - the original label is adopted as is (e.g. either rdfs:label or skos:prefLabel) - 
the new label is added as an alternative label (e.g. skos:altLabel)

Imagine situation when using the OWL I would like to generate a visual for a user. As I see it I have to check for both original labels (rdfs:label and skos:prefLabel). In addition which one should I chose when both would be available? Is there a benefit to have two label predicate for class in lightweight-ontology?

I know this may not be a concern from data modeling standpoint, yet it can be for a developer that has to work with the lightweight-ontology.

costezki commented 1 year ago

This depends on your use case. You shall make a decision on which label to give higher preference and document it clearly.

We stipulate it in the lexicalisation section: https://semiceu.github.io/style-guide/public-review/gc-semantic-conventions.html#sec:sc-r3

This sort of situations (where multiple redundant properties occur) may happen not only with label properties.