Skip to content

Commit 947a949

Browse files
authored
Update StandardizationGuidelines.md
1 parent ecc4008 commit 947a949

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/StandardizationGuidelines.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@ title: Ontology Standardization Guidelines
55

66
### Technical
77

8-
- (ACCEPTED?) Every ontology primary release (an OWL file) MUST be **logically consistent** (from [#482](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/482))
8+
- (ACCEPTED?) The ontology MUST be **logically consistent** (from [#482](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/482))
99
- This means (a) there MUST NOT be contradictory statements revealed by reasoning; (b) there MUST NOT be any unsatisfiable classes; and (c) there MUST NOT be any circular definitions.
10-
- (ACCEPTED? Should this be MUST?) Every ontology MUST be coherent when classified together with RO, BFO, and COB (from [#482](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/482))
10+
- This includes when the ontology is classified together with RO, BFO, and COB (from [#482](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/482))
1111
- (ACCEPTED? Need clarification on what exactly 'base dependency' is) Every ontology SHOULD be coherent when classified together with all its base-dependencies (from [#482](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/482))
1212
- Standardizing how imported ontologies are noted [#424](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/424)
1313
- Ontology metadata requirements [#1365](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/1365)
@@ -29,7 +29,7 @@ title: Ontology Standardization Guidelines
2929

3030
- In addition to a set of release standards in terms of format (see [Principle 2](https://obofoundry.org/principles/fp-002-format.html)), the following are the standards regarding imports, axiomization, and reasoning (see [Release Artefacts](https://oboacademy.github.io/obook/reference/release-artefacts/) for more detailed information):
3131
- **base** (REQUIRED; denoted by PURL ending with ONT.owl): Content includes only terms that are owned by the ontology, which include (a) terms using that ontology's prefix; and (b) any terms with a different prefix that are now maintained by that ontology. It does not contain any imports. It does, however, retain references to external ontologies within axioms as needed for definitions and reasoning. Such references, when displayed in Protege, will appear as identifiers only; that is, without labels. Finally, the base will have had reasoning already applied and will be stripped of redundant axioms. QUESTION: WILL THIS APPLY TO A SPECIFIC REASONER?
32-
- **full** (REQUIRED; denoted by PURL ending with ONT-full.owl ): Content is as for **base** except that all referenced external terms are present (that is, imports are merged into the **full** release).
32+
- **full** (REQUIRED; denoted by PURL ending with ONT-full.owl ): Content is as for **base** except that all referenced external terms (that is, are present (that is, imports are merged into the **full** release).
3333
- *other release artefacts* (OPTIONAL; denoted by PURL ending with ONT-<artefact_type>.owl): These include **non-classified**, **simple**, **basic**, and **simple-non-classified**. See the Release Artefacts link above for details on these.
3434
- (ACCEPTED?) Every ontology SHOULD provide a 'base' release (from [#482](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/482))
3535

0 commit comments

Comments
 (0)