Principle: Documentation (principle 8)
- Open (principle 1)
- Common Format (principle 2)
- URI/Identifier Space (principle 3)
- Versioning (principle 4)
- Scope (principle 5)
- Textual Definitions (principle 6)
- Relations (principle 7)
- Documentation (principle 8)
- Documented Plurality of Users (principle 9)
- Commitment To Collaboration (principle 10)
- Locus of Authority (principle 11)
- Naming Conventions (principle 12)
- Maintenance (principle 16)
- Responsiveness (principle 20)
The wording of this principle is still in progress, with some issues still to be addressed (see Issues To Be Addressed below).
The owners of the ontology should strive to provide as much documentation as possible. The documentation should detail the different processes specific to an ontology life cycle and target various audiences (users or developers).
Central to the issue of ontology documentation is ensuring transparency and traceability of artefact development. For each of the development steps, clear procedures should be made available. Documentation availability will be used to assess the quality of the resource. The following itemized list provides a core checklist, distinguishing general ontology documentation (general information about the resource) and local ontology documentation (documentation at artefact level itself and representational unit level (class and relations)). Documentation assessment with the purpose of assessing Ontology soundness, will cover updates and revision to the documentation. As ontology evolve, so should the documentation, for example by including a release documentation file.
- Embedded or ‘in-situ’ documentation: Namely any specific metadata available from the ontology artefact itself providing information about the resource in its entirety or parts of it. global ontology description (about the ontology as a whole):
- local ontology documentation (about each term): documentation for individual representational unit annotation
- justify the different elements of class metadata
justify class axiomatization documentation about the textual definition: is it manually created or generated with software assistance by relying on patterns and class axioms.
- User documentation: A documentation detailing the ontology’s raison d’etre, its coverage, the use cases and query cases (including translation into SPARQL queries) it is intended to support documentation about how to access the resource documentation about how to produce semantic web document compatible with the representation intended by the developers (OWL examples, OWL coding patterns)
- availability of peer-reviewed publication about the resource
- availability of training material and tutorial
- availability of presentations (e.g. on slideshare)
availability of web seminars (e.g. on a youtube channel)
- documentation about authors contributions
- documentation about licensing terms, rights of use.
- documentation about version control
- documentation about release process
- documentation about changes in ontology between release version
- continuous integration
- documentation about the methodology used for developing the resource
- documentation about interaction with orthogonal resources
- documentation about resource acknowledgement
- documentation about term submission/term requests
- documentation about batch submission
- documentation about term deprecation and deprecation policy (aka retirement policy)
- documentation about conflict resolution
- a documentation detailing the use of software agent devised or exploited to develop, maintain, enhance, perform quality control and ensure high availability of the resource
- documentation about how the ontology is being used
Issues To Be Addressed (partial list):
What minimal metadata is needed?
What minimal documentation is needed?
Clarification of the role of publications
the ontology is well-documented (e.g. in a published paper describing the ontology or in manuals for developers and users)