how online template libraries that support specific ontologies should be built, made available, and maintained
… pointing to a need for new OTTR annotations.
Meta-ontology | OWL itself | http://tpl.ottr.xyz/owl/ |
Upper ontology | ISO 15926-14 | https://rds.posccaesar.org/ontology/lis14/tpl/ |
Industrial generic | POSC Caesar RDL | https://rds.posccaesar.org/ontology/plm/tpl/ |
Special purpose | Pizza | http://tpl.ottr.xyz/p/pizza/ |
A typical OWL ontology has dependencies
skos:definition
, dcterms:issued
, or foaf:img
If an import changes, the semantics may change, and reasoning reveals the change. Thanks to changes higher up, your subordinate ontology has been rendered inconsistent.
If a cherry-picked, external resource changes at origin, impact may go undetected.
owl:imports
Any OTTR template has dependencies
Described in The Core OTTR Template Library (M. Skjæveland, 2021).
The relation between modules and packages is that packages may, and usually will, rely on modules, while a module should not depend on any package. Templates in packages may mature to become part of or form new modules.
Version scheme.
http://tpl.ottr.xyz/[module name]/[version number]/[template name] http://tpl.ottr.xyz/p/[package name]/[version number]/[template name]
ottr.xyz
Pizza example@prefix pz: <http://www.co-ode.org/ontologies/pizza/pizza.owl#>. ... o-pizza:PizzaTopping[ ... o-owl-ax:SubClassOf(?blank505, pz:PizzaTopping),
The PizzaTopping
template uses the pz:PizzaTopping
ontology class, so
may be said to depend on the Pizza ontology.
Section 4.2.3. Versioning and template IRI design:
These don’t provide a default way to refer to the ontology needed to interpret the results of expansion.
Add to http://tpl.ottr.xyz/p/docttr/
owl:imports
the recommended ontologyAdd to the OTTR vocabulary
Coordinate the evolution of ontologies with the templates
Quality check: does the template output axioms that are consistent with the target ontology?
Contact: [email protected]