diff --git a/.travis.yml b/.travis.yml index 1f2e582..be3fa98 100644 --- a/.travis.yml +++ b/.travis.yml @@ -2,15 +2,15 @@ ## Go to: https://travis-ci.org/EBISPOT for details language: java jdk: - - oraclejdk8 + - openjdk8 before_script: - mkdir -p bin - export PATH=$PATH:$PWD/bin - - wget http://build.berkeleybop.org/userContent/owltools/owltools -O bin/owltools - - wget http://build.berkeleybop.org/userContent/owltools/ontology-release-runner -O bin/ontology-release-runner - - wget http://build.berkeleybop.org/userContent/owltools/owltools-runner-all.jar -O bin/owltools-runner-all.jar - - wget http://build.berkeleybop.org/userContent/owltools/owltools-oort-all.jar -O bin/owltools-oort-all.jar + - export OWLTOOLS=2020-04-06 + - wget https://github.com/owlcollab/owltools/releases/download/${OWLTOOLS}/owltools -O bin/owltools + - wget https://github.com/owlcollab/owltools/releases/download/${OWLTOOLS}/ontology-release-runner -O bin/ontology-release-runner + - wget https://github.com/owlcollab/owltools/releases/download/${OWLTOOLS}/owltools-oort-all.jar -O bin/owltools-oort-all.jar - wget https://raw.githubusercontent.com/ontodev/robot/master/bin/robot -O bin/robot - wget https://github.com/ontodev/robot/releases/download/v1.2.0/robot.jar -O bin/robot.jar - wget --no-check-certificate https://raw.githubusercontent.com/cmungall/pattern2owl/master/apply-pattern.py -O bin/apply-pattern.py diff --git a/README.md b/README.md index c3277ab..9ac0020 100644 --- a/README.md +++ b/README.md @@ -10,6 +10,7 @@ Table of Contents * [Stable release versions](#stable-release-versions) * [Editors' version](#editors-version) * [Contact](#contact) + * [DUO users](#duo---users) * [DUO - Full documentation](#duo---full-documentation) * [What is DUO?](#what-is-duo-1) * [How did DUO come about?](#how-did-duo-come-about) @@ -17,6 +18,7 @@ Table of Contents * [Examples of use](#examples-of-use) * [Tagging with ‘data use restrictions/conditions’](#tagging-with-data-use-restrictionsconditions) * [Powering dataset access screening queries](#powering-dataset-access-screening-queries) + * [DUO Webinar](#duo-webinar) * [Automated data access requests](#automated-data-access-requests) * [How does querying work when using DUO?](#how-does-querying-work-when-using-duo) * [Research Purpose : Data Use Limitation Matching](#research-purpose--data-use-limitation-matching) @@ -64,6 +66,14 @@ Editors of this ontology should use the edit version, [src/ontology/duo-edit.owl ## Contact Please use this GitHub repository's [Issue tracker](https://github.com/EBISPOT/duo/issues) to request new terms/classes or report errors or specific concerns related to the ontology. +## DUO - users +Several projects have now implemented DUO in production pipelines: +- the Broad Institute’s Data Use Oversight System, [DUOS](https://duos.broadinstitute.org/#/home) +- the European Genome-phenome Archive (EGA). See [here](https://ega-archive.org/datasets/EGAD00001000002) for example. +- the Data Information System, [DAISY](https://github.com/elixir-luxembourg/daisy) + +[Contact](#contact) us to tell us about your implementation! + # DUO - Full documentation ## What is DUO? @@ -117,6 +127,11 @@ The following figure illustrates how DUO terms can be used to represent data use ![alt tag](https://github.com/EBISPOT/DUO/blob/master/doc/figs/DUO_matching.png "DUO matching") +### DUO Webinar +[Watch a webinar here](https://www.youtube.com/watch?v=8ZyU34xpi4M&t=1s) with an explanation of the DUO as well as several global users describing how they integrate it into their systems. + +[![](http://img.youtube.com/vi/8ZyU34xpi4M/0.jpg)](http://www.youtube.com/watch?v=8ZyU34xpi4M "") + ## Automated data access requests In the long term, we envision DUO coupled with matching algorithms such as DUOS to empower services that automatically determine if a user’s research purpose is compatible with data use restrictions on datasets and in turn determine whether to give a researcher access to the data. @@ -212,6 +227,7 @@ J. Patrick Woolley, Emily Kirby, Josh Leslie, Francis Jeanson, Moran N. Cabili, - Melanie Courtot (EMBL-EBI) - Stacey Donnelly (GA4GH/Broad) - Stephanie Dyke (Mc Gill) +- Melissa Haendel (OHSU) - Francis Jeanson (IAMOPEN) - Giselle Kerry (EMBL-EBI, EGA) - Melissa Konopko (Wellcome Sanger Institute) @@ -220,11 +236,13 @@ J. Patrick Woolley, Emily Kirby, Josh Leslie, Francis Jeanson, Moran N. Cabili, - Greeshma Neglur (NCI Commons/U chicago) - Laura Paglione (Spherical Cow) - Ravi Pandya (Microsoft Research) -- Anthony Philippakis (Broad Institute of MIT and Harvard) +- Anthony Philippakis (Broad Institute of MIT and Harvard) +- Jordi Rambla (Centre for Genomic Regulation, EGA) - Greg Rushton (Broad Institute of MIT and Harvard) - Kathy Reinold (Broad Institute of MIT and Harvard) - Laura Rodriguez (NHGRI) - Andrea Saltzman (Broad) +- Heidi Sofia (NIH) - Dylan Spalding (EMBL-EBI, EGA) - Anne-Marie Tasse (McGill University) - Adrian Thorogood (McGill University) diff --git a/doc/release_notes.md b/doc/release_notes.md new file mode 100644 index 0000000..70ece65 --- /dev/null +++ b/doc/release_notes.md @@ -0,0 +1,19 @@ + +# DUO - Release notes + +## v2020-02-03 + +This release addresses several outstanding tickets: + +- A flat file (CSV) version of DUO is now being created at release time. This file is available from http://purl.obolibrary.org/obo/duo/duo.csv Despite being versioned this file does not include the version explicitly: a ticket has been created to do this in the next release, https://github.com/EBISPOT/DUO/issues/40 +- HMB has been moved to be a child of GRU and sibling of GRU-CC : HMB definition doesn't include clinical care and the hierarchy was therefore updated to reflect this. +- The term 'consent code' has been relabeled as 'data use limitation'. To optimise search the term 'consent code' has been retained as an alternative term. +- The term 'consent code primary category' and 'secondary category' have been deprecated: they were not used to tag datasets but instead as patterns for DUO codes capture. Those patterns are institue specific and would be better reflected by Schemablocks constraints specific to a repository. + + +Minnor fixes +- Addition of xsd:datatype to text field, as per https://github.com/EBISPOT/DUO/issues/33. Reported and fixed by @haoyuanli +- Consistency of ID annotation properties, as per https://github.com/EBISPOT/DUO/issues/32. Reported by @haoyuanli +- typo has been ported back to IAO, https://github.com/EBISPOT/DUO/issues/24 + +## no release notes for older versions diff --git a/duo-basic.owl b/duo-basic.owl index b73baba..334c267 100644 --- a/duo-basic.owl +++ b/duo-basic.owl @@ -7,19 +7,12 @@ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" + xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" + xmlns:protege="http://protege.stanford.edu/plugins/owl/protege#" xmlns:oboInOwl="http://www.geneontology.org/formats/oboInOwl#"> - - Cooper Stansbury - David An - Dylan Spalding - Giselle Kerry - Gregory Rushton - J. Neil Otte - Moran Ncabili - Stephanie Dyke - Melanie Courtot + @@ -35,6 +28,35 @@ + + + + + + + + + + Relates an entity in the ontology to the name of the variable that is used to represent it in the code that generates the BFO OWL file from the lispy specification. + Really of interest to developers only + BFO OWL specification label + + + + + + + + + Relates an entity in the ontology to the term that is used to represent it in the the CLIF specification of BFO2 + Person:Alan Ruttenberg + Really of interest to developers only + BFO CLIF specification label + + + + + @@ -46,20 +68,61 @@ + editor preferred label + editor preferred label + editor preferred term editor preferred term + editor preferred term~editor preferred label The concise, meaningful, and human-friendly name for a class or property preferred by the ontology developers. (US-English) PERSON:Daniel Schober GROUP:OBI:<http://purl.obolibrary.org/obo/obi> + editor preferred label + editor preferred label + editor preferred term editor preferred term + editor preferred term~editor preferred label + + + + + + + + example + + A phrase describing how a term should be used and/or a citation to a work which uses it. May also include other kinds of examples that facilitate immediate understanding, such as widely know prototypes or instances of a class, or cases where a relation is said to hold. + PERSON:Daniel Schober + GROUP:OBI:<http://purl.obolibrary.org/obo/obi> + + example of usage + + + + + + + + in branch + An annotation property indicating which module the terms belong to. This is currently experimental and not implemented yet. + GROUP:OBI + OBI_0000277 + in branch - + + has curation status + PERSON:Alan Ruttenberg + PERSON:Bill Bug + PERSON:Melanie Courtot + OBI_0000281 + has curation status + @@ -67,7 +130,10 @@ definition + definition + textual definition + The official OBI definition, explaining the meaning of a class or property. Shall be Aristotelian, formalized and normalized. Can be augmented with colloquial definitions. The official definition, explaining the meaning of a class or property. Shall be Aristotelian, formalized and normalized. Can be augmented with colloquial definitions. 2012-04-05: Barry Smith @@ -94,19 +160,37 @@ We also have the outstanding issue of how to aim different definitions to differ definition definition + textual definition - + + editor note + + An administrative note intended for its editor. It may not be included in the publication version of the ontology, so it should contain nothing necessary for end users to understand the ontology. + PERSON:Daniel Schober + GROUP:OBI:<http://purl.obfoundry.org/obo/obi> + + editor note + - + + term editor + + Name of editor entering the term in the file. The term editor is a point of contact for information regarding the term. The term editor may be, but is not always, the author of the definition, which may have been worked upon by several people + 20110707, MC: label update to term editor and definition modified accordingly. See https://github.com/information-artifact-ontology/IAO/issues/115. + PERSON:Daniel Schober + GROUP:OBI:<http://purl.obolibrary.org/obo/obi> + + term editor + @@ -126,7 +210,28 @@ We also have the outstanding issue of how to aim different definitions to differ - + + definition source + + formal citation, e.g. identifier in external database to indicate / attribute source(s) for the definition. Free text indicate / attribute source(s) for the definition. EXAMPLE: Author Name, URI, MeSH Term C04, PUBMED ID, Wiki uri on 31.01.2007 + PERSON:Daniel Schober + Discussion on obo-discuss mailing-list, see http://bit.ly/hgm99w + GROUP:OBI:<http://purl.obolibrary.org/obo/obi> + + definition source + + + + + + + + has obsolescence reason + Relates an annotation property to an obsolescence reason. The values of obsolescence reasons come from a list of predefined terms, instances of the class obsolescence reason specification. + PERSON:Alan Ruttenberg + PERSON:Melanie Courtot + has obsolescence reason + @@ -143,6 +248,46 @@ We also have the outstanding issue of how to aim different definitions to differ + + + + term tracker item + the URI for an OBI Terms ticket at sourceforge, such as https://sourceforge.net/p/obi/obi-terms/772/ + + An IRI or similar locator for a request or discussion of an ontology term. + Person: Jie Zheng, Chris Stoeckert, Alan Ruttenberg + Person: Jie Zheng, Chris Stoeckert, Alan Ruttenberg + The 'tracker item' can associate a tracker with a specific ontology term. + term tracker item + + + + + + + + + The name of the person, project, or organization that motivated inclusion of an ontology term by requesting its addition. + Person: Jie Zheng, Chris Stoeckert, Alan Ruttenberg + Person: Jie Zheng, Chris Stoeckert, Alan Ruttenberg + The 'term requester' can credit the person, organization or project who request the ontology term. + ontology term requester + + + + + + + + is denotator type + relates an class defined in an ontology, to the type of it's denotator + In OWL 2 add AnnotationPropertyRange('is denotator type' 'denotator type') + Alan Ruttenberg + is denotator type + + + + @@ -158,6 +303,372 @@ We also have the outstanding issue of how to aim different definitions to differ + + + + expand expression to + ObjectProperty: RO_0002104 +Label: has plasma membrane part +Annotations: IAO_0000424 "http://purl.obolibrary.org/obo/BFO_0000051 some (http://purl.org/obo/owl/GO#GO_0005886 and http://purl.obolibrary.org/obo/BFO_0000051 some ?Y)" + + A macro expansion tag applied to an object property (or possibly a data property) which can be used by a macro-expansion engine to generate more complex expressions from simpler ones + Chris Mungall + expand expression to + + + + + + + + expand assertion to + ObjectProperty: RO??? +Label: spatially disjoint from +Annotations: expand_assertion_to "DisjointClasses: (http://purl.obolibrary.org/obo/BFO_0000051 some ?X) (http://purl.obolibrary.org/obo/BFO_0000051 some ?Y)" + + A macro expansion tag applied to an annotation property which can be expanded into a more detailed axiom. + Chris Mungall + expand assertion to + + + + + + + + first order logic expression + PERSON:Alan Ruttenberg + first order logic expression + + + + + + + + antisymmetric property + part_of antisymmetric property xsd:true + use boolean value xsd:true to indicate that the property is an antisymmetric property + Alan Ruttenberg + antisymmetric property + + + + + + + + OBO foundry unique label + + An alternative name for a class or property which is unique across the OBO Foundry. + The intended usage of that property is as follow: OBO foundry unique labels are automatically generated based on regular expressions provided by each ontology, so that SO could specify unique label = 'sequence ' + [label], etc. , MA could specify 'mouse + [label]' etc. Upon importing terms, ontology developers can choose to use the 'OBO foundry unique label' for an imported term or not. The same applies to tools . + PERSON:Alan Ruttenberg + PERSON:Bjoern Peters + PERSON:Chris Mungall + PERSON:Melanie Courtot + GROUP:OBO Foundry <http://obofoundry.org/> + OBO foundry unique label + + + + + + + + Ontology: <http://purl.obolibrary.org/obo/ro/idrange/> + Annotations: + 'has ID prefix': "http://purl.obolibrary.org/obo/RO_" + 'has ID digit count' : 7, + rdfs:label "RO id policy" + 'has ID policy for': "RO" + Relates an ontology used to record id policy to the number of digits in the URI. The URI is: the 'has ID prefix" annotation property value concatenated with an integer in the id range (left padded with "0"s to make this many digits) + Person:Alan Ruttenberg + has ID digit count + + + + + + + + Datatype: idrange:1 +Annotations: 'has ID range allocated to': "Chris Mungall" +EquivalentTo: xsd:integer[> 2151 , <= 2300] + + Relates a datatype that encodes a range of integers to the name of the person or organization who can use those ids constructed in that range to define new terms + Person:Alan Ruttenberg + has ID range allocated to + + + + + + + + Ontology: <http://purl.obolibrary.org/obo/ro/idrange/> + Annotations: + 'has ID prefix': "http://purl.obolibrary.org/obo/RO_" + 'has ID digit count' : 7, + rdfs:label "RO id policy" + 'has ID policy for': "RO" + Relating an ontology used to record id policy to the ontology namespace whose policy it manages + Person:Alan Ruttenberg + has ID policy for + + + + + + + + Ontology: <http://purl.obolibrary.org/obo/ro/idrange/> + Annotations: + 'has ID prefix': "http://purl.obolibrary.org/obo/RO_" + 'has ID digit count' : 7, + rdfs:label "RO id policy" + 'has ID policy for': "RO" + Relates an ontology used to record id policy to a prefix concatenated with an integer in the id range (left padded with "0"s to make this many digits) to construct an ID for a term being created. + Person:Alan Ruttenberg + has ID prefix + + + + + + + + elucidation + person:Alan Ruttenberg + Person:Barry Smith + Primitive terms in a highest-level ontology such as BFO are terms which are so basic to our understanding of reality that there is no way of defining them in a non-circular fashion. For these, therefore, we can provide only elucidations, supplemented by examples and by axioms + + elucidation + + + + + + + + has associated axiom(nl) + Person:Alan Ruttenberg + Person:Alan Ruttenberg + An axiom associated with a term expressed using natural language + + has associated axiom(nl) + + + + + + + + has associated axiom(fol) + Person:Alan Ruttenberg + Person:Alan Ruttenberg + An axiom expressed in first order logic using CLIF syntax + + has associated axiom(fol) + + + + + + + + is allocated id range + Add as annotation triples in the granting ontology + Relates an ontology IRI to an (inclusive) range of IRIs in an OBO name space. The range is give as, e.g. "IAO_0020000-IAO_0020999" + PERSON:Alan Ruttenberg + is allocated id range + + + + + + + + retired from use as of + relates a class of CRID to the date after which further instances should not be made, according to the central authority + In OWL 2 add AnnotationPropertyRange xsd:dateTimeStamp + Alan Ruttenberg + retired from use as of + + + + + + + + A annotation relationship between two terms in an ontology that may refer to the same (natural) type but where more evidence is required before terms are merged. + David Osumi-Sutherland + #40 + VFB + 2018-09-21T16:43:39Z + Edges asserting this should be annotated with to record evidence supporting the assertion and its provenance. + may be identical to + + + + + + + + Used when the class or object is scheduled for obsoletion/deprecation on or after a particular date. + Chris Mungall, Jie Zheng + https://github.com/geneontology/go-ontology/issues/15532 + https://github.com/information-artifact-ontology/ontology-metadata/issues/32 + GO ontology + scheduled for obsoletion on or after + + + + + + + + + has axiom id + Person:Alan Ruttenberg + Person:Alan Ruttenberg + A URI that is intended to be unique label for an axiom used for tracking change to the ontology. For an axiom expressed in different languages, each expression is given the same URI + + has axiom label + + + + + + + + term replaced by + + Add as annotation triples in the granting ontology + Use on obsolete terms, relating the term to another term that can be used as a substitute + Person:Alan Ruttenberg + Person:Alan Ruttenberg + term replaced by + + + + + + + + An assertion that holds between an OWL Object Property and a temporal interpretation that elucidates how OWL Class Axioms that use this property are to be interpreted in a temporal context. + temporal interpretation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -170,6 +681,51 @@ We also have the outstanding issue of how to aim different definitions to differ + + + + + + + + + + + + + + + + + + + + + + label + label + + + + + + + + + + + + + + + + + + + + + + - consent code + data use limitation A data item that is used to indicate consent permissions for datasets and/or materials, and relates to the purposes for which datasets and/or material might be removed, stored or used. + consent code DUO:0000001 - consent code - - - - - - - - - consent code primary category - A categorical data item indicating the primary category the consent code belongs to according to Dyke et al. 2016. - DUO:0000002 - consent code primary category - - - - - - - - - consent code secondary category - A categorical data item indicating the secondary category the consent code belongs to according to Dyke et al. 2016. - DUO:0000003 - consent code secondary category + data use limitation @@ -219,11 +752,11 @@ We also have the outstanding issue of how to aim different definitions to differ - + no restriction - This consent code primary category indicates there is no restriction on use. + This data use limitation indicates there is no restriction on use. DUO:0000004 - NRES + NRES 20180907, Meeting Moran Melanie: This is to be thought about more carefully - what is the intent when using 'no restriction' as usually users still need to be researchers. Note: the NRES alternative term may be confusing as in the UK it also stands for National Research Ethics Service no restriction @@ -236,9 +769,10 @@ We also have the outstanding issue of how to aim different definitions to differ general research use and clinical care - This primary category consent code indicates that use is allowed for health/medical/biomedical purposes and other biological research, including the study of population origins or ancestry. + This data use limitation indicates that use is allowed for health/medical/biomedical purposes and other biological research, including the study of population origins or ancestry. DUO:0000005 - GRU-CC + GRU-CC + This term includes clinical care, which was not defined in the original consent codes paper. This term does not have a usage in our current use cases and we recommend using DUO:0000042, General Research Use, instead general research use and clinical care @@ -247,11 +781,11 @@ We also have the outstanding issue of how to aim different definitions to differ - + health/medical/biomedical research - This primary category consent code indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry. + This data use limitation indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry. DUO:0000006 - HMB + HMB health or medical or biomedical research @@ -262,9 +796,9 @@ We also have the outstanding issue of how to aim different definitions to differ disease-specific research - This primary category consent code indicates that use is allowed provided it is related to the specified disease. + This data use limitation indicates that use is allowed provided it is related to the specified disease. DUO:0000007 - DS + DS This term should be coupled with a term describing a disease from an ontology, such as the Disease Ontology, HPO, MonDO to specify the disease the restriction applies to. disease specific research @@ -274,12 +808,12 @@ We also have the outstanding issue of how to aim different definitions to differ - + population origins or ancestry research - This primary category consent code indicates that use of the data is limited to the study of population origins or ancestry. + This data use limitation indicates that use of the data is limited to the study of population origins or ancestry. population origins/ancestry research DUO:0000011 - POA + POA population origins or ancestry research @@ -288,11 +822,11 @@ We also have the outstanding issue of how to aim different definitions to differ - + research-specific restrictions - This secondary category consent code indicates that use is limited to studies of a certain research type. + This data use limitation indicates that use is limited to studies of a certain research type. DUO:0000012 - RS + RS research specific restrictions @@ -301,11 +835,11 @@ We also have the outstanding issue of how to aim different definitions to differ - + research use only - This secondary category consent code indicates that use is limited to research purposes (e.g., does not include its use in clinical care). + This data use limitation indicates that use is limited to research purposes (e.g., does not include its use in clinical care). DUO:0000014 - RU + RU research use only @@ -314,9 +848,9 @@ We also have the outstanding issue of how to aim different definitions to differ - + no general methods research - This secondary category consent code indicates that use includes methods development research(e.g., development of software or algorithms) only within the bounds of other use limitations. + This data use limitation indicates that use includes methods development research(e.g., development of software or algorithms) only within the bounds of other use limitations. DUO:0000015 no general methods research @@ -326,11 +860,11 @@ We also have the outstanding issue of how to aim different definitions to differ - + genetic studies only - This secondary category consent code indicates that use is limited to genetic studies only (i.e., no phenotype-only research) + This data use limitation indicates that use is limited to genetic studies only (i.e., no phenotype-only research) DUO:0000016 - GSO + GSO genetic studies only @@ -355,7 +889,7 @@ We also have the outstanding issue of how to aim different definitions to differ This requirement indicates that use of the data is limited to not-for-profit organizations and not-for-profit use, non-commercial use. non-commercial use DUO:0000018 - NPU + NPU not for profit use only @@ -368,7 +902,7 @@ We also have the outstanding issue of how to aim different definitions to differ publication required This requirement indicates that requestor agrees to make results of studies using the data available to the larger scientific community. DUO:0000019 - PUB + PUB publication required @@ -381,7 +915,7 @@ We also have the outstanding issue of how to aim different definitions to differ collaboration required This requirement indicates that the requestor must agree to collaboration with the primary study investigator(s). DUO:0000020 - COL + COL This could be coupled with a string describing the primary study investigator(s). collaboration required @@ -395,7 +929,7 @@ We also have the outstanding issue of how to aim different definitions to differ ethics approval required This requirement indicates that the requestor must provide documentation of local IRB/ERB approval. DUO:0000021 - IRB + IRB ethics approval required @@ -408,7 +942,7 @@ We also have the outstanding issue of how to aim different definitions to differ geographical restriction This requirement indicates that use is limited to within a specific geographic region. DUO:0000022 - GS-[XX] + GS This should be coupled with an ontology term describing the geographical location the restriction applies to. geographical restriction @@ -423,7 +957,7 @@ We also have the outstanding issue of how to aim different definitions to differ This requirement indicates that requestor agrees not to publish results of studies until a specific date publication embargo DUO:0000024 - MOR-[XX] + MOR This should be coupled with a date specified as ISO8601 publication moratorium @@ -437,7 +971,7 @@ We also have the outstanding issue of how to aim different definitions to differ time limit on use This requirement indicates that use is approved for a specific number of months. DUO:0000025 - TS-[XX] + TS This should be coupled with an integer value indicating the number of months. time limit on use @@ -451,7 +985,7 @@ We also have the outstanding issue of how to aim different definitions to differ user-specific restriction This requirement indicates that use is limited to use by approved users. DUO:0000026 - US + US user specific restriction @@ -464,7 +998,7 @@ We also have the outstanding issue of how to aim different definitions to differ project-specific restriction This requirement indicates that use is limited to use within an approved project. DUO:0000027 - PS + PS project specific restriction @@ -477,7 +1011,7 @@ We also have the outstanding issue of how to aim different definitions to differ institution-specific restriction This requirement indicates that use is limited to use within an approved institution. DUO:0000028 - IS + IS institution specific restriction @@ -503,7 +1037,7 @@ We also have the outstanding issue of how to aim different definitions to differ method development An investigation concerning development of methods, algorithms, software or analytical tools. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000031 + DUO:0000031 method development @@ -516,7 +1050,7 @@ We also have the outstanding issue of how to aim different definitions to differ population research An investigation concerning a specific population group. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000032 + DUO:0000032 Should be paired with the an ontology term representing this population (e.g., xxx). population research @@ -530,7 +1064,7 @@ We also have the outstanding issue of how to aim different definitions to differ ancestry research An investigation concerning ancestry or population origins. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000033 + DUO:0000033 ancestry research @@ -543,7 +1077,7 @@ We also have the outstanding issue of how to aim different definitions to differ age category research An investigation concerning specific age categories. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000034 + DUO:0000034 Should be paired with the an ontology term representing this population (e.g., xxx). age category research @@ -557,7 +1091,7 @@ We also have the outstanding issue of how to aim different definitions to differ gender category research An investigation concerning specific gender categories. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000035 + DUO:0000035 Should be paired with the an ontology term representing this population (e.g., xxx). gender category research @@ -571,7 +1105,7 @@ We also have the outstanding issue of how to aim different definitions to differ research control An investigation concerning use of data as reference or control material. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000036 + DUO:0000036 research control @@ -584,7 +1118,7 @@ We also have the outstanding issue of how to aim different definitions to differ biomedical research An investigation concerning health, medical, or biomedical research. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000037 + DUO:0000037 biomedical research @@ -597,7 +1131,7 @@ We also have the outstanding issue of how to aim different definitions to differ genetic research Biomedical research concerning genetics (i.e., the study of genes, genetic variations and heredity). This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000038 + DUO:0000038 genetic research @@ -610,7 +1144,7 @@ We also have the outstanding issue of how to aim different definitions to differ drug development research Biomedical research concerning drug development. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000039 + DUO:0000039 drug development research @@ -623,7 +1157,7 @@ We also have the outstanding issue of how to aim different definitions to differ disease category research Biomedical research research concerning specific disease/s This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000040 + DUO:0000040 disease category research @@ -632,11 +1166,11 @@ We also have the outstanding issue of how to aim different definitions to differ - + general research use - This primary category consent code indicates that use is allowed for general research use for any research purpose. + This data use limitation indicates that use is allowed for general research use for any research purpose. DUO:0000042 - GRU + GRU This includes but is not limited to: health/medical/biomedical purposes, fundamental biology research, the study of population origins or ancestry, statistical methods and algorithms development, and social-sciences research. general research use diff --git a/duo.csv b/duo.csv index cbf031b..e46a0bd 100644 --- a/duo.csv +++ b/duo.csv @@ -1,36 +1,21 @@ -id,label,description -DUO:0000021,ethics approval required,This requirement indicates that the requestor must provide documentation of local IRB/ERB approval. -DUO_0000034,age category research,An investigation concerning specific age categories. -DUO:0000006,health or medical or biomedical research,This primary category consent code indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry. -DUO:0000019,publication required,This requirement indicates that requestor agrees to make results of studies using the data available to the larger scientific community. -DUO:0000026,user specific restriction,This requirement indicates that use is limited to use by approved users. -DUO_0000039,drug development research,Biomedical research concerning drug development. -DUO:0000020,collaboration required,This requirement indicates that the requestor must agree to collaboration with the primary study investigator(s). -DUO_0000033,ancestry research,An investigation concerning ancestry or population origins. -DUO:0000005,general research use and clinical care,"This primary category consent code indicates that use is allowed for health/medical/biomedical purposes and other biological research, including the study of population origins or ancestry." -DUO:0000018,not for profit use only,"This requirement indicates that use of the data is limited to not-for-profit organizations and not-for-profit use, non-commercial use." -DUO_0000040,disease category research,Biomedical research research concerning specific disease/s -DUO:0000012,research specific restrictions,This secondary category consent code indicates that use is limited to studies of a certain research type. -DUO:0000025,time limit on use,This requirement indicates that use is approved for a specific number of months. -DUO_0000038,genetic research,"Biomedical research concerning genetics (i.e., the study of genes, genetic variations and heredity)." -DUO_0000032,population research,An investigation concerning a specific population group. -DUO:0000004,no restriction,This consent code primary category indicates there is no restriction on use. -DUO:0000017,data use requirements,Requirements indicate additional conditions set for use. -DUO:0000011,population origins or ancestry research,This primary category consent code indicates that use of the data is limited to the study of population origins or ancestry. -DUO:0000024,publication moratorium,This requirement indicates that requestor agrees not to publish results of studies until a specific date -DUO_0000037,biomedical research,"An investigation concerning health, medical, or biomedical research." -DUO_0000031,method development,"An investigation concerning development of methods, algorithms, software or analytical tools." -DUO:0000003,consent code secondary category,A categorical data item indicating the secondary category the consent code belongs to according to Dyke et al. 2016. -DUO:0000016,genetic studies only,"This secondary category consent code indicates that use is limited to genetic studies only (i.e., no phenotype-only research)" -DUO:0000029,return to database or resource,This requirement indicates that the requestor must return derived/enriched data to the database/resource. -DUO_0000036,research control,An investigation concerning use of data as reference or control material. -DUO:0000002,consent code primary category,A categorical data item indicating the primary category the consent code belongs to according to Dyke et al. 2016. -DUO:0000015,no general methods research,"This secondary category consent code indicates that use includes methods development research(e.g., development of software or algorithms) only within the bounds of other use limitations." -DUO:0000028,institution specific restriction,This requirement indicates that use is limited to use within an approved institution. -DUO:0000022,geographical restriction,This requirement indicates that use is limited to within a specific geographic region. -DUO_0000035,gender category research,An investigation concerning specific gender categories. -DUO:0000007,disease specific research,This primary category consent code indicates that use is allowed provided it is related to the specified disease. -DUO:0000001,consent code,"A data item that is used to indicate consent permissions for datasets and/or materials, and relates to the purposes for which datasets and/or material might be removed, stored or used." -DUO:0000042,general research use,This primary category consent code indicates that use is allowed for general research use for any research purpose. -DUO:0000014,research use only,"This secondary category consent code indicates that use is limited to research purposes (e.g., does not include its use in clinical care)." -DUO:0000027,project specific restriction,This requirement indicates that use is limited to use within an approved project. +id,shorthand,label,description +DUO:0000021,IRB,ethics approval required,This requirement indicates that the requestor must provide documentation of local IRB/ERB approval. +DUO:0000006,HMB,health or medical or biomedical research,This data use limitation indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry. +DUO:0000019,PUB,publication required,This requirement indicates that requestor agrees to make results of studies using the data available to the larger scientific community. +DUO:0000026,US,user specific restriction,This requirement indicates that use is limited to use by approved users. +DUO:0000020,COL,collaboration required,This requirement indicates that the requestor must agree to collaboration with the primary study investigator(s). +DUO:0000005,GRU-CC,general research use and clinical care,"This data use limitation indicates that use is allowed for health/medical/biomedical purposes and other biological research, including the study of population origins or ancestry." +DUO:0000018,NPU,not for profit use only,"This requirement indicates that use of the data is limited to not-for-profit organizations and not-for-profit use, non-commercial use." +DUO:0000012,RS,research specific restrictions,This data use limitation indicates that use is limited to studies of a certain research type. +DUO:0000025,TS,time limit on use,This requirement indicates that use is approved for a specific number of months. +DUO:0000004,NRES,no restriction,This data use limitation indicates there is no restriction on use. +DUO:0000011,POA,population origins or ancestry research,This data use limitation indicates that use of the data is limited to the study of population origins or ancestry. +DUO:0000024,MOR,publication moratorium,This requirement indicates that requestor agrees not to publish results of studies until a specific date +DUO:0000016,GSO,genetic studies only,"This data use limitation indicates that use is limited to genetic studies only (i.e., no phenotype-only research)" +DUO:0000029,RTN,return to database or resource,This requirement indicates that the requestor must return derived/enriched data to the database/resource. +DUO:0000028,IS,institution specific restriction,This requirement indicates that use is limited to use within an approved institution. +DUO:0000022,GS,geographical restriction,This requirement indicates that use is limited to within a specific geographic region. +DUO:0000007,DS,disease specific research,This data use limitation indicates that use is allowed provided it is related to the specified disease. +DUO:0000042,GRU,general research use,This data use limitation indicates that use is allowed for general research use for any research purpose. +DUO:0000014,RU,research use only,"This data use limitation indicates that use is limited to research purposes (e.g., does not include its use in clinical care)." +DUO:0000027,PS,project specific restriction,This requirement indicates that use is limited to use within an approved project. diff --git a/duo.owl b/duo.owl index ff99579..015981a 100644 --- a/duo.owl +++ b/duo.owl @@ -9,10 +9,11 @@ xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" + xmlns:dcterms="dcterms:" xmlns:protege="http://protege.stanford.edu/plugins/owl/protege#" xmlns:oboInOwl="http://www.geneontology.org/formats/oboInOwl#"> - + Cooper Stansbury David An @@ -396,10 +397,11 @@ - consent code + data use limitation A data item that is used to indicate consent permissions for datasets and/or materials, and relates to the purposes for which datasets and/or material might be removed, stored or used. + consent code DUO:0000001 - consent code + data use limitation @@ -407,11 +409,13 @@ - - consent code primary category + A categorical data item indicating the primary category the consent code belongs to according to Dyke et al. 2016. + This term was depreacted as it is not used to tag datasets but instead as patterns for DUO codes capture. This is an archive specific requirement, e.g. "one code from a primary category and one or more from a second category' +This is better done by Schemablocks and constraining the pattern of usage of DUO terms at each archive level. DUO:0000002 - consent code primary category + obsolete consent code primary category + true @@ -419,11 +423,13 @@ - - consent code secondary category + A categorical data item indicating the secondary category the consent code belongs to according to Dyke et al. 2016. + This term was depreacted as it is not used to tag datasets but instead as patterns for DUO codes capture. This is an archive specific requirement, e.g. "one code from a primary category and one or more from a second category' +This is better done by Schemablocks and constraining the pattern of usage of DUO terms at each archive level. DUO:0000003 - consent code secondary category + obsolete consent code secondary category + true @@ -431,11 +437,11 @@ - + no restriction - This consent code primary category indicates there is no restriction on use. + This data use limitation indicates there is no restriction on use. DUO:0000004 - NRES + NRES 20180907, Meeting Moran Melanie: This is to be thought about more carefully - what is the intent when using 'no restriction' as usually users still need to be researchers. Note: the NRES alternative term may be confusing as in the UK it also stands for National Research Ethics Service no restriction @@ -448,9 +454,10 @@ general research use and clinical care - This primary category consent code indicates that use is allowed for health/medical/biomedical purposes and other biological research, including the study of population origins or ancestry. + This data use limitation indicates that use is allowed for health/medical/biomedical purposes and other biological research, including the study of population origins or ancestry. DUO:0000005 - GRU-CC + GRU-CC + This term includes clinical care, which was not defined in the original consent codes paper. This term does not have a usage in our current use cases and we recommend using DUO:0000042, General Research Use, instead general research use and clinical care @@ -459,11 +466,11 @@ - + health/medical/biomedical research - This primary category consent code indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry. + This data use limitation indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry. DUO:0000006 - HMB + HMB health or medical or biomedical research @@ -480,9 +487,9 @@ disease-specific research - This primary category consent code indicates that use is allowed provided it is related to the specified disease. + This data use limitation indicates that use is allowed provided it is related to the specified disease. DUO:0000007 - DS + DS This term should be coupled with a term describing a disease from an ontology, such as the Disease Ontology, HPO, MonDO to specify the disease the restriction applies to. disease specific research @@ -492,12 +499,12 @@ - + population origins or ancestry research - This primary category consent code indicates that use of the data is limited to the study of population origins or ancestry. + This data use limitation indicates that use of the data is limited to the study of population origins or ancestry. population origins/ancestry research DUO:0000011 - POA + POA population origins or ancestry research @@ -506,7 +513,7 @@ - + @@ -514,9 +521,9 @@ research-specific restrictions - This secondary category consent code indicates that use is limited to studies of a certain research type. + This data use limitation indicates that use is limited to studies of a certain research type. DUO:0000012 - RS + RS research specific restrictions @@ -525,11 +532,11 @@ - + research use only - This secondary category consent code indicates that use is limited to research purposes (e.g., does not include its use in clinical care). + This data use limitation indicates that use is limited to research purposes (e.g., does not include its use in clinical care). DUO:0000014 - RU + RU research use only @@ -538,9 +545,9 @@ - + no general methods research - This secondary category consent code indicates that use includes methods development research(e.g., development of software or algorithms) only within the bounds of other use limitations. + This data use limitation indicates that use includes methods development research(e.g., development of software or algorithms) only within the bounds of other use limitations. DUO:0000015 no general methods research @@ -550,11 +557,11 @@ - + genetic studies only - This secondary category consent code indicates that use is limited to genetic studies only (i.e., no phenotype-only research) + This data use limitation indicates that use is limited to genetic studies only (i.e., no phenotype-only research) DUO:0000016 - GSO + GSO genetic studies only @@ -580,7 +587,7 @@ This requirement indicates that use of the data is limited to not-for-profit organizations and not-for-profit use, non-commercial use. non-commercial use DUO:0000018 - NPU + NPU not for profit use only @@ -593,7 +600,7 @@ publication required This requirement indicates that requestor agrees to make results of studies using the data available to the larger scientific community. DUO:0000019 - PUB + PUB publication required @@ -606,7 +613,7 @@ collaboration required This requirement indicates that the requestor must agree to collaboration with the primary study investigator(s). DUO:0000020 - COL + COL This could be coupled with a string describing the primary study investigator(s). collaboration required @@ -620,7 +627,7 @@ ethics approval required This requirement indicates that the requestor must provide documentation of local IRB/ERB approval. DUO:0000021 - IRB + IRB ethics approval required @@ -639,7 +646,7 @@ geographical restriction This requirement indicates that use is limited to within a specific geographic region. DUO:0000022 - GS-[XX] + GS This should be coupled with an ontology term describing the geographical location the restriction applies to. geographical restriction @@ -654,7 +661,7 @@ This requirement indicates that requestor agrees not to publish results of studies until a specific date publication embargo DUO:0000024 - MOR-[XX] + MOR This should be coupled with a date specified as ISO8601 publication moratorium @@ -668,7 +675,7 @@ time limit on use This requirement indicates that use is approved for a specific number of months. DUO:0000025 - TS-[XX] + TS This should be coupled with an integer value indicating the number of months. time limit on use @@ -682,7 +689,7 @@ user-specific restriction This requirement indicates that use is limited to use by approved users. DUO:0000026 - US + US user specific restriction @@ -695,7 +702,7 @@ project-specific restriction This requirement indicates that use is limited to use within an approved project. DUO:0000027 - PS + PS project specific restriction @@ -708,7 +715,7 @@ institution-specific restriction This requirement indicates that use is limited to use within an approved institution. DUO:0000028 - IS + IS institution specific restriction @@ -734,7 +741,7 @@ method development An investigation concerning development of methods, algorithms, software or analytical tools. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000031 + DUO:0000031 method development @@ -747,7 +754,7 @@ population research An investigation concerning a specific population group. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000032 + DUO:0000032 Should be paired with the an ontology term representing this population (e.g., xxx). population research @@ -761,7 +768,7 @@ ancestry research An investigation concerning ancestry or population origins. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000033 + DUO:0000033 ancestry research @@ -774,7 +781,7 @@ age category research An investigation concerning specific age categories. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000034 + DUO:0000034 Should be paired with the an ontology term representing this population (e.g., xxx). age category research @@ -788,7 +795,7 @@ gender category research An investigation concerning specific gender categories. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000035 + DUO:0000035 Should be paired with the an ontology term representing this population (e.g., xxx). gender category research @@ -802,7 +809,7 @@ research control An investigation concerning use of data as reference or control material. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000036 + DUO:0000036 research control @@ -815,7 +822,7 @@ biomedical research An investigation concerning health, medical, or biomedical research. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000037 + DUO:0000037 biomedical research @@ -828,7 +835,7 @@ genetic research Biomedical research concerning genetics (i.e., the study of genes, genetic variations and heredity). This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000038 + DUO:0000038 genetic research @@ -841,7 +848,7 @@ drug development research Biomedical research concerning drug development. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000039 + DUO:0000039 drug development research @@ -854,7 +861,7 @@ disease category research Biomedical research research concerning specific disease/s This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000040 + DUO:0000040 disease category research @@ -863,11 +870,11 @@ - + general research use - This primary category consent code indicates that use is allowed for general research use for any research purpose. + This data use limitation indicates that use is allowed for general research use for any research purpose. DUO:0000042 - GRU + GRU This includes but is not limited to: health/medical/biomedical purposes, fundamental biology research, the study of population origins or ancestry, statistical methods and algorithms development, and social-sciences research. general research use @@ -2220,6 +2227,174 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2252,10 +2427,26 @@ + + + + + + + + + + + + + + + + - + @@ -2263,11 +2454,35 @@ + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/src/ontology/duo-basic.owl b/src/ontology/duo-basic.owl new file mode 100644 index 0000000..93d89b3 --- /dev/null +++ b/src/ontology/duo-basic.owl @@ -0,0 +1,1193 @@ + + + + + + + + + + + + + + + + + + + + + + + Relates an entity in the ontology to the name of the variable that is used to represent it in the code that generates the BFO OWL file from the lispy specification. + Really of interest to developers only + BFO OWL specification label + + + + + + + + + Relates an entity in the ontology to the term that is used to represent it in the the CLIF specification of BFO2 + Person:Alan Ruttenberg + Really of interest to developers only + BFO CLIF specification label + + + + + + + + + DUO_preferred_label + + + + + + + + editor preferred label + editor preferred label + editor preferred term + editor preferred term + editor preferred term~editor preferred label + + The concise, meaningful, and human-friendly name for a class or property preferred by the ontology developers. (US-English) + PERSON:Daniel Schober + GROUP:OBI:<http://purl.obolibrary.org/obo/obi> + + editor preferred label + editor preferred label + editor preferred term + editor preferred term + editor preferred term~editor preferred label + + + + + + + + example + + A phrase describing how a term should be used and/or a citation to a work which uses it. May also include other kinds of examples that facilitate immediate understanding, such as widely know prototypes or instances of a class, or cases where a relation is said to hold. + PERSON:Daniel Schober + GROUP:OBI:<http://purl.obolibrary.org/obo/obi> + + example of usage + + + + + + + + in branch + An annotation property indicating which module the terms belong to. This is currently experimental and not implemented yet. + GROUP:OBI + OBI_0000277 + in branch + + + + + + + + has curation status + PERSON:Alan Ruttenberg + PERSON:Bill Bug + PERSON:Melanie Courtot + OBI_0000281 + has curation status + + + + + + + + definition + definition + textual definition + + The official OBI definition, explaining the meaning of a class or property. Shall be Aristotelian, formalized and normalized. Can be augmented with colloquial definitions. + The official definition, explaining the meaning of a class or property. Shall be Aristotelian, formalized and normalized. Can be augmented with colloquial definitions. + 2012-04-05: +Barry Smith + +The official OBI definition, explaining the meaning of a class or property: 'Shall be Aristotelian, formalized and normalized. Can be augmented with colloquial definitions' is terrible. + +Can you fix to something like: + +A statement of necessary and sufficient conditions explaining the meaning of an expression referring to a class or property. + +Alan Ruttenberg + +Your proposed definition is a reasonable candidate, except that it is very common that necessary and sufficient conditions are not given. Mostly they are necessary, occasionally they are necessary and sufficient or just sufficient. Often they use terms that are not themselves defined and so they effectively can't be evaluated by those criteria. + +On the specifics of the proposed definition: + +We don't have definitions of 'meaning' or 'expression' or 'property'. For 'reference' in the intended sense I think we use the term 'denotation'. For 'expression', I think we you mean symbol, or identifier. For 'meaning' it differs for class and property. For class we want documentation that let's the intended reader determine whether an entity is instance of the class, or not. For property we want documentation that let's the intended reader determine, given a pair of potential relata, whether the assertion that the relation holds is true. The 'intended reader' part suggests that we also specify who, we expect, would be able to understand the definition, and also generalizes over human and computer reader to include textual and logical definition. + +Personally, I am more comfortable weakening definition to documentation, with instructions as to what is desirable. + +We also have the outstanding issue of how to aim different definitions to different audiences. A clinical audience reading chebi wants a different sort of definition documentation/definition from a chemistry trained audience, and similarly there is a need for a definition that is adequate for an ontologist to work with. + PERSON:Daniel Schober + GROUP:OBI:<http://purl.obolibrary.org/obo/obi> + + definition + definition + textual definition + + + + + + + + editor note + + An administrative note intended for its editor. It may not be included in the publication version of the ontology, so it should contain nothing necessary for end users to understand the ontology. + PERSON:Daniel Schober + GROUP:OBI:<http://purl.obfoundry.org/obo/obi> + + editor note + + + + + + + + term editor + + Name of editor entering the term in the file. The term editor is a point of contact for information regarding the term. The term editor may be, but is not always, the author of the definition, which may have been worked upon by several people + 20110707, MC: label update to term editor and definition modified accordingly. See https://github.com/information-artifact-ontology/IAO/issues/115. + PERSON:Daniel Schober + GROUP:OBI:<http://purl.obolibrary.org/obo/obi> + + term editor + + + + + + + + alternative term + + An alternative name for a class or property which means the same thing as the preferred name (semantically equivalent) + PERSON:Daniel Schober + GROUP:OBI:<http://purl.obolibrary.org/obo/obi> + + alternative term + + + + + + + + definition source + + formal citation, e.g. identifier in external database to indicate / attribute source(s) for the definition. Free text indicate / attribute source(s) for the definition. EXAMPLE: Author Name, URI, MeSH Term C04, PUBMED ID, Wiki uri on 31.01.2007 + PERSON:Daniel Schober + Discussion on obo-discuss mailing-list, see http://bit.ly/hgm99w + GROUP:OBI:<http://purl.obolibrary.org/obo/obi> + + definition source + + + + + + + + has obsolescence reason + Relates an annotation property to an obsolescence reason. The values of obsolescence reasons come from a list of predefined terms, instances of the class obsolescence reason specification. + PERSON:Alan Ruttenberg + PERSON:Melanie Courtot + has obsolescence reason + + + + + + + + curator note + + An administrative note of use for a curator but of no use for a user + PERSON:Alan Ruttenberg + + curator note + + + + + + + + term tracker item + the URI for an OBI Terms ticket at sourceforge, such as https://sourceforge.net/p/obi/obi-terms/772/ + + An IRI or similar locator for a request or discussion of an ontology term. + Person: Jie Zheng, Chris Stoeckert, Alan Ruttenberg + Person: Jie Zheng, Chris Stoeckert, Alan Ruttenberg + The 'tracker item' can associate a tracker with a specific ontology term. + term tracker item + + + + + + + + + The name of the person, project, or organization that motivated inclusion of an ontology term by requesting its addition. + Person: Jie Zheng, Chris Stoeckert, Alan Ruttenberg + Person: Jie Zheng, Chris Stoeckert, Alan Ruttenberg + The 'term requester' can credit the person, organization or project who request the ontology term. + ontology term requester + + + + + + + + is denotator type + relates an class defined in an ontology, to the type of it's denotator + In OWL 2 add AnnotationPropertyRange('is denotator type' 'denotator type') + Alan Ruttenberg + is denotator type + + + + + + + + imported from + + For external terms/classes, the ontology from which the term was imported + PERSON:Alan Ruttenberg + PERSON:Melanie Courtot + GROUP:OBI:<http://purl.obolibrary.org/obo/obi> + + imported from + + + + + + + + expand expression to + ObjectProperty: RO_0002104 +Label: has plasma membrane part +Annotations: IAO_0000424 "http://purl.obolibrary.org/obo/BFO_0000051 some (http://purl.org/obo/owl/GO#GO_0005886 and http://purl.obolibrary.org/obo/BFO_0000051 some ?Y)" + + A macro expansion tag applied to an object property (or possibly a data property) which can be used by a macro-expansion engine to generate more complex expressions from simpler ones + Chris Mungall + expand expression to + + + + + + + + expand assertion to + ObjectProperty: RO??? +Label: spatially disjoint from +Annotations: expand_assertion_to "DisjointClasses: (http://purl.obolibrary.org/obo/BFO_0000051 some ?X) (http://purl.obolibrary.org/obo/BFO_0000051 some ?Y)" + + A macro expansion tag applied to an annotation property which can be expanded into a more detailed axiom. + Chris Mungall + expand assertion to + + + + + + + + first order logic expression + PERSON:Alan Ruttenberg + first order logic expression + + + + + + + + antisymmetric property + part_of antisymmetric property xsd:true + use boolean value xsd:true to indicate that the property is an antisymmetric property + Alan Ruttenberg + antisymmetric property + + + + + + + + OBO foundry unique label + + An alternative name for a class or property which is unique across the OBO Foundry. + The intended usage of that property is as follow: OBO foundry unique labels are automatically generated based on regular expressions provided by each ontology, so that SO could specify unique label = 'sequence ' + [label], etc. , MA could specify 'mouse + [label]' etc. Upon importing terms, ontology developers can choose to use the 'OBO foundry unique label' for an imported term or not. The same applies to tools . + PERSON:Alan Ruttenberg + PERSON:Bjoern Peters + PERSON:Chris Mungall + PERSON:Melanie Courtot + GROUP:OBO Foundry <http://obofoundry.org/> + OBO foundry unique label + + + + + + + + Ontology: <http://purl.obolibrary.org/obo/ro/idrange/> + Annotations: + 'has ID prefix': "http://purl.obolibrary.org/obo/RO_" + 'has ID digit count' : 7, + rdfs:label "RO id policy" + 'has ID policy for': "RO" + Relates an ontology used to record id policy to the number of digits in the URI. The URI is: the 'has ID prefix" annotation property value concatenated with an integer in the id range (left padded with "0"s to make this many digits) + Person:Alan Ruttenberg + has ID digit count + + + + + + + + Datatype: idrange:1 +Annotations: 'has ID range allocated to': "Chris Mungall" +EquivalentTo: xsd:integer[> 2151 , <= 2300] + + Relates a datatype that encodes a range of integers to the name of the person or organization who can use those ids constructed in that range to define new terms + Person:Alan Ruttenberg + has ID range allocated to + + + + + + + + Ontology: <http://purl.obolibrary.org/obo/ro/idrange/> + Annotations: + 'has ID prefix': "http://purl.obolibrary.org/obo/RO_" + 'has ID digit count' : 7, + rdfs:label "RO id policy" + 'has ID policy for': "RO" + Relating an ontology used to record id policy to the ontology namespace whose policy it manages + Person:Alan Ruttenberg + has ID policy for + + + + + + + + Ontology: <http://purl.obolibrary.org/obo/ro/idrange/> + Annotations: + 'has ID prefix': "http://purl.obolibrary.org/obo/RO_" + 'has ID digit count' : 7, + rdfs:label "RO id policy" + 'has ID policy for': "RO" + Relates an ontology used to record id policy to a prefix concatenated with an integer in the id range (left padded with "0"s to make this many digits) to construct an ID for a term being created. + Person:Alan Ruttenberg + has ID prefix + + + + + + + + elucidation + person:Alan Ruttenberg + Person:Barry Smith + Primitive terms in a highest-level ontology such as BFO are terms which are so basic to our understanding of reality that there is no way of defining them in a non-circular fashion. For these, therefore, we can provide only elucidations, supplemented by examples and by axioms + + elucidation + + + + + + + + has associated axiom(nl) + Person:Alan Ruttenberg + Person:Alan Ruttenberg + An axiom associated with a term expressed using natural language + + has associated axiom(nl) + + + + + + + + has associated axiom(fol) + Person:Alan Ruttenberg + Person:Alan Ruttenberg + An axiom expressed in first order logic using CLIF syntax + + has associated axiom(fol) + + + + + + + + is allocated id range + Add as annotation triples in the granting ontology + Relates an ontology IRI to an (inclusive) range of IRIs in an OBO name space. The range is give as, e.g. "IAO_0020000-IAO_0020999" + PERSON:Alan Ruttenberg + is allocated id range + + + + + + + + retired from use as of + relates a class of CRID to the date after which further instances should not be made, according to the central authority + In OWL 2 add AnnotationPropertyRange xsd:dateTimeStamp + Alan Ruttenberg + retired from use as of + + + + + + + + A annotation relationship between two terms in an ontology that may refer to the same (natural) type but where more evidence is required before terms are merged. + David Osumi-Sutherland + #40 + VFB + 2018-09-21T16:43:39Z + Edges asserting this should be annotated with to record evidence supporting the assertion and its provenance. + may be identical to + + + + + + + + Used when the class or object is scheduled for obsoletion/deprecation on or after a particular date. + Chris Mungall, Jie Zheng + https://github.com/geneontology/go-ontology/issues/15532 + https://github.com/information-artifact-ontology/ontology-metadata/issues/32 + GO ontology + scheduled for obsoletion on or after + + + + + + + + + has axiom id + Person:Alan Ruttenberg + Person:Alan Ruttenberg + A URI that is intended to be unique label for an axiom used for tracking change to the ontology. For an axiom expressed in different languages, each expression is given the same URI + + has axiom label + + + + + + + + term replaced by + + Add as annotation triples in the granting ontology + Use on obsolete terms, relating the term to another term that can be used as a substitute + Person:Alan Ruttenberg + Person:Alan Ruttenberg + term replaced by + + + + + + + + An assertion that holds between an OWL Object Property and a temporal interpretation that elucidates how OWL Class Axioms that use this property are to be interpreted in a temporal context. + temporal interpretation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + label + label + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + data use limitation + A data item that is used to indicate consent permissions for datasets and/or materials, and relates to the purposes for which datasets and/or material might be removed, stored or used. + consent code + DUO:0000001 + data use limitation + + + + + + + + + no restriction + This data use limitation indicates there is no restriction on use. + DUO:0000004 + NRES + 20180907, Meeting Moran Melanie: This is to be thought about more carefully - what is the intent when using 'no restriction' as usually users still need to be researchers. + Note: the NRES alternative term may be confusing as in the UK it also stands for National Research Ethics Service + no restriction + + + + + + + + + general research use and clinical care + This data use limitation indicates that use is allowed for health/medical/biomedical purposes and other biological research, including the study of population origins or ancestry. + DUO:0000005 + GRU-CC + This term includes clinical care, which was not defined in the original consent codes paper. This term does not have a usage in our current use cases and we recommend using DUO:0000042, General Research Use, instead + general research use and clinical care + + + + + + + + + health/medical/biomedical research + This data use limitation indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry. + DUO:0000006 + HMB + health or medical or biomedical research + + + + + + + + + disease-specific research + This data use limitation indicates that use is allowed provided it is related to the specified disease. + DUO:0000007 + DS + This term should be coupled with a term describing a disease from an ontology, such as the Disease Ontology, HPO, MonDO to specify the disease the restriction applies to. + disease specific research + + + + + + + + + population origins or ancestry research + This data use limitation indicates that use of the data is limited to the study of population origins or ancestry. + population origins/ancestry research + DUO:0000011 + POA + population origins or ancestry research + + + + + + + + + research-specific restrictions + This data use limitation indicates that use is limited to studies of a certain research type. + DUO:0000012 + RS + research specific restrictions + + + + + + + + + research use only + This data use limitation indicates that use is limited to research purposes (e.g., does not include its use in clinical care). + DUO:0000014 + RU + research use only + + + + + + + + + no general methods research + This data use limitation indicates that use includes methods development research(e.g., development of software or algorithms) only within the bounds of other use limitations. + DUO:0000015 + no general methods research + + + + + + + + + genetic studies only + This data use limitation indicates that use is limited to genetic studies only (i.e., no phenotype-only research) + DUO:0000016 + GSO + genetic studies only + + + + + + + + data use requirements + Requirements indicate additional conditions set for use. + DUO:0000017 + data use requirements + + + + + + + + + not-for-profit use only + This requirement indicates that use of the data is limited to not-for-profit organizations and not-for-profit use, non-commercial use. + non-commercial use + DUO:0000018 + NPU + not for profit use only + + + + + + + + + publication required + This requirement indicates that requestor agrees to make results of studies using the data available to the larger scientific community. + DUO:0000019 + PUB + publication required + + + + + + + + + collaboration required + This requirement indicates that the requestor must agree to collaboration with the primary study investigator(s). + DUO:0000020 + COL + This could be coupled with a string describing the primary study investigator(s). + collaboration required + + + + + + + + + ethics approval required + This requirement indicates that the requestor must provide documentation of local IRB/ERB approval. + DUO:0000021 + IRB + ethics approval required + + + + + + + + + geographical restriction + This requirement indicates that use is limited to within a specific geographic region. + DUO:0000022 + GS + This should be coupled with an ontology term describing the geographical location the restriction applies to. + geographical restriction + + + + + + + + + publication moratorium + This requirement indicates that requestor agrees not to publish results of studies until a specific date + publication embargo + DUO:0000024 + MOR + This should be coupled with a date specified as ISO8601 + publication moratorium + + + + + + + + + time limit on use + This requirement indicates that use is approved for a specific number of months. + DUO:0000025 + TS + This should be coupled with an integer value indicating the number of months. + time limit on use + + + + + + + + + user-specific restriction + This requirement indicates that use is limited to use by approved users. + DUO:0000026 + US + user specific restriction + + + + + + + + + project-specific restriction + This requirement indicates that use is limited to use within an approved project. + DUO:0000027 + PS + project specific restriction + + + + + + + + + institution-specific restriction + This requirement indicates that use is limited to use within an approved institution. + DUO:0000028 + IS + institution specific restriction + + + + + + + + + return to database/resource + This requirement indicates that the requestor must return derived/enriched data to the database/resource. + DUO:0000029 + RTN + return to database or resource + + + + + + + + + method development + An investigation concerning development of methods, algorithms, software or analytical tools. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000031 + method development + + + + + + + + + population research + An investigation concerning a specific population group. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000032 + Should be paired with the an ontology term representing this population (e.g., xxx). + population research + + + + + + + + + ancestry research + An investigation concerning ancestry or population origins. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000033 + ancestry research + + + + + + + + + age category research + An investigation concerning specific age categories. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000034 + Should be paired with the an ontology term representing this population (e.g., xxx). + age category research + + + + + + + + + gender category research + An investigation concerning specific gender categories. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000035 + Should be paired with the an ontology term representing this population (e.g., xxx). + gender category research + + + + + + + + + research control + An investigation concerning use of data as reference or control material. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000036 + research control + + + + + + + + + biomedical research + An investigation concerning health, medical, or biomedical research. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000037 + biomedical research + + + + + + + + + genetic research + Biomedical research concerning genetics (i.e., the study of genes, genetic variations and heredity). + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000038 + genetic research + + + + + + + + + drug development research + Biomedical research concerning drug development. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000039 + drug development research + + + + + + + + + disease category research + Biomedical research research concerning specific disease/s + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000040 + disease category research + + + + + + + + + general research use + This data use limitation indicates that use is allowed for general research use for any research purpose. + DUO:0000042 + GRU + This includes but is not limited to: health/medical/biomedical purposes, fundamental biology research, the study of population origins or ancestry, statistical methods and algorithms development, and social-sciences research. + general research use + + + + + + + + investigation + a planned process that consists of parts: planning, study design execution, documentation and which produce conclusion(s). + + investigation + + + + + + + diff --git a/src/ontology/duo-edit.owl b/src/ontology/duo-edit.owl index 1502c80..e93205e 100644 --- a/src/ontology/duo-edit.owl +++ b/src/ontology/duo-edit.owl @@ -1,26 +1,27 @@ + xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" + xmlns:dcterms="dcterms:" + xmlns:protege="http://protege.stanford.edu/plugins/owl/protege#" + xmlns:oboInOwl="http://www.geneontology.org/formats/oboInOwl#"> - Stephanie Dyke - Giselle Kerry - Moran Ncabili - J. Neil Otte - Gregory Rushton - David An Cooper Stansbury + David An Dylan Spalding + Giselle Kerry + Gregory Rushton + J. Neil Otte + Moran Ncabili + Stephanie Dyke Melanie Courtot @@ -43,11 +44,18 @@ DUO_preferred_label - - + + + + + + + + + - @@ -101,10 +108,11 @@ - consent code + data use limitation A data item that is used to indicate consent permissions for datasets and/or materials, and relates to the purposes for which datasets and/or material might be removed, stored or used. + consent code DUO:0000001 - consent code + data use limitation @@ -112,11 +120,13 @@ - - consent code primary category + A categorical data item indicating the primary category the consent code belongs to according to Dyke et al. 2016. + This term was depreacted as it is not used to tag datasets but instead as patterns for DUO codes capture. This is an archive specific requirement, e.g. "one code from a primary category and one or more from a second category' +This is better done by Schemablocks and constraining the pattern of usage of DUO terms at each archive level. DUO:0000002 - consent code primary category + obsolete consent code primary category + true @@ -124,11 +134,13 @@ - - consent code secondary category + A categorical data item indicating the secondary category the consent code belongs to according to Dyke et al. 2016. + This term was depreacted as it is not used to tag datasets but instead as patterns for DUO codes capture. This is an archive specific requirement, e.g. "one code from a primary category and one or more from a second category' +This is better done by Schemablocks and constraining the pattern of usage of DUO terms at each archive level. DUO:0000003 - consent code secondary category + obsolete consent code secondary category + true @@ -136,11 +148,11 @@ - + no restriction - This consent code primary category indicates there is no restriction on use. + This data use limitation indicates there is no restriction on use. DUO:0000004 - NRES + NRES 20180907, Meeting Moran Melanie: This is to be thought about more carefully - what is the intent when using 'no restriction' as usually users still need to be researchers. Note: the NRES alternative term may be confusing as in the UK it also stands for National Research Ethics Service no restriction @@ -153,10 +165,11 @@ general research use and clinical care - This primary category consent code indicates that use is allowed for health/medical/biomedical purposes and other biological research, including the study of population origins or ancestry. + This data use limitation indicates that use is allowed for health/medical/biomedical purposes and other biological research, including the study of population origins or ancestry. DUO:0000005 - GRU-CC - general research use and clinical care + GRU-CC + This term includes clinical care, which was not defined in the original consent codes paper. This term does not have a usage in our current use cases and we recommend using DUO:0000042, General Research Use, instead + general research use and clinical care @@ -164,11 +177,11 @@ - + health/medical/biomedical research - This primary category consent code indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry. + This data use limitation indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry. DUO:0000006 - HMB + HMB health or medical or biomedical research @@ -185,9 +198,9 @@ disease-specific research - This primary category consent code indicates that use is allowed provided it is related to the specified disease. + This data use limitation indicates that use is allowed provided it is related to the specified disease. DUO:0000007 - DS + DS This term should be coupled with a term describing a disease from an ontology, such as the Disease Ontology, HPO, MonDO to specify the disease the restriction applies to. disease specific research @@ -197,12 +210,12 @@ - + population origins or ancestry research - This primary category consent code indicates that use of the data is limited to the study of population origins or ancestry. + This data use limitation indicates that use of the data is limited to the study of population origins or ancestry. population origins/ancestry research DUO:0000011 - POA + POA population origins or ancestry research @@ -211,7 +224,7 @@ - + @@ -219,9 +232,9 @@ research-specific restrictions - This secondary category consent code indicates that use is limited to studies of a certain research type. + This data use limitation indicates that use is limited to studies of a certain research type. DUO:0000012 - RS + RS research specific restrictions @@ -230,11 +243,11 @@ - + research use only - This secondary category consent code indicates that use is limited to research purposes (e.g., does not include its use in clinical care). + This data use limitation indicates that use is limited to research purposes (e.g., does not include its use in clinical care). DUO:0000014 - RU + RU research use only @@ -243,9 +256,9 @@ - + no general methods research - This secondary category consent code indicates that use includes methods development research(e.g., development of software or algorithms) only within the bounds of other use limitations. + This data use limitation indicates that use includes methods development research(e.g., development of software or algorithms) only within the bounds of other use limitations. DUO:0000015 no general methods research @@ -255,11 +268,11 @@ - + genetic studies only - This secondary category consent code indicates that use is limited to genetic studies only (i.e., no phenotype-only research) + This data use limitation indicates that use is limited to genetic studies only (i.e., no phenotype-only research) DUO:0000016 - GSO + GSO genetic studies only @@ -285,7 +298,7 @@ This requirement indicates that use of the data is limited to not-for-profit organizations and not-for-profit use, non-commercial use. non-commercial use DUO:0000018 - NPU + NPU not for profit use only @@ -298,7 +311,7 @@ publication required This requirement indicates that requestor agrees to make results of studies using the data available to the larger scientific community. DUO:0000019 - PUB + PUB publication required @@ -311,7 +324,7 @@ collaboration required This requirement indicates that the requestor must agree to collaboration with the primary study investigator(s). DUO:0000020 - COL + COL This could be coupled with a string describing the primary study investigator(s). collaboration required @@ -325,7 +338,7 @@ ethics approval required This requirement indicates that the requestor must provide documentation of local IRB/ERB approval. DUO:0000021 - IRB + IRB ethics approval required @@ -344,7 +357,7 @@ geographical restriction This requirement indicates that use is limited to within a specific geographic region. DUO:0000022 - GS-[XX] + GS This should be coupled with an ontology term describing the geographical location the restriction applies to. geographical restriction @@ -359,7 +372,7 @@ This requirement indicates that requestor agrees not to publish results of studies until a specific date publication embargo DUO:0000024 - MOR-[XX] + MOR This should be coupled with a date specified as ISO8601 publication moratorium @@ -373,7 +386,7 @@ time limit on use This requirement indicates that use is approved for a specific number of months. DUO:0000025 - TS-[XX] + TS This should be coupled with an integer value indicating the number of months. time limit on use @@ -387,7 +400,7 @@ user-specific restriction This requirement indicates that use is limited to use by approved users. DUO:0000026 - US + US user specific restriction @@ -400,7 +413,7 @@ project-specific restriction This requirement indicates that use is limited to use within an approved project. DUO:0000027 - PS + PS project specific restriction @@ -413,7 +426,7 @@ institution-specific restriction This requirement indicates that use is limited to use within an approved institution. DUO:0000028 - IS + IS institution specific restriction @@ -439,7 +452,7 @@ method development An investigation concerning development of methods, algorithms, software or analytical tools. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000031 + DUO:0000031 method development @@ -452,7 +465,7 @@ population research An investigation concerning a specific population group. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000032 + DUO:0000032 Should be paired with the an ontology term representing this population (e.g., xxx). population research @@ -466,7 +479,7 @@ ancestry research An investigation concerning ancestry or population origins. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000033 + DUO:0000033 ancestry research @@ -479,7 +492,7 @@ age category research An investigation concerning specific age categories. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000034 + DUO:0000034 Should be paired with the an ontology term representing this population (e.g., xxx). age category research @@ -493,7 +506,7 @@ gender category research An investigation concerning specific gender categories. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000035 + DUO:0000035 Should be paired with the an ontology term representing this population (e.g., xxx). gender category research @@ -507,7 +520,7 @@ research control An investigation concerning use of data as reference or control material. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000036 + DUO:0000036 research control @@ -520,7 +533,7 @@ biomedical research An investigation concerning health, medical, or biomedical research. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000037 + DUO:0000037 biomedical research @@ -533,7 +546,7 @@ genetic research Biomedical research concerning genetics (i.e., the study of genes, genetic variations and heredity). This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000038 + DUO:0000038 genetic research @@ -546,7 +559,7 @@ drug development research Biomedical research concerning drug development. This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000039 + DUO:0000039 drug development research @@ -559,7 +572,7 @@ disease category research Biomedical research research concerning specific disease/s This definition is a placeholder as a result of meetings at ICBO2018. - DUO_0000040 + DUO:0000040 disease category research @@ -568,11 +581,11 @@ - + general research use - This primary category consent code indicates that use is allowed for general research use for any research purpose. + This data use limitation indicates that use is allowed for general research use for any research purpose. DUO:0000042 - GRU + GRU This includes but is not limited to: health/medical/biomedical purposes, fundamental biology research, the study of population origins or ancestry, statistical methods and algorithms development, and social-sciences research. general research use @@ -618,5 +631,5 @@ - + diff --git a/src/ontology/duo.csv b/src/ontology/duo.csv new file mode 100644 index 0000000..7894922 --- /dev/null +++ b/src/ontology/duo.csv @@ -0,0 +1,34 @@ +id,shorthand,label,description +DUO:0000021,IRB,ethics approval required,This requirement indicates that the requestor must provide documentation of local IRB/ERB approval. +DUO:0000034,,age category research,An investigation concerning specific age categories. +DUO:0000006,HMB,health or medical or biomedical research,This data use limitation indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry. +DUO:0000019,PUB,publication required,This requirement indicates that requestor agrees to make results of studies using the data available to the larger scientific community. +DUO:0000026,US,user specific restriction,This requirement indicates that use is limited to use by approved users. +DUO:0000039,,drug development research,Biomedical research concerning drug development. +DUO:0000020,COL,collaboration required,This requirement indicates that the requestor must agree to collaboration with the primary study investigator(s). +DUO:0000033,,ancestry research,An investigation concerning ancestry or population origins. +DUO:0000005,GRU-CC,general research use and clinical care,"This data use limitation indicates that use is allowed for health/medical/biomedical purposes and other biological research, including the study of population origins or ancestry." +DUO:0000018,NPU,not for profit use only,"This requirement indicates that use of the data is limited to not-for-profit organizations and not-for-profit use, non-commercial use." +DUO:0000040,,disease category research,Biomedical research research concerning specific disease/s +DUO:0000012,RS,research specific restrictions,This data use limitation indicates that use is limited to studies of a certain research type. +DUO:0000025,TS,time limit on use,This requirement indicates that use is approved for a specific number of months. +DUO:0000038,,genetic research,"Biomedical research concerning genetics (i.e., the study of genes, genetic variations and heredity)." +DUO:0000032,,population research,An investigation concerning a specific population group. +DUO:0000004,NRES,no restriction,This data use limitation indicates there is no restriction on use. +DUO:0000017,,data use requirements,Requirements indicate additional conditions set for use. +DUO:0000011,POA,population origins or ancestry research,This data use limitation indicates that use of the data is limited to the study of population origins or ancestry. +DUO:0000024,MOR,publication moratorium,This requirement indicates that requestor agrees not to publish results of studies until a specific date +DUO:0000037,,biomedical research,"An investigation concerning health, medical, or biomedical research." +DUO:0000031,,method development,"An investigation concerning development of methods, algorithms, software or analytical tools." +DUO:0000016,GSO,genetic studies only,"This data use limitation indicates that use is limited to genetic studies only (i.e., no phenotype-only research)" +DUO:0000029,RTN,return to database or resource,This requirement indicates that the requestor must return derived/enriched data to the database/resource. +DUO:0000036,,research control,An investigation concerning use of data as reference or control material. +DUO:0000015,,no general methods research,"This data use limitation indicates that use includes methods development research(e.g., development of software or algorithms) only within the bounds of other use limitations." +DUO:0000028,IS,institution specific restriction,This requirement indicates that use is limited to use within an approved institution. +DUO:0000022,GS,geographical restriction,This requirement indicates that use is limited to within a specific geographic region. +DUO:0000035,,gender category research,An investigation concerning specific gender categories. +DUO:0000007,DS,disease specific research,This data use limitation indicates that use is allowed provided it is related to the specified disease. +DUO:0000001,,data use limitation,"A data item that is used to indicate consent permissions for datasets and/or materials, and relates to the purposes for which datasets and/or material might be removed, stored or used." +DUO:0000042,GRU,general research use,This data use limitation indicates that use is allowed for general research use for any research purpose. +DUO:0000014,RU,research use only,"This data use limitation indicates that use is limited to research purposes (e.g., does not include its use in clinical care)." +DUO:0000027,PS,project specific restriction,This requirement indicates that use is limited to use within an approved project. diff --git a/src/ontology/duo.owl b/src/ontology/duo.owl new file mode 100644 index 0000000..015981a --- /dev/null +++ b/src/ontology/duo.owl @@ -0,0 +1,2571 @@ + + + + + + Cooper Stansbury + David An + Dylan Spalding + Giselle Kerry + Gregory Rushton + J. Neil Otte + Moran Ncabili + Stephanie Dyke + Melanie Courtot + + + + + + + + + + + + + DUO_preferred_label + + + + + + + + + + + + + + + + + + + + + + + + + is_restricted_to + A is restricted to B iff A is a consent code and B is an investigation and A may only participate in instances of a class C, of which B is an instance. + J. Neil Otte + E.g. A dataset is restricted to an instance of an investigation for a specific disease or at geographical location. + DUO:0000010 + is restricted to + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A disease is a disposition (i) to undergo pathological processes that (ii) exists in an organism because of one or more disorders in that organism. [url:http://ontology.buffalo.edu/medo/Disease_and_Diagnosis.pdf ] + DOID:4 + disease + + + + + + + + + data use limitation + A data item that is used to indicate consent permissions for datasets and/or materials, and relates to the purposes for which datasets and/or material might be removed, stored or used. + consent code + DUO:0000001 + data use limitation + + + + + + + + + A categorical data item indicating the primary category the consent code belongs to according to Dyke et al. 2016. + This term was depreacted as it is not used to tag datasets but instead as patterns for DUO codes capture. This is an archive specific requirement, e.g. "one code from a primary category and one or more from a second category' +This is better done by Schemablocks and constraining the pattern of usage of DUO terms at each archive level. + DUO:0000002 + obsolete consent code primary category + true + + + + + + + + + A categorical data item indicating the secondary category the consent code belongs to according to Dyke et al. 2016. + This term was depreacted as it is not used to tag datasets but instead as patterns for DUO codes capture. This is an archive specific requirement, e.g. "one code from a primary category and one or more from a second category' +This is better done by Schemablocks and constraining the pattern of usage of DUO terms at each archive level. + DUO:0000003 + obsolete consent code secondary category + true + + + + + + + + + no restriction + This data use limitation indicates there is no restriction on use. + DUO:0000004 + NRES + 20180907, Meeting Moran Melanie: This is to be thought about more carefully - what is the intent when using 'no restriction' as usually users still need to be researchers. + Note: the NRES alternative term may be confusing as in the UK it also stands for National Research Ethics Service + no restriction + + + + + + + + + general research use and clinical care + This data use limitation indicates that use is allowed for health/medical/biomedical purposes and other biological research, including the study of population origins or ancestry. + DUO:0000005 + GRU-CC + This term includes clinical care, which was not defined in the original consent codes paper. This term does not have a usage in our current use cases and we recommend using DUO:0000042, General Research Use, instead + general research use and clinical care + + + + + + + + + health/medical/biomedical research + This data use limitation indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry. + DUO:0000006 + HMB + health or medical or biomedical research + + + + + + + + + + + + + + + disease-specific research + This data use limitation indicates that use is allowed provided it is related to the specified disease. + DUO:0000007 + DS + This term should be coupled with a term describing a disease from an ontology, such as the Disease Ontology, HPO, MonDO to specify the disease the restriction applies to. + disease specific research + + + + + + + + + population origins or ancestry research + This data use limitation indicates that use of the data is limited to the study of population origins or ancestry. + population origins/ancestry research + DUO:0000011 + POA + population origins or ancestry research + + + + + + + + + + + + + + + research-specific restrictions + This data use limitation indicates that use is limited to studies of a certain research type. + DUO:0000012 + RS + research specific restrictions + + + + + + + + + research use only + This data use limitation indicates that use is limited to research purposes (e.g., does not include its use in clinical care). + DUO:0000014 + RU + research use only + + + + + + + + + no general methods research + This data use limitation indicates that use includes methods development research(e.g., development of software or algorithms) only within the bounds of other use limitations. + DUO:0000015 + no general methods research + + + + + + + + + genetic studies only + This data use limitation indicates that use is limited to genetic studies only (i.e., no phenotype-only research) + DUO:0000016 + GSO + genetic studies only + + + + + + + + + data use requirements + Requirements indicate additional conditions set for use. + DUO:0000017 + data use requirements + + + + + + + + + not-for-profit use only + This requirement indicates that use of the data is limited to not-for-profit organizations and not-for-profit use, non-commercial use. + non-commercial use + DUO:0000018 + NPU + not for profit use only + + + + + + + + + publication required + This requirement indicates that requestor agrees to make results of studies using the data available to the larger scientific community. + DUO:0000019 + PUB + publication required + + + + + + + + + collaboration required + This requirement indicates that the requestor must agree to collaboration with the primary study investigator(s). + DUO:0000020 + COL + This could be coupled with a string describing the primary study investigator(s). + collaboration required + + + + + + + + + ethics approval required + This requirement indicates that the requestor must provide documentation of local IRB/ERB approval. + DUO:0000021 + IRB + ethics approval required + + + + + + + + + + + + + + + geographical restriction + This requirement indicates that use is limited to within a specific geographic region. + DUO:0000022 + GS + This should be coupled with an ontology term describing the geographical location the restriction applies to. + geographical restriction + + + + + + + + + publication moratorium + This requirement indicates that requestor agrees not to publish results of studies until a specific date + publication embargo + DUO:0000024 + MOR + This should be coupled with a date specified as ISO8601 + publication moratorium + + + + + + + + + time limit on use + This requirement indicates that use is approved for a specific number of months. + DUO:0000025 + TS + This should be coupled with an integer value indicating the number of months. + time limit on use + + + + + + + + + user-specific restriction + This requirement indicates that use is limited to use by approved users. + DUO:0000026 + US + user specific restriction + + + + + + + + + project-specific restriction + This requirement indicates that use is limited to use within an approved project. + DUO:0000027 + PS + project specific restriction + + + + + + + + + institution-specific restriction + This requirement indicates that use is limited to use within an approved institution. + DUO:0000028 + IS + institution specific restriction + + + + + + + + + return to database/resource + This requirement indicates that the requestor must return derived/enriched data to the database/resource. + DUO:0000029 + RTN + return to database or resource + + + + + + + + + method development + An investigation concerning development of methods, algorithms, software or analytical tools. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000031 + method development + + + + + + + + + population research + An investigation concerning a specific population group. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000032 + Should be paired with the an ontology term representing this population (e.g., xxx). + population research + + + + + + + + + ancestry research + An investigation concerning ancestry or population origins. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000033 + ancestry research + + + + + + + + + age category research + An investigation concerning specific age categories. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000034 + Should be paired with the an ontology term representing this population (e.g., xxx). + age category research + + + + + + + + + gender category research + An investigation concerning specific gender categories. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000035 + Should be paired with the an ontology term representing this population (e.g., xxx). + gender category research + + + + + + + + + research control + An investigation concerning use of data as reference or control material. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000036 + research control + + + + + + + + + biomedical research + An investigation concerning health, medical, or biomedical research. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000037 + biomedical research + + + + + + + + + genetic research + Biomedical research concerning genetics (i.e., the study of genes, genetic variations and heredity). + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000038 + genetic research + + + + + + + + + drug development research + Biomedical research concerning drug development. + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000039 + drug development research + + + + + + + + + disease category research + Biomedical research research concerning specific disease/s + This definition is a placeholder as a result of meetings at ICBO2018. + DUO:0000040 + disease category research + + + + + + + + + general research use + This data use limitation indicates that use is allowed for general research use for any research purpose. + DUO:0000042 + GRU + This includes but is not limited to: health/medical/biomedical purposes, fundamental biology research, the study of population origins or ancestry, statistical methods and algorithms development, and social-sciences research. + general research use + + + + + + + + + GAZ:00000448 + geographic location + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A category denoting a rather broad domain or field of interest, study, application, work, data, or technology. Topics have no clearly defined borders between each other. + topic:0003 + Topic + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/src/ontology/make-csv.sparql b/src/ontology/make-csv.sparql index 50a70b8..b6dcc29 100644 --- a/src/ontology/make-csv.sparql +++ b/src/ontology/make-csv.sparql @@ -1,8 +1,9 @@ PREFIX rdfs: + SELECT ?id ?shorthand ?label ?description WHERE { ?term rdfs:label ?label ; ?description ; ?id; - ?shorthand + OPTIONAL {?term ?shorthand} }