Skip to content

Commit e0f34da

Browse files
authored
Merge branch 'master' into patch-24
2 parents c6cd088 + bc71626 commit e0f34da

5 files changed

Lines changed: 8 additions & 8 deletions

File tree

docs/Policy_for_OBO_namespace_and_associated_PURL_requests.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ title: OBO Foundry membership requirements and technical details
55

66
# Expectations for OBO Membership
77

8-
1. Participation in the OBO Foundry implies willingness to discuss your project and collaboratively develop it. You are strongly encouraged to build upon the existing suite of ontologies available in the [OBO library](http://obofoundry.org).
8+
1. Participation in the OBO Foundry implies willingness to discuss your project and collaboratively develop it. You are strongly encouraged to build upon the existing suite of ontologies available in the [OBO Foundry](http://obofoundry.org).
99

1010
2. We recommend projects be orthogonal to each other (i.e. no domain overlap). For those classes that are common across multiple resources (e.g., the class _cell_) we recommend importing terms from an already existing ontology. Application ontologies (those developed for specific data integration tasks) should reuse terms from existing OBO Foundry domain ontologies. At a minimum, we expect attribution of existing work, specifically through the use of PURLs for individual terms and ontologies.
1111

faq/what-is-the-build-field.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,8 @@ build:
1818
...
1919
```
2020

21-
This is instructions for the central OBO library build pipeline which
22-
runs nightly. This ensures creation of correct obo and owl files for
21+
These are the instructions for the central OBO Foundry build pipeline that
22+
runs nightly, which ensures creation of correct obo and owl files for
2323
each ontology.
2424

2525
The output goes here:

ontology/peco.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ contact:
77
github: jaiswalp
88
label: Pankaj Jaiswal
99
orcid: 0000-0002-1005-8383
10-
depicted_by: http://planteome.org/sites/default/files/garland_logo.PNG
10+
depicted_by: https://raw.githubusercontent.com/Planteome/plant-ontology/refs/heads/master/Planteome_profile.jpg
1111
description: A structured, controlled vocabulary which describes the treatments, growing conditions, and/or study types used in plant biology experiments.
1212
domain: investigations
1313
homepage: http://planteome.org/

ontology/pso.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,8 @@ description: The Plant Stress Ontology describes biotic and abiotic stresses tha
1313
domain: agriculture
1414
homepage: https://github.com/Planteome/plant-stress-ontology
1515
license:
16-
label: CC BY 3.0
17-
url: http://creativecommons.org/licenses/by/3.0/
16+
label: CC BY 4.0
17+
url: http://creativecommons.org/licenses/by/4.0/
1818
preferredPrefix: PSO
1919
products:
2020
- id: pso.owl

principles/fp-014-guidelines.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ GO TO: [Recommendations/Requirements](#recommendations-and-requirements) |
1010

1111
## Summary
1212

13-
In addition to the principles, each ontology MUST follow general OBO guidelines.
13+
In addition to the principles, each ontology MUST follow other OBO guidelines.
1414

1515
## Purpose
1616

17-
Text to be added.
17+
The OBO Foundry has developed a set of best practices that address specific ontology development issues. Unlike the more high level requirements of the OBO Foundry principles, these practices tend to be detailed and often can be characterized as recommendations rather than hard requirements. Following these practices improves uniformity and interoperability of OBO ontologies. Therefore, the OBO Foundry has chosen to elevate these best practices to guidelines.
1818

1919
## Recommendations and Requirements
2020

0 commit comments

Comments
 (0)