Skip to content

Commit 176fdd6

Browse files
authored
Update StandardizationGuidelines.md
1 parent 450e129 commit 176fdd6

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

docs/StandardizationGuidelines.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,9 @@ title: Ontology Standardization Guidelines
2525
### Releases
2626

2727
- (ACCEPTED? Also check what should be the 'official' release. Reasoned?) Every ontology SHOULD provide a base (from [#482](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/482))
28+
- 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 some standards in terms of content:
29+
- **Base** (denoted by ?): 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. QUESTION: WILL THERE BE A SPECIFIC REASONER?
30+
2831
- (ACCEPTED?) Every ontology primary release MUST be consistent and coherent (from [#482](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/482))
2932

3033
### Social

0 commit comments

Comments
 (0)