Inconsistent annotation of external properties

[cKlee]

We have three external classes

• DocumentService
• Location
• Chronology

These classes are connected with the core classes either through properties defined in the holding ontology or through external object properties.

With the latter we did this not consistently.

Either we annotate all the corresponding object properties like we did with

• service:providedBy
• gr:availableAtOrFrom
• org:siteOf

This means dso:hasService, daia:availableFor, daia:unavailableFor, ecpo:hasChronology and ecpo:hasChronolgyGap are missing.

OR we drop the annotation of external object properties and just make a textual recommendation to use these properties.

The two external data properties

• gr:name
• gr:hasStockKeepingUnit

might also be dropped and recommended in text. They are quite arbitrary I think.

The property dct:hasPart is very important to this ontology. It should be annotated. See also #30

[nichtich]

Textual recommendations are fine, as the primary goal of holding ontology is to give recommendations to humans, not to provide a single set of OWL for automatic reasoning. The external properties mentioned above should be included in the documentation with examples and images, but they do not need to be included in the RDF file.

[cKlee]

Done with d789dc7