You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/StandardizationGuidelines.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ GO TO: [Technical Considerations](#technical-considerations) | [Content-Con
12
12
- (b) there MUST NOT be any unsatisfiable classes; and
13
13
- (c) there MUST NOT be any circular definitions.
14
14
- This includes when the ontology is classified together with RO, BFO, and COB
15
-
- This also includes when the ontology is classified together with its base dependencies; that is, as part of a 'full' release (see Releases section below)
15
+
- This also includes when the ontology is classified together with its base dependencies; that is, as part of a 'full' release (see [Release Considerations](#release-considerations) section below)
- Some ontology browsers make use of an ontology-wide annotation property, 'has ontology root term' (IAO:0000700), that governs how the hierarchy is displayed. This helps shield users from having to navigate through not-specific-enough parent terms (such as BFO:0000040 "material entity"). To enable this feature, an ontology SHOULD specify one or more appropriate root terms like so:
0 commit comments