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: principles/fp-001-open.md
+1-27Lines changed: 1 addition & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,8 +61,7 @@ The attribution method for individual terms reused in another ontology (e.g., by
61
61
1.**In OWL** - Any ontology re-using individual terms from another ontology should:
62
62
63
63
1. re-use the original term IRI (which for OBO Foundry ontologies is generally in the form of an OBO Foundry PURL)
64
-
2. use an IAO:imported from annotation <http://purl.obolibrary.org/obo/IAO_0000412> on each imported term to link back to the group (i.e. ontology) maintaining it, where more information would be available about the license
65
-
3. include any annotations for term or definition editors from the original ontology
64
+
2. include any annotations for term or definition editors from the original ontology
66
65
67
66
2.**In OBO** - Any ontology re-using individual terms from another ontology should:
68
67
1. re-use the original term ID (of the form <GO:0000001>)
@@ -124,31 +123,6 @@ The first course of action should be to reuse the external term as is, by import
124
123
125
124
Please see the discussion tab for additional discussion of how to use different annotation properties to credit external ontologies or definition sources.
126
125
127
-
#### Example 3A: IAO:imported from
128
-
129
-
The Ontology for Biomedical Investigation (OBI) imports the class "environmental material" from the Environment Ontology (ENVO), using OntoFox. The imported from axiom is automatically generated by Ontofox and added to "environmental material" in OBI:
- An ontology with no license statement is by default subject to the most restrictive copyright laws for those parts of the ontology that are copyrightable, and therefore is not useful within the OBO Foundry.
Copy file name to clipboardExpand all lines: principles/fp-002-format.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
@@ -15,7 +15,7 @@ A common format allows the maximum number of people to access and reuse an ontol
15
15
16
16
## Recommendations and Requirements
17
17
18
-
All ontologies MUST have at least one OWL product whose name corresponds to the registered prefix (e.g., 'GO' --> go.owl, 'OBI' --> obi.owl). Thus the ontology whose IRI is http://purl.obolibrary.org/obo/ro.owl (known to the OBO Foundry as 'RO'), must have at least the product ro.owl. Developers are free to use whatever combination of technologies and formats is appropriate for development. However, the official OWL PURL (see [Principle 3](https://obofoundry.org/principles/fp-003-uris.html)) for the ontology MUST resolve to a syntactically valid OWL file using the [RDF-XML](https://www.w3.org/TR/rdf-syntax-grammar/) syntax.
18
+
All ontologies MUST have at least one OWL product whose name corresponds to the registered prefix (e.g., 'GO' --> go.owl, 'OBI' --> obi.owl). Thus the ontology whose IRI is http://purl.obolibrary.org/obo/ro.owl (known to the OBO Foundry as 'RO'), MUST have at least the product ro.owl which MUST be a syntactically valid OWL file using the [RDF-XML](https://www.w3.org/TR/rdf-syntax-grammar/) syntax. Developers are free to use whatever combination of technologies and formats is appropriate for development.
19
19
20
20
Developers can OPTIONALLY produce ontologies in other formats. These are conventionally the same IRI as the owl, but with .owl changed to the relevant extension (e.g., '.obo', '.json'). Note that such products are not listed by default. If you produce an additional format product, you should register it under the 'products' field in the appropriate metadata file found in this [folder](https://github.com/OBOFoundry/OBOFoundry.github.io/tree/master/ontology).
Copy file name to clipboardExpand all lines: principles/fp-003-uris.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,8 @@ A unique namespace within the OBO Foundry Library allows the source of an elemen
17
17
18
18
Each ontology MUST have a unique IRI in the form of an OBO Foundry permanent URL (PURL). The PURL must include the ontology namespace, which is a short string of letters (usually 2-5) that represents the ontology. Namespaces MUST be approved by the OBO Foundry Operations Committee. Every element (class, property, etc.) created by the ontology MUST use the namespace in the identifier of each element, as specified in the OBO Foundry [ID policy](http://www.obofoundry.org/id-policy).
19
19
20
+
The official PURL for the ontology, after redirection, MUST resolve to the ontology OWL file (see [Principle 2](https://obofoundry.org/principles/fp-002-format.html) for format requirements). Furthermore, PURLs for individual terms, after redirection, MUST resolve to a dedicated _term-centric_ destination page containing the appropriate content.
Copy file name to clipboardExpand all lines: principles/fp-009-users.md
+30-30Lines changed: 30 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ scientific area and does so in a usable and sustainable fashion.
20
20
It is important to be able to illustrate usage outside of the immediate circle of ontology developers and stakeholders. Demonstrations of usage MUST be publicly available. Preferred indicators of usage are those that directly demonstrate such, including:
21
21
22
22
- Use of the target ontology's term IRIs in an external ontology. Indicators of this type MUST include one or more IRIs for a term _within the external ontology_ that uses a term from the target ontology.
23
-
23
+
24
24
- Documentation of requests from multiple users. Indicators of this type MUST link to specific requests in the issue tracker, OR link to an issue tracker search (for example, showing new term requests), OR link to an email thread or other mechanism _if publicly viewable_.
25
25
26
26
- Publications showing the ontology being used in research by external users. Indicators of this type MUST provide citation details for the publications (link to PubMed or full text) and MUST include a sentence demonstrating the use (preferably taken from the title, abstract, or full text of the cited reference). Note that if citing full text that is behind a paywall, it may be necessary to provide a PDF for the paper.
@@ -42,67 +42,67 @@ Other indicators are currently possible as well:
42
42
within some community (mere mention of the existence is not enough
43
43
to warrant inclusion).
44
44
45
-
Note that the ontology can still be listed on the OBO Foundry website while publicising your resource in appropriate channels and searching for users with needs you can meet.
45
+
Note that the ontology can still be listed on the OBO Foundry website while publicising your resource in appropriate channels and searching for users with needs you can meet.
46
46
47
47
## Implementation
48
48
49
49
The ontology developers MUST provide links/citations to publicly available evidence of
50
-
use within your ontology [metadata file](https://github.com/OBOFoundry/OBOFoundry.github.io/tree/master/ontology) as given below (replacing with the correct group name, link, and description):
50
+
use within your ontology [metadata file](https://github.com/OBOFoundry/OBOFoundry.github.io/tree/master/ontology) as given below (after replacing with the correct description of usage, description of example, link to example, and link to user group):
51
51
52
52
```yaml
53
53
usages:
54
-
- user: http://www.informatics.jax.org/disease (link to group)
55
-
description: MGI disease model annotations use DO (description of group)
54
+
- description: MGI disease model annotations use DO (description of usage)
56
55
examples:
57
-
- url: http://www.informatics.jax.org/disease/DOID:4123 (link to specific example)
58
-
description: Human genes and mouse homology associated with nail diseases (description of specific example)
56
+
- description: Human genes and mouse homology associated with nail diseases (description of example)
57
+
url: http://www.informatics.jax.org/disease/DOID:4123 (link to example)
58
+
user: http://www.informatics.jax.org/disease (link to user group)
59
59
```
60
60
61
-
You may have multiple examples for each user, and mulitple users under the `usages` tag.
61
+
You may have multiple examples for each user, and multiple users under the `usages` tag.
62
62
63
63
## Examples
64
64
65
65
Use of PSI-MOD term IRI (in the form of a CURIE) in the PR ontology:
Publication showing the Disease Ontology being used in research by external users
82
82
```yaml
83
-
- user: https://pubmed.ncbi.nlm.nih.gov/36860337/
84
-
description: Machine learning-based prediction of candidate gene biomarkers correlated with immune infiltration in patients with idiopathic pulmonary fibrosis
83
+
- description: Machine learning-based prediction of candidate gene biomarkers correlated with immune infiltration in patients with idiopathic pulmonary fibrosis
85
84
examples:
86
-
- url: https://pubmed.ncbi.nlm.nih.gov/36860337/
87
-
description: In abstract, "Functional annotation, pathway enrichment, Disease Ontology and gene set enrichment analyses revealed..."
85
+
- description: In abstract, "Functional annotation, pathway enrichment, Disease Ontology and gene set enrichment analyses revealed..."
0 commit comments