Skip to content

Add annotation properties to indicate intended usage of properties AND 'min 0' begone.  #389

Closed
@uscholdm

Description

@uscholdm

A common problem is over-constraining the domain or range of a property. One can err on the side of adaptability by having no domain or range, but then there is no information about its likely use.

For example, the property formerlyPartOf is being used at Platts to indicate that Ukraine was part of the Soviet Union. For the foreseeable future this will only be used when the subject and object are both instances of pleo:Region. I want to indicate this w/o having it be the domain and range, because lots of things can be former parts of other things. I propse doing the followign:

pleo:domainIncludes rdfs:subPropertyOf skos:scopeNote .
pleo:rangeIncludes  rdfs:subPropertyOf skos:scopeNote .
pleo:formerlyPartOf pleo:domainIncludes pleo:Region .
pleo:formerlyPartOf pleo:rangeIncludes pleo:Region .

This also eliminates the temptation to add a min 0 - restriction on the class pleo:Region.

Metadata

Metadata

Assignees

Labels

effort: smallRequires less than one day to completeimpact: patchNo new functionality or changes in human-readable semantics (e.g,. fixing a typo in an annotation)topic: annotations

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions