search

ebu / ebucoreplus

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

Range for "hasBeenAwarded" is wrong #276

Open JuergenGrupp opened 12 months ago

JuergenGrupp commented 12 months ago

The object property hasBeenAwarded has as its range Award and Agent. More strangely, the second case has also Agent as its domain, stating that "an agent has been awarded and agent". Two statements are probably intended:

  1. an award has been awarded to an agent
  2. an agent has been awarded with an award

My suggestion is to split the property into two separate, but inverse object properties:

  1. Award hasBeenAwardedTo Agent
  2. Agent hasBeenAwardedWith Award
tormodv commented 11 months ago

Yes, a good proposal.

JuergenGrupp commented 2 months ago

Following our new naming conventions, I will split the properties into: Award isAwardedTo Agent Agent isAwardedWith Award

JuergenGrupp commented 2 months ago

Another improvement for disambiguation: instead of isAwardedWith I will use holdsAward

JuergenGrupp commented 2 months ago

And another improvement: holdsAward is the inverse of isAwardedTo

JuergenGrupp commented 2 months ago

EditorialCommittee, May 6: should we rather use: isHeldBy instead of isAwardedTo? This opens the question, whether the naming should support building of SPARQL-requests or should it mainly support easy understanding. Rethink, whether "isHeldBy" might be a super-property for "isAwardedTo". But property hierarchies need to be designed carefully. Super properties are most helpful when the linked concepts are also in a hierarchy. Also: more precise properties are more efficient in terms of Queries. How about using "awards" or "praise"? "wins"<->"isWonBy" or "holds"<->"isHeldBy". Could also express nominations: "isNominatedFor"<->"nominates" ? Looks like "holdsAward"<->"isAwardedTo" is still the best option in terms of easy understanding, even if the rules are not met perfectly.