ebu / ebucoreplus

Maintenance and development of the EBUCorePlus
MIT License
23 stars 6 forks source link

Labeling inconsistencies for object properties #286

Open alexander-schulze opened 8 months ago

alexander-schulze commented 8 months ago

The object property “hasProgramme” has a label “has programme”. Most of the other object properties have short names (see examples below). For consistency reasons, I expected a label “Programme” here, for instance, like for most of the other labels in EBUCorePlus.

These are some examples of some other object properties with an inconsistent labeling:

grafik

These are some examples of other properties with short names:

grafik
alexander-schulze commented 7 months ago

Dear EBU Colleagues, according to the naming conventions, I propose the following refactoring:

has agent => Agent has alternative title => Alternative title has article => Article has audience => Audience has clip = Clip has consumption count => Consumption count has device => Device has member => (SKOS) has member list => (SKOS) has parent editorial segment => Parent editorial segment has post => Post has programme => Programme has promotion => Promotion has publication channel => Publication channel has serial => Serial Has target channel => Target channel Has target service => Target service has top concept => (SKOS) Has TRS => TRS hasGroupMember => Group Member (as of 2023-11-16 no labels and comments)

Open for discussion. Alex

aro-max commented 2 months ago

Thank you Alex, is this list of changes exhaustive ?

[has agent](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasAgent.html)
[has alternative title](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasAlternativeTitle.html)
[has article](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasArticle.html)
[has audience](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasAudience.html)
[has broader](https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_broader.html)
[has broader match](https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_broadMatch.html)
[has broader transitive](https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_broaderTransitive.html)
[has clip](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasClip.html)
[has close match](https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_closeMatch.html)
[has consumption count](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasConsumptionCount.html)
[has device](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasDevice.html)
[has editorial group](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasEditorialGroup.html)
[has editorial work](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasEditorialWork.html)
[has exact match](https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_exactMatch.html)
[has member](https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_member.html)
[has member list](https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_memberList.html)
[has narrower](https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_narrower.html)
[has narrower match](https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_narrowMatch.html)
[has narrower transitive](https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_narrowerTransitive.html)
[has parent editorial segment](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasParentEditorialSegment.html)
[has post](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasPost.html)
[has programme](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasProgramme.html)
[has promotion](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasPromotion.html)
[has publication channel](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasPublicationChannel.html)
[has related](https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_related.html)
[has related match](https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_relatedMatch.html)
[has scene](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasScene.html)
[has serial](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasSerial.html)
[has shot](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasShot.html)
[has take](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasTake.html)
[has top concept](https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_hasTopConcept.html)
[Has TRS](https://www.ebu.ch/metadata/ontologies/ebucoreplus/time_hasTRS.html)

These labels should also be renamed : 

[ec:duration](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_duration.html) = > Duration
[ec:end](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_end.html) = > End 
[ec:hasGroupMember](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_hasGroupMember.html) => Group member 
[ec:loggsPublicationEvent](https://www.ebu.ch/metadata/ontologies/ebucoreplus/ec_loggsPublicationEvent.html) = > ?
alexander-schulze commented 2 months ago

Regarding the local names using prefixes you propose: has agent has alternative title

The namespace is already defined by the IRI and would be redundant by such a change. Following the standard, it should be

[has alternative title] https://www.ebu.ch/metadata/ontologies/ebucoreplus#hasAlternativeTitle.html

The SKOS the W3C time ontology have their own individual namespaces. These were not planned to be touched at all, since this would break interoperability. [has top concept] (https://www.ebu.ch/metadata/ontologies/ebucoreplus/skos_hasTopConcept.html) is supposed to be kept as http://www.w3.org/2004/02/skos/core#hasTopConcept (as standardized here: https://www.w3.org/2009/08/skos-reference/skos.html)

From my perspective, we can set this issue to obsolete, since it will be covered completely by #299.

aro-max commented 2 months ago

The list I copy past is not a proposal but the actual naming. My point is that you should list the names of all the properties like "has agent" to rename.

JuergenGrupp commented 2 months ago

This issue is not fully covered by #299. There we are correcting the IRIs. Here we need to correct the labels. We agreed on May 6 to correct the labels after correcting the IRIs and do that in a separate pull request.