Difference between revisions of "OBO Foundry"
Line 5: | Line 5: | ||
*May 10th, 2011: [[POC_Conf._Call_5-10-11#Review_for_OBO_Foundry_Acceptance]] | *May 10th, 2011: [[POC_Conf._Call_5-10-11#Review_for_OBO_Foundry_Acceptance]] | ||
+ | BS brought up the topic of review for OBO Foundry acceptance at the [[POC_Conf._Call_4-19-11]]. He suggested that the PO can be submitted for OBO Foundry membership within the next few weeks. | ||
+ | List of Foundry Principles:[[http://www.obofoundry.org/wiki/index.php/Category:Accepted Accepted]] with a brief summary of each: | ||
+ | |||
+ | * [http://www.obofoundry.org/wiki/index.php/FP_001_open FP 001 open]: | ||
+ | The ontology must be open and available to be used by all without any constraint other than (a) its origin must be acknowledged and (b) it is not to be altered and subsequently redistributed under the original name or with the same identifiers. | ||
+ | |||
+ | * [http://www.obofoundry.org/wiki/index.php/FP_002_format FP 002 format]: | ||
+ | The ontology is in, or can be expressed in, a common shared syntax. This may be either the OBO syntax, extensions of this syntax, or OWL. | ||
+ | |||
+ | * [http://www.obofoundry.org/wiki/index.php/FP_003_URIs FP 003 URIs]: | ||
+ | The ontology possesses a unique identifier space within the OBO Foundry. The identifier uniquely and persistently identifies a definition, which itself unambiguous identifies some type of biological entity. The identifier is for the definition: it is NOT the name and it is NOT an identifier for the name. | ||
+ | |||
+ | * [http://www.obofoundry.org/wiki/index.php/FP_004_versioning FP 004 versioning]: | ||
+ | The ontology provider has procedures for identifying distinct successive versions. | ||
+ | |||
+ | * [http://www.obofoundry.org/wiki/index.php/FP_005_delineated_content FP 005 delineated content]: | ||
+ | The ontology has a clearly specified and clearly delineated content. The ontology must be orthogonal to other ontologies already lodged within OBO. | ||
+ | |||
+ | * [http://www.obofoundry.org/wiki/index.php/FP_006_textual_definitions FP 006 textual definitions]: | ||
+ | The ontologies include textual definitions for all terms. | ||
+ | |||
+ | * [http://www.obofoundry.org/wiki/index.php/FP_007_relations FP 007 relations]: | ||
+ | The ontology uses relations which are unambiguously defined following the pattern of definitions laid down in the OBO Relation Ontology. | ||
+ | |||
+ | * [http://www.obofoundry.org/wiki/index.php/FP_008_documented FP 008 documented]: | ||
+ | The ontology is well documented. | ||
+ | |||
+ | * [http://www.obofoundry.org/wiki/index.php/FP_009_users FP 009 users]: | ||
+ | The ontology has a plurality of independent users. | ||
+ | |||
+ | * [http://www.obofoundry.org/wiki/index.php/FP_010_collaboration FP 010 collaboration]: | ||
+ | The ontology will be developed collaboratively with other OBO Foundry members. | ||
+ | |||
+ | * [http://www.obofoundry.org/wiki/index.php/FP_011_locus_of_authority FP 011 locus of authority]: | ||
+ | single locus of authority, tracker (SOP), responsive help desk | ||
+ | |||
+ | * [http://www.obofoundry.org/wiki/index.php/FP_012_naming_conventions FP 012 naming conventions]: | ||
+ | See [http://www.obofoundry.org/wiki/index.php/Naming naming conventions] | ||
+ | |||
+ | * [http://www.obofoundry.org/wiki/index.php/FP_016_maintenance FP 016 maintenance] | ||
+ | OBO is an open community and, by joining the initiative, the authors of an ontology commit to its maintenance in light of scientific advance and to working with other members to ensure the improvement of these principles over time | ||
+ | |||
+ | |||
+ | ''We reviewed the list and feel that we are in compliance on all of them, although the PGDSO still needs to be completely revised. LC will contact BS (since he was not present) and find out what the procedure is for applying for OBO Foundry acceptance. PJ thought we just send an email with a request to be considered. | ||
+ | '' | ||
Revision as of 21:13, 18 July 2011
The Plant Ontology is applying for membership. This was discussed at the POC Conf calls:
- May 10th, 2011: POC_Conf._Call_5-10-11#Review_for_OBO_Foundry_Acceptance
BS brought up the topic of review for OBO Foundry acceptance at the POC_Conf._Call_4-19-11. He suggested that the PO can be submitted for OBO Foundry membership within the next few weeks.
List of Foundry Principles:[Accepted] with a brief summary of each:
The ontology must be open and available to be used by all without any constraint other than (a) its origin must be acknowledged and (b) it is not to be altered and subsequently redistributed under the original name or with the same identifiers.
The ontology is in, or can be expressed in, a common shared syntax. This may be either the OBO syntax, extensions of this syntax, or OWL.
The ontology possesses a unique identifier space within the OBO Foundry. The identifier uniquely and persistently identifies a definition, which itself unambiguous identifies some type of biological entity. The identifier is for the definition: it is NOT the name and it is NOT an identifier for the name.
The ontology provider has procedures for identifying distinct successive versions.
The ontology has a clearly specified and clearly delineated content. The ontology must be orthogonal to other ontologies already lodged within OBO.
The ontologies include textual definitions for all terms.
The ontology uses relations which are unambiguously defined following the pattern of definitions laid down in the OBO Relation Ontology.
The ontology is well documented.
The ontology has a plurality of independent users.
The ontology will be developed collaboratively with other OBO Foundry members.
single locus of authority, tracker (SOP), responsive help desk
OBO is an open community and, by joining the initiative, the authors of an ontology commit to its maintenance in light of scientific advance and to working with other members to ensure the improvement of these principles over time
We reviewed the list and feel that we are in compliance on all of them, although the PGDSO still needs to be completely revised. LC will contact BS (since he was not present) and find out what the procedure is for applying for OBO Foundry acceptance. PJ thought we just send an email with a request to be considered.
- May 17th, 2011: POC_Conf._Call_5-17-11#OBO_Foundry_Acceptance
Comments: Need to display a list of webpages that use the PO and encourage other groups to link to the PO and where the PO is integrated into their search engines.
Need an impressive web page, volunteer to link to them
-need collaborator pages for SSWAP and NASC- others??
-1000 Transcriptome project- DWS will encourage them to have a link to PO, adopt the PO rather than free text for annotations
BS: Need to demonstrate utility, will help with getting refunded