299 refactoring renaming property cluster 01
This pull request includes the renaming of ten object properties.
appliesOutOftohasTerritoryExcludesappliesTotohasTerritoryIncludesapplyTotohasTerritoryIncludesclonedTotohasCloneisClonedFromtoisCloneOfdubbedTotohasDubisDubbedFromtoisDubOfisCoveredBytohasRightsisAgenttohasRelatedAgentisAnimalGroomtohasAnimalGroom
Reviewers
- @JuergenGrupp
- @aro-max
I have 3 improvements to this pull request:
-
I think I have spotted an error in our renaming plan of
applyTo:applyTois currently only used here: RightsapplyToAsset. The wording seemed strange at first, because of the plural "apply" instead of "applies". That is why we proposed this change tohasTerritoryIncludes. But the meaning would change withhasTerritoryIncludeand the grammar ofapplyTois fully correct and expresses exactly what our intention is. My conclusion: stick withapplyToand do not rename it. -
There is another class to use
applyTowith:PublicationEvent. My conclusion: add the following restriction to the ontology: "RightsapplyToPublicationEvent. -
This opens up the opportunity to make "applyTo" and "isCoveredBy" inverse properties. My conclusion: add the rule
applyToisInverseOfisCoveredBy
Please comment!
Yes @JuergenGrupp, I agree. @aro-max do you agree with these changes so I can proceed with making the updates?
Here are the latest changes made:
- Reinitialized the
applyToobject property instead of renaming it tohasTerritoryIncludes. - Removed the
Rights hasTerritoryIncludes Assetrestriction and replaced it with theRights applyTo Assetrestriction. - Added a new restriction:
Rights applyTo PublicationEvent. - Added
applyToobject property as the inverse of theisCoveredByobject property, which is renamed tohasRights.
@JuergenGrupp, can you please review the latest changes and merge it?
Cleaned up mixed-in property values for rdfs:label and dcterms:description from hasRelatedAgent, ensuring only 3 values for supported languages, and removed owl:IrreflexiveProperty from hasRelatedAgent.