en Adam Goldstein Alan Ruttenberg Albert Goldfain Barry Smith Bjoern Peters Carlo Torniai Chris Mungall Chris Stoeckert Christian A. Boelling Clint Dowland Darren Natale David Osumi-Sutherland Gwen Frishkoff Holger Stenzhorn James A. Overton James Malone Jennifer Fostel Jie Zheng Jonathan Rees Larisa Soldatova Lawrence Hunter Mathias Brochhausen Matt Brush Melanie Courtot Michel Dumontier Paolo Ciccarese Pat Hayes Philippe Rocca-Serra Randy Dipert Ron Rudnicki Satya Sahoo Sivaram Arabandi Werner Ceusters William Duncan William Hogan Yongqun (Oliver) He Allyson Lister Andy Brown Duncan Hull Helen Parkinson James Malone Jon Ison Nandini Badarinarayan Robert Stevens The Information Artifact Ontology (IAO) is an ontology of information entities, originally driven by work by the OBI digital entity and realizable information entity branch. Information Artifact Ontology (IAO) SWO (The Software Ontology) Dave Beckett Degui Zhi Kirk Roberts Licong Cui Nikki Rogers Participants in W3C's Semantic Web Deployment Working Group. Xiaqian Jiang Alistair Miles Sean Bechhofer Tuan Amith and Cui Tao An RDF vocabulary for describing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', other types of controlled vocabulary, and also concept schemes embedded in glossaries and terminologies. An ontology representing the model card structure The Software Ontology (SWO) is a resource for describing software tools, their types, tasks, versions, licences, provenance and associated data. https://creativecommons.org/licenses/by/3.0/ Model Card Ontology SKOS Vocabulary An information artifact is, loosely, a dependent continuant or its bearer that is created as the result of one or more intentional processes. Examples: uniprot, the english language, the contents of this document or a printout of it, the temperature measurements from a weather balloon. For more information, see the project home page at https://github.com/information-artifact-ontology/IAO Date of release: 21.10.2019 IDs allocated to related efforts: PNO: IAO_0020000-IAO_0020999, D_ACTS: IAO_0021000-IAO_0021999 IDs allocated to subdomains of IAO. pno.owl: IAO_0020000-IAO_0020999, d-acts.owl: IAO_0021000-IAO_0021999 The Software Ontology (SWO) is a resource for describing software tools, their types, tasks, versions, licensing, provenance and associated data. It contains SWO-specific classes and axioms as well as imports from: 1. BFO 2. IAO 3. OBI 4. EDAM This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page). If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome. W3C PROVenance Interchange Ontology (PROV-O) 1.7 2022-11-07 2023-03-07 Recommendation version 2013-04-30 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 editor preferred term 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 term example of usage 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 has curation status definition 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 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.obofoundry.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 label A label for a class or property that can be used to refer to the class or property instead of the preferred rdfs:label. Alternative labels should be used to indicate community- or context-specific labels, abbreviations, shorthand forms and the like. OBO Operations committee PERSON:Daniel Schober GROUP:OBI:<http://purl.obolibrary.org/obo/obi> Consider re-defing to: An alternative name for a class or property which can mean the same thing as the preferred name (semantically equivalent, narrow, broad or related). alternative label 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 ontology term requester 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 has ID digit count 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 has ID range allocated 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 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" Relating an ontology used to record id policy to the ontology namespace whose policy it manages Person:Alan Ruttenberg has ID policy for has ID prefix 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 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 Add as annotation triples in the granting ontology 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 has ontology root term Ontology annotation property. Relates an ontology to a term that is a designated root term of the ontology. Display tools like OLS can use terms annotated with this property as the starting point for rendering the ontology class hierarchy. There can be more than one root. Nicolas Matentzoglu has ontology root term may be identical to 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 Edges asserting this should be annotated with to record evidence supporting the assertion and its provenance. may be identical to scheduled for obsoletion on or after 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 Use on obsolete terms, relating the term to another term that can be used as a substitute Person:Alan Ruttenberg Person:Alan Ruttenberg Add as annotation triples in the granting ontology term replaced by This is an annotation used on an object property to indicate a logical characterstic beyond what is possible in OWL. OBO Operations call logical characteristic of object property 'part disjoint with' 'defined by construct' """ PREFIX owl: <http://www.w3.org/2002/07/owl#> PREFIX : <http://example.org/ CONSTRUCT { [ a owl:Restriction ; owl:onProperty :part_of ; owl:someValuesFrom ?a ; owl:disjointWith [ a owl:Restriction ; owl:onProperty :part_of ; owl:someValuesFrom ?b ] ] } WHERE { ?a :part_disjoint_with ?b . } Links an annotation property to a SPARQL CONSTRUCT query which is meant to provide semantics for a shortcut relation. defined by construct 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 An alternative label for a class or property which has a more general meaning than the preferred name/primary label. https://github.com/information-artifact-ontology/ontology-metadata/issues/18 has broad synonym https://github.com/information-artifact-ontology/ontology-metadata/issues/18 An alternative label for a class or property which has the exact same meaning than the preferred name/primary label. https://github.com/information-artifact-ontology/ontology-metadata/issues/20 has exact synonym https://github.com/information-artifact-ontology/ontology-metadata/issues/20 An alternative label for a class or property which has a more specific meaning than the preferred name/primary label. https://github.com/information-artifact-ontology/ontology-metadata/issues/19 has narrow synonym https://github.com/information-artifact-ontology/ontology-metadata/issues/19 An alternative label for a class or property that has been used synonymously with the primary term name, but the usage is not strictly correct. https://github.com/information-artifact-ontology/ontology-metadata/issues/21 has related synonym https://github.com/information-artifact-ontology/ontology-metadata/issues/21 The range of skos:altLabel is the class of RDF plain literals. skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. alternative label An alternative lexical label for a resource. Acronyms, abbreviations, spelling variants, and irregular plural/singular forms may be included among the alternative labels for a concept. Mis-spelled terms are normally included as hidden labels (see skos:hiddenLabel). change note A note about a modification to a concept. definition A statement or formal explanation of the meaning of a concept. editorial note A note for an editor, translator or maintainer of the vocabulary. example An example of the use of a concept. The range of skos:hiddenLabel is the class of RDF plain literals. skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. hidden label A lexical label for a resource that should be hidden when generating visual displays of the resource, but should still be accessible to free text search operations. history note A note about the past state/use/meaning of a concept. note A general note, for any purpose. This property may be used directly, or as a super-property for more specific note types. A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag. The range of skos:prefLabel is the class of RDF plain literals. skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. preferred label The preferred lexical label for a resource, in a given language. scope note A note that helps to clarify the meaning and/or the use of a concept. Classify prov-o terms into three categories, including 'starting-point', 'qualifed', and 'extended'. This classification is used by the prov-o html document to gently introduce prov-o terms to its users. Classify prov-o terms into six components according to prov-dm, including 'agents-responsibility', 'alternate', 'annotations', 'collections', 'derivations', and 'entities-activities'. This classification is used so that readers of prov-o specification can find its correspondence with the prov-dm specification. A reference to the principal section of the PROV-CONSTRAINTS document that describes this concept. A definition quoted from PROV-DM or PROV-CONSTRAINTS that describes the concept expressed with this OWL term. A reference to the principal section of the PROV-DM document that describes this concept. A note by the OWL development team about how this term expresses the PROV-DM concept, or how it should be used in context of semantic web or linked data. When the prov-o term does not have a definition drawn from prov-dm, and the prov-o editor provides one. PROV-O does not define all property inverses. The directionalities defined in PROV-O should be given preference over those not defined. However, if users wish to name the inverse of a PROV-O property, the local name given by prov:inverse should be used. A reference to the principal section of the PROV-DM document that describes this concept. The position that this OWL term should be listed within documentation. The scope of the documentation (e.g., among all terms, among terms within a prov:category, among properties applying to a particular class, etc.) is unspecified. This annotation property links a subproperty of prov:wasInfluencedBy with the subclass of prov:Influence and the qualifying property that are used to qualify it. Example annotation: prov:wasGeneratedBy prov:qualifiedForm prov:qualifiedGeneration, prov:Generation . Then this unqualified assertion: :entity1 prov:wasGeneratedBy :activity1 . can be qualified by adding: :entity1 prov:qualifiedGeneration :entity1Gen . :entity1Gen a prov:Generation, prov:Influence; prov:activity :activity1; :customValue 1337 . Note how the value of the unqualified influence (prov:wasGeneratedBy :activity1) is mirrored as the value of the prov:activity (or prov:entity, or prov:agent) property on the influence class. Classes and properties used to qualify relationships are annotated with prov:unqualifiedForm to indicate the property used to assert an unqualified provenance relation. 'is about' relates an information entity to other entities in which the information entity holds some information which dscribes some facet of the other entity, such as the arrow direction on a sign. IAO James Malone Alan Ruttenberg is about is part of my brain is part of my body (continuant parthood, two material entities) my stomach cavity is part of my stomach (continuant parthood, immaterial entity is part of material entity) this day is part of this year (occurrent parthood) a core relation that holds between a part and its whole Everything is part of itself. Any part of any part of a thing is itself part of that thing. Two distinct things cannot be part of each other. Occurrents are not subject to change and so parthood between occurrents holds for all the times that the part exists. Many continuants are subject to change, so parthood between continuants will only hold at certain times, but this is difficult to specify in OWL. See http://purl.obolibrary.org/obo/ro/docs/temporal-semantics/ Parthood requires the part and the whole to have compatible classes: only an occurrent can be part of an occurrent; only a process can be part of a process; only a continuant can be part of a continuant; only an independent continuant can be part of an independent continuant; only an immaterial entity can be part of an immaterial entity; only a specifically dependent continuant can be part of a specifically dependent continuant; only a generically dependent continuant can be part of a generically dependent continuant. (This list is not exhaustive.) A continuant cannot be part of an occurrent: use 'participates in'. An occurrent cannot be part of a continuant: use 'has participant'. A material entity cannot be part of an immaterial entity: use 'has location'. A specifically dependent continuant cannot be part of an independent continuant: use 'inheres in'. An independent continuant cannot be part of a specifically dependent continuant: use 'bearer of'. part_of part of http://www.obofoundry.org/ro/#OBO_REL:part_of realized in this disease is realized in this disease course this fragility is realized in this shattering this investigator role is realized in this investigation is realized by realized_in [copied from inverse property 'realizes'] to say that b realizes c at t is to assert that there is some material entity d & b is a process which has participant d at t & c is a disposition or role of which d is bearer_of at t& the type instantiated by b is correlated with the type instantiated by c. (axiom label in BFO2 Reference: [059-003]) Paraphrase of elucidation: a relation between a realizable entity and a process, where there is some material entity that is bearer of the realizable entity and participates in the process, and the realizable entity comes to be realized in the course of the process realized in realizes this disease course realizes this disease this investigation realizes this investigator role this shattering realizes this fragility to say that b realizes c at t is to assert that there is some material entity d & b is a process which has participant d at t & c is a disposition or role of which d is bearer_of at t& the type instantiated by b is correlated with the type instantiated by c. (axiom label in BFO2 Reference: [059-003]) Paraphrase of elucidation: a relation between a process and a realizable entity, where there is some material entity that is bearer of the realizable entity and participates in the process, and the realizable entity comes to be realized in the course of the process realizes OBO Foundry Please note that, as stated on one of the RO documentation pages (https://code.google.com/p/obo-relations/wiki/ROAndBFO), some of the relations RO makes use are either uncontroversial (non-temporalized) parts of BFO2, or will be incorporated in the future. In the case of BFO_0000063, it is not currently in BFO2, but may be in the future. The RO ontologists assume this is the transitive form. For a full definition, refer to the inverse of this property, BFO_0000060. (Allyson Lister) preceded by The assertion P 'followed by' P1 tells us something about Ps in general: that is, it tells us something about what happened later, given what we know about what happened earlier. Thus it does not provide information pointing in the opposite direction, concerning instances of P1 in general; that is, that each is such as to be preceded by some instance of P. Note that assertions using this property only are rather weak. Typically we will be interested in stronger relations, for example in the relation 'directly followed by'. Modified by Allyson Lister from the preceded_by (which is the inverse of precedes / 'followed by') definition within RO: http://www.obofoundry.org/ro/ro.owl OBO Foundry Please note that, as stated on one of the RO documentation pages (https://code.google.com/p/obo-relations/wiki/ROAndBFO), some of the relations RO makes use are either uncontroversial (non-temporalized) parts of BFO2, or will be incorporated in the future. In the case of BFO_0000060, it is not currently in BFO2, but may be in the future. The RO ontologists assume this is the transitive form. (Allyson Lister) followed by occurs in b occurs_in c =def b is a process and c is a material entity or immaterial entity& there exists a spatiotemporal region r and b occupies_spatiotemporal_region r.& forall(t) if b exists_at t then c exists_at t & there exist spatial regions s and s’ where & b spatially_projects_onto s at t& c is occupies_spatial_region s’ at t& s is a proper_continuant_part_of s’ at t occurs_in unfolds in unfolds_in Paraphrase of definition: a relation between a process and an independent continuant, in which the process takes place entirely within the independent continuant occurs in site of [copied from inverse property 'occurs in'] b occurs_in c =def b is a process and c is a material entity or immaterial entity& there exists a spatiotemporal region r and b occupies_spatiotemporal_region r.& forall(t) if b exists_at t then c exists_at t & there exist spatial regions s and s’ where & b spatially_projects_onto s at t& c is occupies_spatial_region s’ at t& s is a proper_continuant_part_of s’ at t Paraphrase of definition: a relation between an independent continuant and a process, in which the process takes place entirely within the independent continuant contains process The process of creation is, for example, writing down on paper the name of a friend by deliberately creating a certain pattern using ink. Here the ink + paper is the independent continuant and the carrier is the pattern in the ink. c = pattern in the ink b = paper + ink r = friend c specifically denotes r =def r is a portion of reality & c is a particular quality & c depends specifically on some independent continuant b & b acquired c as the result of the achievement of an objective to enable pointing to r repeatedly. Marked means there is a changed or additional quality of the bearer - the quality is the information carrier. Case 1 Memory trace as mark created when reading some description of some friend. The trace can denote. Case 2 Pattern of ink arrayed on paper as mark when writing down a friend's name Case 3 Pattern of magnetic domains on scattered pieces of a hard disk platter as mark when saving a file. 8/6/2009 Alan Ruttenberg: The suggestions is to deprecate specific and generically denotes in favor of a single denote relationship that corresponds to the generic sense see https://github.com/information-artifact-ontology/IAO/issues/25&q=denote Alan Ruttenberg Smith, Ceusters, Ruttenberg, 2000 years of philosophy obsolete_specifically denotes true An information artifact IA mentions an entity E exactly when it has a component/part that denotes E 7/6/2009 Alan Ruttenberg. P4 RC1 munges our GCI so remove it for now: mentions some entity equivalentTo has_part some ('generically denotes' some entity) 7/6/2009 Alan Ruttenberg: Add this relation following conversation with Jonathan Rees that N&S GCI for is_about was too strong. Really it was simply sufficient. To effect this change we introduce this relation, which is subproperty of is_about, and have previous GCI use this relation "mentions" in it's (logical) definition PERSON: Jonathan Rees Person: Alan Ruttenberg mentions Inverse of the relation 'mentions' 2022-01-28T07:20:08Z mentioned by see https://github.com/information-artifact-ontology/IAO/issues/25&q=denote obsolete_materially denotes true obsolete_describes true obsolete_represents true inverse of the relation 'denotes' Person: Jie Zheng, Chris Stoeckert, Mike Conlon denoted by relating a cartesian spatial coordinate datum to a unit label that together with the values represent a point has coordinate unit label relates a process to a time-measurement-datum that represents the duration of the process Person:Alan Ruttenberg is duration of inverse of the relation of is quality measurement of 2009/10/19 Alan Ruttenberg. Named 'junk' relation useful in restrictions, but not a real instance relationship Person:Alan Ruttenberg is quality measured as A relation between a data item and a quality of a material entity where the material entity is the specified output of a material transformation which achieves an objective specification that indicates the intended value of the specified quality. Person:Alan Ruttenberg Person:Bjoern Peters is quality specification of inverse of the relation of is quality specification of 2009/10/19 Alan Ruttenberg. Named 'junk' relation useful in restrictions, but not a real instance relationship Person:Alan Ruttenberg Person:Bjoern Peters quality is specified as relates a time stamped measurement datum to the time measurement datum that denotes the time when the measurement was taken Alan Ruttenberg has time stamp relates a time stamped measurement datum to the measurement datum that was measured Alan Ruttenberg has measurement datum is_specified_input_of inheres in this fragility is a characteristic of this vase this red color is a characteristic of this apple a relation between a specifically dependent continuant (the characteristic) and any other entity (the bearer), in which the characteristic depends on the bearer for its existence. inheres_in Note that this relation was previously called "inheres in", but was changed to be called "characteristic of" because BFO2 uses "inheres in" in a more restricted fashion. This relation differs from BFO2:inheres_in in two respects: (1) it does not impose a range constraint, and thus it allows qualities of processes, as well as of information entities, whereas BFO2 restricts inheres_in to only apply to independent continuants (2) it is declared functional, i.e. something can only be a characteristic of one thing. characteristic of bearer of this apple is bearer of this red color this vase is bearer of this fragility Inverse of characteristic_of A bearer can have many dependents, and its dependents can exist for different periods of time, but none of its dependents can exist when the bearer does not exist. bearer_of is bearer of has characteristic participates in this blood clot participates in this blood coagulation this input material (or this output material) participates in this process this investigator participates in this investigation a relation between a continuant and a process, in which the continuant is somehow involved in the process participates_in Andy Brown Please see the official RO definition for the inverse of this property, 'has participant.' participates in participates in A journal article is an information artifact that inheres in some number of printed journals. For each copy of the printed journal there is some quality that carries the journal article, such as a pattern of ink. The journal article (a generically dependent continuant) is concretized as the quality (a specifically dependent continuant), and both depend on that copy of the printed journal (an independent continuant). An investigator reads a protocol and forms a plan to carry out an assay. The plan is a realizable entity (a specifically dependent continuant) that concretizes the protocol (a generically dependent continuant), and both depend on the investigator (an independent continuant). The plan is then realized by the assay (a process). A relationship between a generically dependent continuant and a specifically dependent continuant, in which the generically dependent continuant depends on some independent continuant in virtue of the fact that the specifically dependent continuant also depends on that same independent continuant. A generically dependent continuant may be concretized as multiple specifically dependent continuants. is concretized as A journal article is an information artifact that inheres in some number of printed journals. For each copy of the printed journal there is some quality that carries the journal article, such as a pattern of ink. The quality (a specifically dependent continuant) concretizes the journal article (a generically dependent continuant), and both depend on that copy of the printed journal (an independent continuant). An investigator reads a protocol and forms a plan to carry out an assay. The plan is a realizable entity (a specifically dependent continuant) that concretizes the protocol (a generically dependent continuant), and both depend on the investigator (an independent continuant). The plan is then realized by the assay (a process). A relationship between a specifically dependent continuant and a generically dependent continuant, in which the generically dependent continuant depends on some independent continuant in virtue of the fact that the specifically dependent continuant also depends on that same independent continuant. Multiple specifically dependent continuants can concretize the same generically dependent continuant. concretizes this catalysis function is a function of this enzyme a relation between a function and an independent continuant (the bearer), in which the function specifically depends on the bearer for its existence A function inheres in its bearer at all times for which the function exists, however the function need not be realized at all the times that the function exists. function_of is function of This relation is modeled after the BFO relation of the same name which was in BFO2, but is used in a more restricted sense - specifically, we model this relation as functional (inherited from characteristic-of). Note that this relation is now removed from BFO2020. function of this red color is a quality of this apple a relation between a quality and an independent continuant (the bearer), in which the quality specifically depends on the bearer for its existence A quality inheres in its bearer at all times for which the quality exists. is quality of quality_of This relation is modeled after the BFO relation of the same name which was in BFO2, but is used in a more restricted sense - specifically, we model this relation as functional (inherited from characteristic-of). Note that this relation is now removed from BFO2020. quality of this investigator role is a role of this person a relation between a role and an independent continuant (the bearer), in which the role specifically depends on the bearer for its existence A role inheres in its bearer at all times for which the role exists, however the role need not be realized at all the times that the role exists. is role of role_of This relation is modeled after the BFO relation of the same name which was in BFO2, but is used in a more restricted sense - specifically, we model this relation as functional (inherited from characteristic-of). Note that this relation is now removed from BFO2020. role of this enzyme has function this catalysis function (more colloquially: this enzyme has this catalysis function) a relation between an independent continuant (the bearer) and a function, in which the function specifically depends on the bearer for its existence A bearer can have many functions, and its functions can exist for different periods of time, but none of its functions can exist when the bearer does not exist. A function need not be realized at all the times that the function exists. has_function has function this apple has quality this red color a relation between an independent continuant (the bearer) and a quality, in which the quality specifically depends on the bearer for its existence A bearer can have many qualities, and its qualities can exist for different periods of time, but none of its qualities can exist when the bearer does not exist. has_quality has quality this person has role this investigator role (more colloquially: this person has this role of investigator) a relation between an independent continuant (the bearer) and a role, in which the role specifically depends on the bearer for its existence A bearer can have many roles, and its roles can exist for different periods of time, but none of its roles can exist when the bearer does not exist. A role need not be realized at all the times that the role exists. has_role has role has_role a relation between an independent continuant (the bearer) and a disposition, in which the disposition specifically depends on the bearer for its existence has disposition This relation is modeled after the BFO relation of the same name which was in BFO2, but is used in a more restricted sense - specifically, we model this relation as functional (inherited from characteristic-of). Note that this relation is now removed from BFO2020. disposition of this cell derives from this parent cell (cell division) this nucleus derives from this parent nucleus (nuclear division) a relation between two distinct material entities, the new entity and the old entity, in which the new entity begins to exist when the old entity ceases to exist, and the new entity inherits the significant portion of the matter of the old entity This is a very general relation. More specific relations are preferred when applicable, such as 'directly develops from'. derives_from derives from this parent cell derives into this cell (cell division) this parent nucleus derives into this nucleus (nuclear division) a relation between two distinct material entities, the old entity and the new entity, in which the new entity begins to exist when the old entity ceases to exist, and the new entity inherits the significant portion of the matter of the old entity This is a very general relation. More specific relations are preferred when applicable, such as 'directly develops into'. To avoid making statements about a future that may not come to pass, it is often better to use the backward-looking 'derives from' rather than the forward-looking 'derives into'. derives_into derives into is location of my head is the location of my brain this cage is the location of this rat a relation between two independent continuants, the location and the target, in which the target is entirely within the location Most location relations will only hold at certain times, but this is difficult to specify in OWL. See http://purl.obolibrary.org/obo/ro/docs/temporal-semantics/ location_of location of located in my brain is located in my head this rat is located in this cage a relation between two independent continuants, the target and the location, in which the target is entirely within the location Location as a relation between instances: The primitive instance-level relation c located_in r at t reflects the fact that each continuant is at any given time associated with exactly one spatial region, namely its exact location. Following we can use this relation to define a further instance-level location relation - not between a continuant and the region which it exactly occupies, but rather between one continuant and another. c is located in c1, in this sense, whenever the spatial region occupied by c is part_of the spatial region occupied by c1. Note that this relation comprehends both the relation of exact location between one continuant and another which obtains when r and r1 are identical (for example, when a portion of fluid exactly fills a cavity), as well as those sorts of inexact location relations which obtain, for example, between brain and head or between ovum and uterus Most location relations will only hold at certain times, but this is difficult to specify in OWL. See http://purl.obolibrary.org/obo/ro/docs/temporal-semantics/ located_in http://www.obofoundry.org/ro/#OBO_REL:located_in located in This is redundant with the more specific 'independent and not spatial region' constraint. We leave in the redundant axiom for use with reasoners that do not use negation. This is redundant with the more specific 'independent and not spatial region' constraint. We leave in the redundant axiom for use with reasoners that do not use negation. the surface of my skin is a 2D boundary of my body a relation between a 2D immaterial entity (the boundary) and a material entity, in which the boundary delimits the material entity A 2D boundary may have holes and gaps, but it must be a single connected entity, not an aggregate of several disconnected parts. Although the boundary is two-dimensional, it exists in three-dimensional space and thus has a 3D shape. 2D_boundary_of boundary of is 2D boundary of is boundary of 2D boundary of my body has 2D boundary the surface of my skin a relation between a material entity and a 2D immaterial entity (the boundary), in which the boundary delimits the material entity A 2D boundary may have holes and gaps, but it must be a single connected entity, not an aggregate of several disconnected parts. Although the boundary is two-dimensional, it exists in three-dimensional space and thus has a 3D shape. has boundary has_2D_boundary has 2D boundary An organism that is a member of a population of organisms is member of is a mereological relation between a item and a collection. is member of member part of SIO member of has member is a mereological relation between a collection and an item. SIO has member An entity A is the 'input of' another entity B if A was put into the system, entity or software represented by B. Allyson Lister input of A piece of software can be the output of a particular software company via a software publishing process; data might be the output of a particular piece of data-producing software. An entity A is the 'output of' another entity B if it was produced as a result of the functioning of entity B. Allyson Lister output of DEPRECATED This relation is similar to but different in important respects to the characteristic-of relation. See comments on that relation for more information. DEPRECATED inheres in true DEPRECATED bearer of true The relationship between a software and software developer. is developed by The relationship between software and a software publisher. Marked as obsolete by Allyson Lister. 0.5 This class can be entirely replaced with 'is published by', SWO_0004004. Please use SWO_0004004 instead. obsolete_is_published_by true implements is the relationship between software and an algorithm that is defined for use within that software when executed. James Malone implements Linking a type of software to its particular programming language. Is encoded in is an "is about" relationship which describes the type of encoding used for the referenced class. Allyson Lister is encoded in 'is version of' provides a link between a 'version name' and the entity with that version. Allyson Lister For further information, please see http://softwareontology.wordpress.com/2012/06/20/versioning-in-swo/ is version of Cytoscape plugins would be linked to the Cytoscape application via uses software, while Microsoft Excel is linked to Microsoft Office via has_part. This property allows the linkage of two different pieces of software such that one directly executes or uses the other. The has_part relationship should instead be used to describe related but independent members of a larger software package, and 'uses platform' relationship should be used to describe which operating system(s) a particular piece of software can use. Allyson Lister uses software is implemented by is the relationship between an algorithm and a piece of software which includes an implementation of that software for use when the software is executed. James Malone is implemented by The relationship between input data which is permitted to a piece of software. James Malone See also http://softwareontology.wordpress.com/2011/04/15/ins-and-outs-of-software/ has specified data input The relationship between a piece of software and the data that it is possible to output. James Malone See also http://softwareontology.wordpress.com/2011/04/15/ins-and-outs-of-software/ has specified data output The relationship between a data and the software which can possibly take this data as input. James Malone is specified data input of The relationship between a data and the software which can possibly produce this data as output. James Malone is specified data output of Microsoft version 2007 is directly preceded by Microsoft version 2003. Entity A is 'directly preceded by' entity B if there are no intermediate entities temporally between the two entities. WIthin SWO this property is mainly used to describe versions of entities such as software. Allyson Lister OBO Foundry directly preceded by 'directly followed by' is an object property which further specializes the parent 'followed by' property. In the assertion 'C directly followed by C1', says that Cs generally are immediately followed by C1s. Allyson Lister directly followed by 'uses platform' should be used to link a particular piece of software to one or more operating systems which that software can run on. This is in contrast to both 'uses software' (which describes one piece of software directly executing another), and has_part, which can be used to describe related but independent software in a package, for example. Allyson Lister This property, together with 'uses software', is probably best modelled as a child of has_part. Its current position in the property hierarchy is based on simplicity of use. 'uses platform' was deemed an appropriate addition (rather than making use of already extant has_part or 'uses software') due to the already present definitions of those classes which restrict their use to particular situations. uses platform is software for relationship between an entity and a version name or number For further information, please see http://softwareontology.wordpress.com/2012/06/20/versioning-in-swo/ has version Provides a method of asserting what type of interactions are possible for the class in question. The interface must be from the 'software interface' hierarchy. Allyson Lister Andy Brown Andy Brown has interface Has format specification is a type of "is encoded in" relationship which specifically describes the relationship between data and a data format specification. Allyson Lister has format specification 'is published by' elucidates the relationship between a piece of software or a data format specification and its owning organization. Please note that this is not the same as authorship of the software. For instance, affy is published within Bioconductor, but has its own distinct authorship list. Allyson Lister James Malone is published by is executed in defines the relationship between a software class and an appropriate process in the information processing hierarchy. Specifically, it allows the linking of a particular piece of software to a process of a particular purpose, Allyson Lister Allyson Lister OBI is executed in Axioms using the 'has clause' property, e.g. C 'has clause' C1, provide links from the left hand class to the instances within the 'license clause' hierarchy. This provides a way to more precisely assert the constraints of the licensing applied. Allyson Lister has clause The relationship between an entity and the set of legal restrictions, i.e. license, which are applied in using or otherwise interacting with that entity. Eg. relationship between software and a software license. has license The relationship between an entity and the set of legal restrictions, i.e. license, which are applied in using or otherwise interacting with that entity. Eg. relationship between a software license and the software which implements it. is license for The format for BioPAX Manchester OWL syntax is an alternative format of the BioPAX RDF/XML format. With both a domain and range of 'data format specification', this property provides a means of stating that two different data format specifications are valid specifications for the same type of data. Allyson Lister is alternative format of 'is compatible license of' provides a method of marking two software licenses as compatible and without conflicts, e.g. that the Apache License version 2 is compatible with GNU GPL version 3. If two licenses are connected with this property, it means code released under one license can be released with code from the other license in a larger program. http://www.gnu.org/licenses/gpl-faq.html#WhatDoesCompatMean, accessed 12 June 2013. Allyson Lister is compatible license of 'has declared status' provides a way to assert the developmental status of a class, such as whether it is stable or under development. Is especially useful for software that might not be complete or stable yet, and when combined with version information. Allyson Lister has declared status has broader match skos:broadMatch is used to state a hierarchical mapping link between two conceptual resources in different concept schemes. Broader concepts are typically rendered as parents in a concept hierarchy (tree). has broader Relates a concept to a concept that is more general in meaning. By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources. has broader transitive skos:broaderTransitive is a transitive superproperty of skos:broader. By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application. has close match skos:closeMatch is used to link two concepts that are sufficiently similar that they can be used interchangeably in some information retrieval applications. In order to avoid the possibility of "compound errors" when combining mappings across more than two concept schemes, skos:closeMatch is not declared to be a transitive property. skos:exactMatch is disjoint with each of the properties skos:broadMatch and skos:relatedMatch. has exact match skos:exactMatch is used to link two concepts, indicating a high degree of confidence that the concepts can be used interchangeably across a wide range of information retrieval applications. skos:exactMatch is a transitive property, and is a sub-property of skos:closeMatch. has top concept Relates, by convention, a concept scheme to a concept which is topmost in the broader/narrower concept hierarchies for that scheme, providing an entry point to these hierarchies. is in scheme Relates a resource (for example a concept) to a concept scheme in which it is included. A concept may be a member of more than one concept scheme. These concept mapping relations mirror semantic relations, and the data model defined below is similar (with the exception of skos:exactMatch) to the data model defined for semantic relations. A distinct vocabulary is provided for concept mapping relations, to provide a convenient way to differentiate links within a concept scheme from links between concept schemes. However, this pattern of usage is not a formal requirement of the SKOS data model, and relies on informal definitions of best practice. is in mapping relation with Relates two concepts coming, by convention, from different schemes, and that have comparable meanings has member Relates a collection to one of its members. For any resource, every item in the list given as the value of the skos:memberList property is also a value of the skos:member property. has member list Relates an ordered collection to the RDF list containing its members. has narrower match skos:narrowMatch is used to state a hierarchical mapping link between two conceptual resources in different concept schemes. Narrower concepts are typically rendered as children in a concept hierarchy (tree). has narrower Relates a concept to a concept that is more specific in meaning. By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources. has narrower transitive skos:narrowerTransitive is a transitive superproperty of skos:narrower. By convention, skos:narrowerTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application. skos:related is disjoint with skos:broaderTransitive has related Relates a concept to a concept with which there is an associative semantic relationship. has related match skos:relatedMatch is used to state an associative mapping link between two conceptual resources in different concept schemes. is in semantic relation with Links a concept to a concept related by meaning. This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts. is top concept in scheme Relates a concept to the concept scheme that it is a top level concept of. An object property to express the accountability of an agent towards another agent. The subordinate agent acted on behalf of the responsible agent in an actual activity. actedOnBehalfOf starting-point agents-responsibility hadDelegate activity qualified This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple. The prov:activity property references an prov:Activity which influenced a resource. This property applies to an prov:ActivityInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent. activityOfInfluence agent qualified This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple. The prov:agent property references an prov:Agent which influenced a resource. This property applies to an prov:AgentInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent. agentOfInfluence alternateOf expanded alternate http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig Two alternate entities present aspects of the same thing. These aspects may be the same or different, and the alternate entities may or may not overlap in time. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-alternate alternateOf http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-alternate The Location of any resource. This property has multiple RDFS domains to suit multiple OWL Profiles. See <a href="#owl-profile">PROV-O OWL Profile</a>. atLocation expanded The naming of prov:atLocation parallels prov:atTime, and is not named prov:hadLocation to avoid conflicting with the convention that prov:had* properties are used on prov:Influence classes. This property is not functional because the many values could be at a variety of granularies (In this building, in this room, in that chair). locationOf entity qualified This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple. The prov:entity property references an prov:Entity which influenced a resource. This property applies to an prov:EntityInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent. entityOfInfluence generated expanded entities-activities prov:generated is one of few inverse property defined, to allow Activity-oriented assertions in addition to Entity-oriented assertions. wasGeneratedBy The _optional_ Activity of an Influence, which used, generated, invalidated, or was the responsibility of some Entity. This property is _not_ used by ActivityInfluence (use prov:activity instead). This property has multiple RDFS domains to suit multiple OWL Profiles. See <a href="#owl-profile">PROV-O OWL Profile</a>. hadActivity qualified derivations The multiple rdfs:domain assertions are intended. One is simpler and works for OWL-RL, the union is more specific but is not recognized by OWL-RL. wasActivityOfInfluence The _optional_ Generation involved in an Entity's Derivation. hadGeneration qualified derivations generatedAsDerivation hadMember expanded expanded wasMemberOf A collection is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the collections. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-collection The _optional_ Plan adopted by an Agent in Association with some Activity. Plan specifications are out of the scope of this specification. hadPlan qualified agents-responsibility wasPlanOf hadPrimarySource expanded derivations wasPrimarySourceOf hadPrimarySource property is a particular case of wasDerivedFrom (see http://www.w3.org/TR/prov-dm/#term-original-source) that aims to give credit to the source that originated some information. The _optional_ Role that an Entity assumed in the context of an Activity. For example, :baking prov:used :spoon; prov:qualified [ a prov:Usage; prov:entity :spoon; prov:hadRole roles:mixing_implement ]. This property has multiple RDFS domains to suit multiple OWL Profiles. See <a href="#owl-profile">PROV-O OWL Profile</a>. hadRole qualified agents-responsibility prov:hadRole references the Role (i.e. the function of an entity with respect to an activity), in the context of an instantaneous usage, generation, association, start, and end. wasRoleIn The _optional_ Usage involved in an Entity's Derivation. hadUsage qualified derivations wasUsedInDerivation influenced expanded agents-responsibility wasInfluencedBy Subproperties of prov:influencer are used to cite the object of an unqualified PROV-O triple whose predicate is a subproperty of prov:wasInfluencedBy (e.g. prov:used, prov:wasGeneratedBy). prov:influencer is used much like rdf:object is used. influencer qualified http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence This property and its subproperties are used in the same way as the rdf:object property, i.e. to reference the object of an unqualified prov:wasInfluencedBy or prov:influenced triple. This property is used as part of the qualified influence pattern. Subclasses of prov:Influence use these subproperties to reference the resource (Entity, Agent, or Activity) whose influence is being qualified. hadInfluence invalidated expanded entities-activities prov:invalidated is one of few inverse property defined, to allow Activity-oriented assertions in addition to Entity-oriented assertions. wasInvalidatedBy If this Activity prov:wasAssociatedWith Agent :ag, then it can qualify the Association using prov:qualifiedAssociation [ a prov:Association; prov:agent :ag; :foo :bar ]. qualifiedAssociation qualified agents-responsibility qualifiedAssociationOf If this Entity prov:wasAttributedTo Agent :ag, then it can qualify how it was influenced using prov:qualifiedAttribution [ a prov:Attribution; prov:agent :ag; :foo :bar ]. qualifiedAttribution qualified agents-responsibility qualifiedAttributionOf If this Activity prov:wasInformedBy Activity :a, then it can qualify how it was influenced using prov:qualifiedCommunication [ a prov:Communication; prov:activity :a; :foo :bar ]. qualifiedCommunication qualified entities-activities qualifiedCommunicationOf If this Agent prov:actedOnBehalfOf Agent :ag, then it can qualify how with prov:qualifiedResponsibility [ a prov:Responsibility; prov:agent :ag; :foo :bar ]. qualifiedDelegation qualified agents-responsibility qualifiedDelegationOf If this Entity prov:wasDerivedFrom Entity :e, then it can qualify how it was derived using prov:qualifiedDerivation [ a prov:Derivation; prov:entity :e; :foo :bar ]. qualifiedDerivation qualified derivations qualifiedDerivationOf If this Activity prov:wasEndedBy Entity :e1, then it can qualify how it was ended using prov:qualifiedEnd [ a prov:End; prov:entity :e1; :foo :bar ]. qualifiedEnd qualified entities-activities qualifiedEndOf If this Activity prov:generated Entity :e, then it can qualify how it performed the Generation using prov:qualifiedGeneration [ a prov:Generation; prov:entity :e; :foo :bar ]. qualifiedGeneration qualified entities-activities qualifiedGenerationOf Because prov:qualifiedInfluence is a broad relation, the more specific relations (qualifiedCommunication, qualifiedDelegation, qualifiedEnd, etc.) should be used when applicable. qualifiedInfluence qualified derivations qualifiedInfluenceOf If this Entity prov:wasInvalidatedBy Activity :a, then it can qualify how it was invalidated using prov:qualifiedInvalidation [ a prov:Invalidation; prov:activity :a; :foo :bar ]. qualifiedInvalidation qualified entities-activities qualifiedInvalidationOf If this Entity prov:hadPrimarySource Entity :e, then it can qualify how using prov:qualifiedPrimarySource [ a prov:PrimarySource; prov:entity :e; :foo :bar ]. qualifiedPrimarySource qualified derivations qualifiedSourceOf If this Entity prov:wasQuotedFrom Entity :e, then it can qualify how using prov:qualifiedQuotation [ a prov:Quotation; prov:entity :e; :foo :bar ]. qualifiedQuotation qualified derivations qualifiedQuotationOf If this Entity prov:wasRevisionOf Entity :e, then it can qualify how it was revised using prov:qualifiedRevision [ a prov:Revision; prov:entity :e; :foo :bar ]. qualifiedRevision qualified derivations revisedEntity If this Activity prov:wasStartedBy Entity :e1, then it can qualify how it was started using prov:qualifiedStart [ a prov:Start; prov:entity :e1; :foo :bar ]. qualifiedStart qualified entities-activities qualifiedStartOf If this Activity prov:used Entity :e, then it can qualify how it used it using prov:qualifiedUsage [ a prov:Usage; prov:entity :e; :foo :bar ]. qualifiedUsage qualified entities-activities qualifiedUsingActivity A prov:Entity that was used by this prov:Activity. For example, :baking prov:used :spoon, :egg, :oven . used starting-point entities-activities wasUsedBy An prov:Agent that had some (unspecified) responsibility for the occurrence of this prov:Activity. wasAssociatedWith starting-point agents-responsibility wasAssociateFor Attribution is the ascribing of an entity to an agent. wasAttributedTo starting-point agents-responsibility Attribution is the ascribing of an entity to an agent. contributed Attribution is a particular case of trace (see http://www.w3.org/TR/prov-dm/#concept-trace), in the sense that it links an entity to the agent that ascribed it. IF wasAttributedTo(e2,ag1,aAttr) holds, THEN wasInfluencedBy(e2,ag1) also holds. The more specific subproperties of prov:wasDerivedFrom (i.e., prov:wasQuotedFrom, prov:wasRevisionOf, prov:hadPrimarySource) should be used when applicable. wasDerivedFrom starting-point derivations A derivation is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity. hadDerivation Derivation is a particular case of trace (see http://www.w3.org/TR/prov-dm/#term-trace), since it links an entity to another entity that contributed to its existence. End is when an activity is deemed to have ended. An end may refer to an entity, known as trigger, that terminated the activity. wasEndedBy expanded entities-activities ended wasGeneratedBy starting-point entities-activities generated Because prov:wasInfluencedBy is a broad relation, its more specific subproperties (e.g. prov:wasInformedBy, prov:actedOnBehalfOf, prov:wasEndedBy, etc.) should be used when applicable. This property has multiple RDFS domains to suit multiple OWL Profiles. See <a href="#owl-profile">PROV-O OWL Profile</a>. wasInfluencedBy qualified agents-responsibility The sub-properties of prov:wasInfluencedBy can be elaborated in more detail using the Qualification Pattern. For example, the binary relation :baking prov:used :spoon can be qualified by asserting :baking prov:qualifiedUsage [ a prov:Usage; prov:entity :spoon; prov:atLocation :kitchen ] . Subproperties of prov:wasInfluencedBy may also be asserted directly without being qualified. prov:wasInfluencedBy should not be used without also using one of its subproperties. influenced influencee: an identifier (o2) for an entity, activity, or agent; http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence influencer: an identifier (o1) for an ancestor entity, activity, or agent that the former depends on; http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence An activity a2 is dependent on or informed by another activity a1, by way of some unspecified entity that is generated by a1 and used by a2. wasInformedBy starting-point entities-activities informed wasInvalidatedBy expanded entities-activities invalidated An entity is derived from an original entity by copying, or 'quoting', some or all of it. wasQuotedFrom expanded derivations quotedAs Quotation is a particular case of derivation (see http://www.w3.org/TR/prov-dm/#term-quotation) in which an entity is derived from an original entity by copying, or "quoting", some or all of it. Revision is a derivation (see http://www.w3.org/TR/prov-dm/#term-Revision). Moreover, according to http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#term-Revision 23 April 2012 'wasRevisionOf is a strict sub-relation of wasDerivedFrom since two entities e2 and e1 may satisfy wasDerivedFrom(e2,e1) without being a variant of each other.' Start is when an activity is deemed to have started. A start may refer to an entity, known as trigger, that initiated the activity. wasStartedBy expanded entities-activities started has measurement value has x coordinate value has z coordinate value has y coordinate value additional information abou the citation associated with the model citation text value of the confidence interval attributed to the Performance Metric concept confidence interval value Data pertaining to the contact information of the model's contact information. This is associated to the Owner Information class of the Model Card Ontology contact text Additional textual information attributed to the licensing information. custom_text Detailed textual information of the model card that is attributed to specific concepts of the Model Card Ontology. This contrasts with the "overview" data property as the "overview" has a summarized version of "documentation" documentation Model Card Report Ontology specific data properties that provide attributes to its concepts. model card text Name of the owner of the model. This is linked to the Owner Information concept of the Model Card Ontology name text Summary textual information for the concepts of the Model Card Ontology overview general numeric value associated with the Performance Metric concepts performance metric value "A description of any sensitive data that may be present in adataset. Be sure to note PII information such as names, addresses, phone numbers, etc. Preferably, such info should be scrubbed from a dataset if possible. Note that even non-identifying information, such as zip code, age, race, and gender, can be used to identify individuals when aggregated. Please describe any such fields here" Google LLC sensitive data This is data property is specific to Perfomance Metric concepts. It attributes information about the data partition used to experiment on the model. slice This is a value pertaining to a threshold value that is attributed to the Performance Metric concept for the Model Card ontology. threshold value Should be used to link a particular class (e.g. a piece of software or an algorithm) with a publication(s) which act as the primary reference(s) for that class. Allyson Lister has documentation The location from where the software can be downloaded. Allyson Lister Allyson Lister has download location Andy Brown The official date of release of software has release date notation A notation, also known as classification code, is a string of characters such as "T58.5" or "303.4833" used to uniquely identify a concept within the scope of a given concept scheme. By convention, skos:notation is used with a typed literal in the object position of the triple. The time at which an InstantaneousEvent occurred, in the form of xsd:dateTime. atTime qualified entities-activities The time at which an activity ended. See also prov:startedAtTime. endedAtTime starting-point entities-activities It is the intent that the property chain holds: (prov:qualifiedEnd o prov:atTime) rdfs:subPropertyOf prov:endedAtTime. The time at which an entity was completely created and is available for use. generatedAtTime expanded entities-activities It is the intent that the property chain holds: (prov:qualifiedGeneration o prov:atTime) rdfs:subPropertyOf prov:generatedAtTime. The time at which an entity was invalidated (i.e., no longer usable). invalidatedAtTime expanded entities-activities It is the intent that the property chain holds: (prov:qualifiedInvalidation o prov:atTime) rdfs:subPropertyOf prov:invalidatedAtTime. The time at which an activity started. See also prov:endedAtTime. startedAtTime starting-point entities-activities It is the intent that the property chain holds: (prov:qualifiedStart o prov:atTime) rdfs:subPropertyOf prov:startedAtTime. value expanded entities-activities Provides a value that is a direct representation of an entity. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-value The editor's definition comes from http://www.w3.org/TR/rdf-primer/#rdfvalue This property serves the same purpose as rdf:value, but has been reintroduced to avoid some of the definitional ambiguity in the RDF specification (specifically, 'may be used in describing structured values'). An ontology of biological or bioinformatics concepts and relations, a controlled vocabulary, structured glossary etc. Ontologies Ontology A graphical 2D tabular representation of gene expression data, typically derived from a DNA microarray experiment. Heat map Heatmap Image, hybridisation or some other data arising from a study of gene expression, typically profiling or quantification. Gene product profile Gene product quantification data Gene transcription profile Gene transcription quantification data Microarray data Non-coding RNA profile Non-coding RNA quantification data RNA profile RNA quantification data RNA-seq data Transcriptome profile Transcriptome quantification data mRNA profile mRNA quantification data Gene expression data Microarray data Biological or biomedical data has been rendered into an image, typically for display on screen. Image data Image Groupings of gene expression profiles according to a clustering algorithm. Clustered gene expression profiles PDBML Format of Taverna workflows. Taverna workflow format newick FASTA format Genbank entry format. GenBank GenBank format GFF html, or HyperText Markup Language in full, is a data format specification is a markup language for web pages and is the publishing language of the World Wide Web. http://www.w3.org/TR/html401/ James Malone HTML Extensible Markup Language (XML) is a standard set of rules for encoding documents in a machine-readable form defined by the W3C. James Malone XML binary format OBO format is the text file format used by OBO-Edit, the open source, platform-independent application for viewing and editing ontologies. OBO flat file format OBO Flat File Format Systems Biology Markup Language (SBML) is a machine-readable format for representing models. It's oriented towards describing systems where biological entities are involved in, and modified by, processes that occur over time. Systems Biology Markup Language http://sbml.org SBML BED format The PSI-MI format is an acronym for the Proteomics Standards Initiative - Molecular Interaction format. It provides an XML standard for molecular interactions and is supported by many molecular interaction databases and tools. PSI-MI format PSI-MIF Modified from http://wiki.cytoscape.org/GettingStarted, accessed 20 June 2012. Allyson Lister MAGE-ML MAGE-TAB is a tab delimited data format comprimising of ADF file for array design, IDFfor experimental design, SDRF for sample data relationships and associated data files. http://www.mged.org/mage-tab/ A simple spreadsheet-based, MIAME-supportive format for microarray data: MAGE-TAB. MAGE-TAB CopasiML, the native format of COPASI. CopasiML Search or query a data resource and retrieve entries and / or annotation. Database retrieval Query Query and retrieval Annotate a genome sequence with terms from a controlled vocabulary. Metagenome annotation Genome annotation Model or simulate some biological entity or system, typically using mathematical techniques including dynamical systems, statistical models, differential equations, and game theoretic models. Mathematical modelling Modelling and simulation data visualization algorithm data cleaning algorithm data selection algorithm data integration algorithm A data processing task is an information processing objective that specifies the objective that a data processing algorithm execution process needs to achieve when executed on a dataset to produce as output a new dataset. data processing task data construction algorithm Allyson Lister A data processing algorithm is an algorithm that has as its objective a data processing task and has data items both as input and output. data processing algorithm APOLLO_SV:00000008 A planned process that has specified output a software product and that involves the creation of source code. Mathias Brochhausen William R. Hogan http://en.wikipedia.org/wiki/Software_development A planned process resulting in a software product involving the creation of source code. software development APOLLO_SV:00000032 A measurement datum that is the output of counting. Mathias Brochhausen A measurement datum that is the output of counting. count APOLLO_SV:00000033 The planned process of finding the number of elements in a finite set of objects. Mathias Brochhausen http://en.wikipedia.org/wiki/Counting The planned process of finding the number of elements in a finite set of objects. counting APOLLO_SV:00000522 software source code version control repository A document that comprises at least one source code module and provenance data about who contributed the set of files making up the module(s), and optionally comprises also multiple versions of files with detailed change history about who committed files and when, a license for the software, readme files, documentation, executables, etc. William R. Hogan Refers to the stuff that lives on GitHub, not to GitHub or the git software on which it is based source code repository APOLLO_SV:00000524 process of compiling software A planned process that converts human-written or curated software into a machine-executable or interpretable set of instructions. William R. Hogan It's compiling "software" (scare quotes) and not "source code" because you can compile Java bytecode to machine code, and Java bytecode is not technically "source code". Compiling source code would be a subclass of this class (as would compiling Java bytecode, etc.). Source code can be automatically generated to some extent, but we're assuming humans still curate it minimally. Also, in the case of Java and its JVM, it's machine interpretable instructions, not directly executable. Ditto for other languages with intermediate form like Java byte code. compiling software APOLLO_SV:00000796 creating a data set A planned process that has a data set as its specified output. William R. Hogan data set creation dataset creation dataset creating BFO:0000001 entity Entity Julius Caesar Verdi’s Requiem the Second World War your body mass index BFO 2 Reference: In all areas of empirical inquiry we encounter general terms of two sorts. First are general terms which refer to universals or types:animaltuberculosissurgical procedurediseaseSecond, are general terms used to refer to groups of entities which instantiate a given universal but do not correspond to the extension of any subuniversal of that universal because there is nothing intrinsic to the entities in question by virtue of which they – and only they – are counted as belonging to the given group. Examples are: animal purchased by the Emperortuberculosis diagnosed on a Wednesdaysurgical procedure performed on a patient from Stockholmperson identified as candidate for clinical trial #2056-555person who is signatory of Form 656-PPVpainting by Leonardo da VinciSuch terms, which represent what are called ‘specializations’ in [81 Entity doesn't have a closure axiom because the subclasses don't necessarily exhaust all possibilites. For example Werner Ceusters 'portions of reality' include 4 sorts, entities (as BFO construes them), universals, configurations, and relations. It is an open question as to whether entities as construed in BFO will at some point also include these other portions of reality. See, for example, 'How to track absolutely everything' at http://www.referent-tracking.com/_RTU/papers/CeustersICbookRevised.pdf An entity is anything that exists or has existed or will exist. (axiom label in BFO2 Reference: [001-001]) entity Entity doesn't have a closure axiom because the subclasses don't necessarily exhaust all possibilites. For example Werner Ceusters 'portions of reality' include 4 sorts, entities (as BFO construes them), universals, configurations, and relations. It is an open question as to whether entities as construed in BFO will at some point also include these other portions of reality. See, for example, 'How to track absolutely everything' at http://www.referent-tracking.com/_RTU/papers/CeustersICbookRevised.pdf per discussion with Barry Smith An entity is anything that exists or has existed or will exist. (axiom label in BFO2 Reference: [001-001]) BFO:0000002 continuant Continuant An entity that exists in full at any time in which it exists at all, persists through time while maintaining its identity and has no temporal parts. BFO 2 Reference: Continuant entities are entities which can be sliced to yield parts only along the spatial dimension, yielding for example the parts of your table which we call its legs, its top, its nails. ‘My desk stretches from the window to the door. It has spatial parts, and can be sliced (in space) in two. With respect to time, however, a thing is a continuant.’ [60, p. 240 Continuant doesn't have a closure axiom because the subclasses don't necessarily exhaust all possibilites. For example, in an expansion involving bringing in some of Ceuster's other portions of reality, questions are raised as to whether universals are continuants A continuant is an entity that persists, endures, or continues to exist through time while maintaining its identity. (axiom label in BFO2 Reference: [008-002]) if b is a continuant and if, for some t, c has_continuant_part b at t, then c is a continuant. (axiom label in BFO2 Reference: [126-001]) if b is a continuant and if, for some t, cis continuant_part of b at t, then c is a continuant. (axiom label in BFO2 Reference: [009-002]) if b is a material entity, then there is some temporal interval (referred to below as a one-dimensional temporal region) during which b exists. (axiom label in BFO2 Reference: [011-002]) (forall (x y) (if (and (Continuant x) (exists (t) (continuantPartOfAt y x t))) (Continuant y))) // axiom label in BFO2 CLIF: [009-002] (forall (x y) (if (and (Continuant x) (exists (t) (hasContinuantPartOfAt y x t))) (Continuant y))) // axiom label in BFO2 CLIF: [126-001] (forall (x) (if (Continuant x) (Entity x))) // axiom label in BFO2 CLIF: [008-002] (forall (x) (if (Material Entity x) (exists (t) (and (TemporalRegion t) (existsAt x t))))) // axiom label in BFO2 CLIF: [011-002] continuant Continuant doesn't have a closure axiom because the subclasses don't necessarily exhaust all possibilites. For example, in an expansion involving bringing in some of Ceuster's other portions of reality, questions are raised as to whether universals are continuants A continuant is an entity that persists, endures, or continues to exist through time while maintaining its identity. (axiom label in BFO2 Reference: [008-002]) if b is a continuant and if, for some t, c has_continuant_part b at t, then c is a continuant. (axiom label in BFO2 Reference: [126-001]) if b is a continuant and if, for some t, cis continuant_part of b at t, then c is a continuant. (axiom label in BFO2 Reference: [009-002]) if b is a material entity, then there is some temporal interval (referred to below as a one-dimensional temporal region) during which b exists. (axiom label in BFO2 Reference: [011-002]) (forall (x y) (if (and (Continuant x) (exists (t) (continuantPartOfAt y x t))) (Continuant y))) // axiom label in BFO2 CLIF: [009-002] (forall (x y) (if (and (Continuant x) (exists (t) (hasContinuantPartOfAt y x t))) (Continuant y))) // axiom label in BFO2 CLIF: [126-001] (forall (x) (if (Continuant x) (Entity x))) // axiom label in BFO2 CLIF: [008-002] (forall (x) (if (Material Entity x) (exists (t) (and (TemporalRegion t) (existsAt x t))))) // axiom label in BFO2 CLIF: [011-002] BFO:0000003 occurrent Occurrent An entity that has temporal parts and that happens, unfolds or develops through time. BFO 2 Reference: every occurrent that is not a temporal or spatiotemporal region is s-dependent on some independent continuant that is not a spatial region BFO 2 Reference: s-dependence obtains between every process and its participants in the sense that, as a matter of necessity, this process could not have existed unless these or those participants existed also. A process may have a succession of participants at different phases of its unfolding. Thus there may be different players on the field at different times during the course of a football game; but the process which is the entire game s-depends_on all of these players nonetheless. Some temporal parts of this process will s-depend_on on only some of the players. Occurrent doesn't have a closure axiom because the subclasses don't necessarily exhaust all possibilites. An example would be the sum of a process and the process boundary of another process. Simons uses different terminology for relations of occurrents to regions: Denote the spatio-temporal location of a given occurrent e by 'spn[e]' and call this region its span. We may say an occurrent is at its span, in any larger region, and covers any smaller region. Now suppose we have fixed a frame of reference so that we can speak not merely of spatio-temporal but also of spatial regions (places) and temporal regions (times). The spread of an occurrent, (relative to a frame of reference) is the space it exactly occupies, and its spell is likewise the time it exactly occupies. We write 'spr[e]' and `spl[e]' respectively for the spread and spell of e, omitting mention of the frame. An occurrent is an entity that unfolds itself in time or it is the instantaneous boundary of such an entity (for example a beginning or an ending) or it is a temporal or spatiotemporal region which such an entity occupies_temporal_region or occupies_spatiotemporal_region. (axiom label in BFO2 Reference: [077-002]) Every occurrent occupies_spatiotemporal_region some spatiotemporal region. (axiom label in BFO2 Reference: [108-001]) b is an occurrent entity iff b is an entity that has temporal parts. (axiom label in BFO2 Reference: [079-001]) (forall (x) (if (Occurrent x) (exists (r) (and (SpatioTemporalRegion r) (occupiesSpatioTemporalRegion x r))))) // axiom label in BFO2 CLIF: [108-001] (forall (x) (iff (Occurrent x) (and (Entity x) (exists (y) (temporalPartOf y x))))) // axiom label in BFO2 CLIF: [079-001] occurrent Occurrent doesn't have a closure axiom because the subclasses don't necessarily exhaust all possibilites. An example would be the sum of a process and the process boundary of another process. per discussion with Barry Smith Simons uses different terminology for relations of occurrents to regions: Denote the spatio-temporal location of a given occurrent e by 'spn[e]' and call this region its span. We may say an occurrent is at its span, in any larger region, and covers any smaller region. Now suppose we have fixed a frame of reference so that we can speak not merely of spatio-temporal but also of spatial regions (places) and temporal regions (times). The spread of an occurrent, (relative to a frame of reference) is the space it exactly occupies, and its spell is likewise the time it exactly occupies. We write 'spr[e]' and `spl[e]' respectively for the spread and spell of e, omitting mention of the frame. An occurrent is an entity that unfolds itself in time or it is the instantaneous boundary of such an entity (for example a beginning or an ending) or it is a temporal or spatiotemporal region which such an entity occupies_temporal_region or occupies_spatiotemporal_region. (axiom label in BFO2 Reference: [077-002]) Every occurrent occupies_spatiotemporal_region some spatiotemporal region. (axiom label in BFO2 Reference: [108-001]) b is an occurrent entity iff b is an entity that has temporal parts. (axiom label in BFO2 Reference: [079-001]) (forall (x) (if (Occurrent x) (exists (r) (and (SpatioTemporalRegion r) (occupiesSpatioTemporalRegion x r))))) // axiom label in BFO2 CLIF: [108-001] (forall (x) (iff (Occurrent x) (and (Entity x) (exists (y) (temporalPartOf y x))))) // axiom label in BFO2 CLIF: [079-001] BFO:0000004 ic IndependentContinuant a chair a heart a leg a molecule a spatial region an atom an orchestra. an organism the bottom right portion of a human torso the interior of your mouth A continuant that is a bearer of quality and realizable entity entities, in which other entities inhere and which itself cannot inhere in anything. b is an independent continuant = Def. b is a continuant which is such that there is no c and no t such that b s-depends_on c at t. (axiom label in BFO2 Reference: [017-002]) For any independent continuant b and any time t there is some spatial region r such that b is located_in r at t. (axiom label in BFO2 Reference: [134-001]) For every independent continuant b and time t during the region of time spanned by its life, there are entities which s-depends_on b during t. (axiom label in BFO2 Reference: [018-002]) (forall (x t) (if (IndependentContinuant x) (exists (r) (and (SpatialRegion r) (locatedInAt x r t))))) // axiom label in BFO2 CLIF: [134-001] (forall (x t) (if (and (IndependentContinuant x) (existsAt x t)) (exists (y) (and (Entity y) (specificallyDependsOnAt y x t))))) // axiom label in BFO2 CLIF: [018-002] (iff (IndependentContinuant a) (and (Continuant a) (not (exists (b t) (specificallyDependsOnAt a b t))))) // axiom label in BFO2 CLIF: [017-002] independent continuant b is an independent continuant = Def. b is a continuant which is such that there is no c and no t such that b s-depends_on c at t. (axiom label in BFO2 Reference: [017-002]) For any independent continuant b and any time t there is some spatial region r such that b is located_in r at t. (axiom label in BFO2 Reference: [134-001]) For every independent continuant b and time t during the region of time spanned by its life, there are entities which s-depends_on b during t. (axiom label in BFO2 Reference: [018-002]) (forall (x t) (if (IndependentContinuant x) (exists (r) (and (SpatialRegion r) (locatedInAt x r t))))) // axiom label in BFO2 CLIF: [134-001] (forall (x t) (if (and (IndependentContinuant x) (existsAt x t)) (exists (y) (and (Entity y) (specificallyDependsOnAt y x t))))) // axiom label in BFO2 CLIF: [018-002] (iff (IndependentContinuant a) (and (Continuant a) (not (exists (b t) (specificallyDependsOnAt a b t))))) // axiom label in BFO2 CLIF: [017-002] BFO:0000006 s-region SpatialRegion BFO 2 Reference: Spatial regions do not participate in processes. Spatial region doesn't have a closure axiom because the subclasses don't exhaust all possibilites. An example would be the union of a spatial point and a spatial line that doesn't overlap the point, or two spatial lines that intersect at a single point. In both cases the resultant spatial region is neither 0-dimensional, 1-dimensional, 2-dimensional, or 3-dimensional. A spatial region is a continuant entity that is a continuant_part_of spaceR as defined relative to some frame R. (axiom label in BFO2 Reference: [035-001]) All continuant parts of spatial regions are spatial regions. (axiom label in BFO2 Reference: [036-001]) (forall (x y t) (if (and (SpatialRegion x) (continuantPartOfAt y x t)) (SpatialRegion y))) // axiom label in BFO2 CLIF: [036-001] (forall (x) (if (SpatialRegion x) (Continuant x))) // axiom label in BFO2 CLIF: [035-001] spatial region Spatial region doesn't have a closure axiom because the subclasses don't exhaust all possibilites. An example would be the union of a spatial point and a spatial line that doesn't overlap the point, or two spatial lines that intersect at a single point. In both cases the resultant spatial region is neither 0-dimensional, 1-dimensional, 2-dimensional, or 3-dimensional. per discussion with Barry Smith A spatial region is a continuant entity that is a continuant_part_of spaceR as defined relative to some frame R. (axiom label in BFO2 Reference: [035-001]) All continuant parts of spatial regions are spatial regions. (axiom label in BFO2 Reference: [036-001]) (forall (x y t) (if (and (SpatialRegion x) (continuantPartOfAt y x t)) (SpatialRegion y))) // axiom label in BFO2 CLIF: [036-001] (forall (x) (if (SpatialRegion x) (Continuant x))) // axiom label in BFO2 CLIF: [035-001] BFO:0000008 t-region TemporalRegion Temporal region doesn't have a closure axiom because the subclasses don't exhaust all possibilites. An example would be the mereological sum of a temporal instant and a temporal interval that doesn't overlap the instant. In this case the resultant temporal region is neither 0-dimensional nor 1-dimensional A temporal region is an occurrent entity that is part of time as defined relative to some reference frame. (axiom label in BFO2 Reference: [100-001]) All parts of temporal regions are temporal regions. (axiom label in BFO2 Reference: [101-001]) Every temporal region t is such that t occupies_temporal_region t. (axiom label in BFO2 Reference: [119-002]) (forall (r) (if (TemporalRegion r) (occupiesTemporalRegion r r))) // axiom label in BFO2 CLIF: [119-002] (forall (x y) (if (and (TemporalRegion x) (occurrentPartOf y x)) (TemporalRegion y))) // axiom label in BFO2 CLIF: [101-001] (forall (x) (if (TemporalRegion x) (Occurrent x))) // axiom label in BFO2 CLIF: [100-001] temporal region Temporal region doesn't have a closure axiom because the subclasses don't exhaust all possibilites. An example would be the mereological sum of a temporal instant and a temporal interval that doesn't overlap the instant. In this case the resultant temporal region is neither 0-dimensional nor 1-dimensional per discussion with Barry Smith A temporal region is an occurrent entity that is part of time as defined relative to some reference frame. (axiom label in BFO2 Reference: [100-001]) All parts of temporal regions are temporal regions. (axiom label in BFO2 Reference: [101-001]) Every temporal region t is such that t occupies_temporal_region t. (axiom label in BFO2 Reference: [119-002]) (forall (r) (if (TemporalRegion r) (occupiesTemporalRegion r r))) // axiom label in BFO2 CLIF: [119-002] (forall (x y) (if (and (TemporalRegion x) (occurrentPartOf y x)) (TemporalRegion y))) // axiom label in BFO2 CLIF: [101-001] (forall (x) (if (TemporalRegion x) (Occurrent x))) // axiom label in BFO2 CLIF: [100-001] BFO:0000009 2d-s-region TwoDimensionalSpatialRegion an infinitely thin plane in space. the surface of a sphere-shaped part of space A two-dimensional spatial region is a spatial region that is of two dimensions. (axiom label in BFO2 Reference: [039-001]) (forall (x) (if (TwoDimensionalSpatialRegion x) (SpatialRegion x))) // axiom label in BFO2 CLIF: [039-001] two-dimensional spatial region A two-dimensional spatial region is a spatial region that is of two dimensions. (axiom label in BFO2 Reference: [039-001]) (forall (x) (if (TwoDimensionalSpatialRegion x) (SpatialRegion x))) // axiom label in BFO2 CLIF: [039-001] BFO:0000011 st-region SpatiotemporalRegion the spatiotemporal region occupied by a human life the spatiotemporal region occupied by a process of cellular meiosis. the spatiotemporal region occupied by the development of a cancer tumor A spatiotemporal region is an occurrent entity that is part of spacetime. (axiom label in BFO2 Reference: [095-001]) All parts of spatiotemporal regions are spatiotemporal regions. (axiom label in BFO2 Reference: [096-001]) Each spatiotemporal region at any time t projects_onto some spatial region at t. (axiom label in BFO2 Reference: [099-001]) Each spatiotemporal region projects_onto some temporal region. (axiom label in BFO2 Reference: [098-001]) Every spatiotemporal region occupies_spatiotemporal_region itself. Every spatiotemporal region s is such that s occupies_spatiotemporal_region s. (axiom label in BFO2 Reference: [107-002]) (forall (r) (if (SpatioTemporalRegion r) (occupiesSpatioTemporalRegion r r))) // axiom label in BFO2 CLIF: [107-002] (forall (x t) (if (SpatioTemporalRegion x) (exists (y) (and (SpatialRegion y) (spatiallyProjectsOntoAt x y t))))) // axiom label in BFO2 CLIF: [099-001] (forall (x y) (if (and (SpatioTemporalRegion x) (occurrentPartOf y x)) (SpatioTemporalRegion y))) // axiom label in BFO2 CLIF: [096-001] (forall (x) (if (SpatioTemporalRegion x) (Occurrent x))) // axiom label in BFO2 CLIF: [095-001] (forall (x) (if (SpatioTemporalRegion x) (exists (y) (and (TemporalRegion y) (temporallyProjectsOnto x y))))) // axiom label in BFO2 CLIF: [098-001] spatiotemporal region A spatiotemporal region is an occurrent entity that is part of spacetime. (axiom label in BFO2 Reference: [095-001]) All parts of spatiotemporal regions are spatiotemporal regions. (axiom label in BFO2 Reference: [096-001]) Each spatiotemporal region at any time t projects_onto some spatial region at t. (axiom label in BFO2 Reference: [099-001]) Each spatiotemporal region projects_onto some temporal region. (axiom label in BFO2 Reference: [098-001]) Every spatiotemporal region s is such that s occupies_spatiotemporal_region s. (axiom label in BFO2 Reference: [107-002]) (forall (r) (if (SpatioTemporalRegion r) (occupiesSpatioTemporalRegion r r))) // axiom label in BFO2 CLIF: [107-002] (forall (x t) (if (SpatioTemporalRegion x) (exists (y) (and (SpatialRegion y) (spatiallyProjectsOntoAt x y t))))) // axiom label in BFO2 CLIF: [099-001] (forall (x y) (if (and (SpatioTemporalRegion x) (occurrentPartOf y x)) (SpatioTemporalRegion y))) // axiom label in BFO2 CLIF: [096-001] (forall (x) (if (SpatioTemporalRegion x) (Occurrent x))) // axiom label in BFO2 CLIF: [095-001] (forall (x) (if (SpatioTemporalRegion x) (exists (y) (and (TemporalRegion y) (temporallyProjectsOnto x y))))) // axiom label in BFO2 CLIF: [098-001] BFO:0000015 process Process a process of cell-division, \ a beating of the heart a process of meiosis a process of sleeping the course of a disease the flight of a bird the life of an organism your process of aging. An occurrent that has temporal proper parts and for some time t, p s-depends_on some material entity at t. p is a process = Def. p is an occurrent that has temporal proper parts and for some time t, p s-depends_on some material entity at t. (axiom label in BFO2 Reference: [083-003]) BFO 2 Reference: The realm of occurrents is less pervasively marked by the presence of natural units than is the case in the realm of independent continuants. Thus there is here no counterpart of ‘object’. In BFO 1.0 ‘process’ served as such a counterpart. In BFO 2.0 ‘process’ is, rather, the occurrent counterpart of ‘material entity’. Those natural – as contrasted with engineered, which here means: deliberately executed – units which do exist in the realm of occurrents are typically either parasitic on the existence of natural units on the continuant side, or they are fiat in nature. Thus we can count lives; we can count football games; we can count chemical reactions performed in experiments or in chemical manufacturing. We cannot count the processes taking place, for instance, in an episode of insect mating behavior.Even where natural units are identifiable, for example cycles in a cyclical process such as the beating of a heart or an organism’s sleep/wake cycle, the processes in question form a sequence with no discontinuities (temporal gaps) of the sort that we find for instance where billiard balls or zebrafish or planets are separated by clear spatial gaps. Lives of organisms are process units, but they too unfold in a continuous series from other, prior processes such as fertilization, and they unfold in turn in continuous series of post-life processes such as post-mortem decay. Clear examples of boundaries of processes are almost always of the fiat sort (midnight, a time of death as declared in an operating theater or on a death certificate, the initiation of a state of war) (iff (Process a) (and (Occurrent a) (exists (b) (properTemporalPartOf b a)) (exists (c t) (and (MaterialEntity c) (specificallyDependsOnAt a c t))))) // axiom label in BFO2 CLIF: [083-003] process p is a process = Def. p is an occurrent that has temporal proper parts and for some time t, p s-depends_on some material entity at t. (axiom label in BFO2 Reference: [083-003]) (iff (Process a) (and (Occurrent a) (exists (b) (properTemporalPartOf b a)) (exists (c t) (and (MaterialEntity c) (specificallyDependsOnAt a c t))))) // axiom label in BFO2 CLIF: [083-003] BFO:0000016 disposition Disposition an atom of element X has the disposition to decay to an atom of element Y certain people have a predisposition to colon cancer children are innately disposed to categorize objects in certain ways. the cell wall is disposed to filter chemicals in endocytosis and exocytosis BFO 2 Reference: Dispositions exist along a strength continuum. Weaker forms of disposition are realized in only a fraction of triggering cases. These forms occur in a significant number of cases of a similar type. b is a disposition means: b is a realizable entity & b’s bearer is some material entity & b is such that if it ceases to exist, then its bearer is physically changed, & b’s realization occurs when and because this bearer is in some special physical circumstances, & this realization occurs in virtue of the bearer’s physical make-up. (axiom label in BFO2 Reference: [062-002]) If b is a realizable entity then for all t at which b exists, b s-depends_on some material entity at t. (axiom label in BFO2 Reference: [063-002]) (forall (x t) (if (and (RealizableEntity x) (existsAt x t)) (exists (y) (and (MaterialEntity y) (specificallyDepends x y t))))) // axiom label in BFO2 CLIF: [063-002] (forall (x) (if (Disposition x) (and (RealizableEntity x) (exists (y) (and (MaterialEntity y) (bearerOfAt x y t)))))) // axiom label in BFO2 CLIF: [062-002] disposition b is a disposition means: b is a realizable entity & b’s bearer is some material entity & b is such that if it ceases to exist, then its bearer is physically changed, & b’s realization occurs when and because this bearer is in some special physical circumstances, & this realization occurs in virtue of the bearer’s physical make-up. (axiom label in BFO2 Reference: [062-002]) If b is a realizable entity then for all t at which b exists, b s-depends_on some material entity at t. (axiom label in BFO2 Reference: [063-002]) (forall (x t) (if (and (RealizableEntity x) (existsAt x t)) (exists (y) (and (MaterialEntity y) (specificallyDepends x y t))))) // axiom label in BFO2 CLIF: [063-002] (forall (x) (if (Disposition x) (and (RealizableEntity x) (exists (y) (and (MaterialEntity y) (bearerOfAt x y t)))))) // axiom label in BFO2 CLIF: [062-002] BFO:0000017 realizable RealizableEntity the disposition of this piece of metal to conduct electricity. the disposition of your blood to coagulate the function of your reproductive organs the role of being a doctor the role of this boundary to delineate where Utah and Colorado meet A specifically dependent continuant that inheres in continuant entities and are not exhibited in full at every time in which it inheres in an entity or group of entities. The exhibition or actualization of a realizable entity is a particular manifestation, functioning or process that occurs under certain circumstances. To say that b is a realizable entity is to say that b is a specifically dependent continuant that inheres in some independent continuant which is not a spatial region and is of a type instances of which are realized in processes of a correlated type. (axiom label in BFO2 Reference: [058-002]) All realizable dependent continuants have independent continuants that are not spatial regions as their bearers. (axiom label in BFO2 Reference: [060-002]) (forall (x t) (if (RealizableEntity x) (exists (y) (and (IndependentContinuant y) (not (SpatialRegion y)) (bearerOfAt y x t))))) // axiom label in BFO2 CLIF: [060-002] (forall (x) (if (RealizableEntity x) (and (SpecificallyDependentContinuant x) (exists (y) (and (IndependentContinuant y) (not (SpatialRegion y)) (inheresIn x y)))))) // axiom label in BFO2 CLIF: [058-002] realizable entity To say that b is a realizable entity is to say that b is a specifically dependent continuant that inheres in some independent continuant which is not a spatial region and is of a type instances of which are realized in processes of a correlated type. (axiom label in BFO2 Reference: [058-002]) All realizable dependent continuants have independent continuants that are not spatial regions as their bearers. (axiom label in BFO2 Reference: [060-002]) (forall (x t) (if (RealizableEntity x) (exists (y) (and (IndependentContinuant y) (not (SpatialRegion y)) (bearerOfAt y x t))))) // axiom label in BFO2 CLIF: [060-002] (forall (x) (if (RealizableEntity x) (and (SpecificallyDependentContinuant x) (exists (y) (and (IndependentContinuant y) (not (SpatialRegion y)) (inheresIn x y)))))) // axiom label in BFO2 CLIF: [058-002] BFO:0000018 0d-s-region ZeroDimensionalSpatialRegion A zero-dimensional spatial region is a point in space. (axiom label in BFO2 Reference: [037-001]) (forall (x) (if (ZeroDimensionalSpatialRegion x) (SpatialRegion x))) // axiom label in BFO2 CLIF: [037-001] zero-dimensional spatial region A zero-dimensional spatial region is a point in space. (axiom label in BFO2 Reference: [037-001]) (forall (x) (if (ZeroDimensionalSpatialRegion x) (SpatialRegion x))) // axiom label in BFO2 CLIF: [037-001] BFO:0000019 quality Quality the ambient temperature of this portion of air the color of a tomato the length of the circumference of your waist the mass of this piece of gold. the shape of your nose the shape of your nostril a quality is a specifically dependent continuant that, in contrast to roles and dispositions, does not require any further process in order to be realized. (axiom label in BFO2 Reference: [055-001]) If an entity is a quality at any time that it exists, then it is a quality at every time that it exists. (axiom label in BFO2 Reference: [105-001]) (forall (x) (if (Quality x) (SpecificallyDependentContinuant x))) // axiom label in BFO2 CLIF: [055-001] (forall (x) (if (exists (t) (and (existsAt x t) (Quality x))) (forall (t_1) (if (existsAt x t_1) (Quality x))))) // axiom label in BFO2 CLIF: [105-001] quality a quality is a specifically dependent continuant that, in contrast to roles and dispositions, does not require any further process in order to be realized. (axiom label in BFO2 Reference: [055-001]) If an entity is a quality at any time that it exists, then it is a quality at every time that it exists. (axiom label in BFO2 Reference: [105-001]) (forall (x) (if (Quality x) (SpecificallyDependentContinuant x))) // axiom label in BFO2 CLIF: [055-001] (forall (x) (if (exists (t) (and (existsAt x t) (Quality x))) (forall (t_1) (if (existsAt x t_1) (Quality x))))) // axiom label in BFO2 CLIF: [105-001] BFO:0000020 sdc SpecificallyDependentContinuant Reciprocal specifically dependent continuants: the function of this key to open this lock and the mutually dependent disposition of this lock: to be opened by this key of one-sided specifically dependent continuants: the mass of this tomato of relational dependent continuants (multiple bearers): John’s love for Mary, the ownership relation between John and this statue, the relation of authority between John and his subordinates. the disposition of this fish to decay the function of this heart: to pump blood the mutual dependence of proton donors and acceptors in chemical reactions [79 the mutual dependence of the role predator and the role prey as played by two organisms in a given interaction the pink color of a medium rare piece of grilled filet mignon at its center the role of being a doctor the shape of this hole. the smell of this portion of mozzarella b is a specifically dependent continuant = Def. b is a continuant & there is some independent continuant c which is not a spatial region and which is such that b s-depends_on c at every time t during the course of b’s existence. (axiom label in BFO2 Reference: [050-003]) Specifically dependent continuant doesn't have a closure axiom because the subclasses don't necessarily exhaust all possibilites. We're not sure what else will develop here, but for example there are questions such as what are promises, obligation, etc. (iff (SpecificallyDependentContinuant a) (and (Continuant a) (forall (t) (if (existsAt a t) (exists (b) (and (IndependentContinuant b) (not (SpatialRegion b)) (specificallyDependsOnAt a b t))))))) // axiom label in BFO2 CLIF: [050-003] specifically dependent continuant b is a specifically dependent continuant = Def. b is a continuant & there is some independent continuant c which is not a spatial region and which is such that b s-depends_on c at every time t during the course of b’s existence. (axiom label in BFO2 Reference: [050-003]) Specifically dependent continuant doesn't have a closure axiom because the subclasses don't necessarily exhaust all possibilites. We're not sure what else will develop here, but for example there are questions such as what are promises, obligation, etc. per discussion with Barry Smith (iff (SpecificallyDependentContinuant a) (and (Continuant a) (forall (t) (if (existsAt a t) (exists (b) (and (IndependentContinuant b) (not (SpatialRegion b)) (specificallyDependsOnAt a b t))))))) // axiom label in BFO2 CLIF: [050-003] BFO:0000023 role Role John’s role of husband to Mary is dependent on Mary’s role of wife to John, and both are dependent on the object aggregate comprising John and Mary as member parts joined together through the relational quality of being married. the priest role the role of a boundary to demarcate two neighboring administrative territories the role of a building in serving as a military target the role of a stone in marking a property boundary the role of subject in a clinical trial the student role A realizable entity the manifestation of which brings about some result or end that is not essential to a continuant in virtue of the kind of thing that it is but that can be served or participated in by that kind of continuant in some kinds of natural, social or institutional contexts. BFO 2 Reference: One major family of examples of non-rigid universals involves roles, and ontologies developed for corresponding administrative purposes may consist entirely of representatives of entities of this sort. Thus ‘professor’, defined as follows,b instance_of professor at t =Def. there is some c, c instance_of professor role & c inheres_in b at t.denotes a non-rigid universal and so also do ‘nurse’, ‘student’, ‘colonel’, ‘taxpayer’, and so forth. (These terms are all, in the jargon of philosophy, phase sortals.) By using role terms in definitions, we can create a BFO conformant treatment of such entities drawing on the fact that, while an instance of professor may be simultaneously an instance of trade union member, no instance of the type professor role is also (at any time) an instance of the type trade union member role (any more than any instance of the type color is at any time an instance of the type length).If an ontology of employment positions should be defined in terms of roles following the above pattern, this enables the ontology to do justice to the fact that individuals instantiate the corresponding universals – professor, sergeant, nurse – only during certain phases in their lives. b is a role means: b is a realizable entity & b exists because there is some single bearer that is in some special physical, social, or institutional set of circumstances in which this bearer does not have to be& b is not such that, if it ceases to exist, then the physical make-up of the bearer is thereby changed. (axiom label in BFO2 Reference: [061-001]) (forall (x) (if (Role x) (RealizableEntity x))) // axiom label in BFO2 CLIF: [061-001] role b is a role means: b is a realizable entity & b exists because there is some single bearer that is in some special physical, social, or institutional set of circumstances in which this bearer does not have to be& b is not such that, if it ceases to exist, then the physical make-up of the bearer is thereby changed. (axiom label in BFO2 Reference: [061-001]) (forall (x) (if (Role x) (RealizableEntity x))) // axiom label in BFO2 CLIF: [061-001] BFO:0000024 fiat-object-part FiatObjectPart or with divisions drawn by cognitive subjects for practical reasons, such as the division of a cake (before slicing) into (what will become) slices (and thus member parts of an object aggregate). However, this does not mean that fiat object parts are dependent for their existence on divisions or delineations effected by cognitive subjects. If, for example, it is correct to conceive geological layers of the Earth as fiat object parts of the Earth, then even though these layers were first delineated in recent times, still existed long before such delineation and what holds of these layers (for example that the oldest layers are also the lowest layers) did not begin to hold because of our acts of delineation.Treatment of material entity in BFOExamples viewed by some as problematic cases for the trichotomy of fiat object part, object, and object aggregate include: a mussel on (and attached to) a rock, a slime mold, a pizza, a cloud, a galaxy, a railway train with engine and multiple carriages, a clonal stand of quaking aspen, a bacterial community (biofilm), a broken femur. Note that, as Aristotle already clearly recognized, such problematic cases – which lie at or near the penumbra of instances defined by the categories in question – need not invalidate these categories. The existence of grey objects does not prove that there are not objects which are black and objects which are white; the existence of mules does not prove that there are not objects which are donkeys and objects which are horses. It does, however, show that the examples in question need to be addressed carefully in order to show how they can be fitted into the proposed scheme, for example by recognizing additional subdivisions [29 the FMA:regional parts of an intact human body. the Western hemisphere of the Earth the division of the brain into regions the division of the planet into hemispheres the dorsal and ventral surfaces of the body the upper and lower lobes of the left lung BFO 2 Reference: Most examples of fiat object parts are associated with theoretically drawn divisions b is a fiat object part = Def. b is a material entity which is such that for all times t, if b exists at t then there is some object c such that b proper continuant_part of c at t and c is demarcated from the remainder of c by a two-dimensional continuant fiat boundary. (axiom label in BFO2 Reference: [027-004]) (forall (x) (if (FiatObjectPart x) (and (MaterialEntity x) (forall (t) (if (existsAt x t) (exists (y) (and (Object y) (properContinuantPartOfAt x y t)))))))) // axiom label in BFO2 CLIF: [027-004] fiat object part b is a fiat object part = Def. b is a material entity which is such that for all times t, if b exists at t then there is some object c such that b proper continuant_part of c at t and c is demarcated from the remainder of c by a two-dimensional continuant fiat boundary. (axiom label in BFO2 Reference: [027-004]) (forall (x) (if (FiatObjectPart x) (and (MaterialEntity x) (forall (t) (if (existsAt x t) (exists (y) (and (Object y) (properContinuantPartOfAt x y t)))))))) // axiom label in BFO2 CLIF: [027-004] BFO:0000026 1d-s-region OneDimensionalSpatialRegion an edge of a cube-shaped portion of space. A one-dimensional spatial region is a line or aggregate of lines stretching from one point in space to another. (axiom label in BFO2 Reference: [038-001]) (forall (x) (if (OneDimensionalSpatialRegion x) (SpatialRegion x))) // axiom label in BFO2 CLIF: [038-001] one-dimensional spatial region A one-dimensional spatial region is a line or aggregate of lines stretching from one point in space to another. (axiom label in BFO2 Reference: [038-001]) (forall (x) (if (OneDimensionalSpatialRegion x) (SpatialRegion x))) // axiom label in BFO2 CLIF: [038-001] BFO:0000027 object-aggregate ObjectAggregate a collection of cells in a blood biobank. a swarm of bees is an aggregate of members who are linked together through natural bonds a symphony orchestra an organization is an aggregate whose member parts have roles of specific types (for example in a jazz band, a chess club, a football team) defined by fiat: the aggregate of members of an organization defined through physical attachment: the aggregate of atoms in a lump of granite defined through physical containment: the aggregate of molecules of carbon dioxide in a sealed container defined via attributive delimitations such as: the patients in this hospital the aggregate of bearings in a constant velocity axle joint the aggregate of blood cells in your body the nitrogen atoms in the atmosphere the restaurants in Palo Alto your collection of Meissen ceramic plates. An entity a is an object aggregate if and only if there is a mutually exhaustive and pairwise disjoint partition of a into objects BFO 2 Reference: object aggregates may gain and lose parts while remaining numerically identical (one and the same individual) over time. This holds both for aggregates whose membership is determined naturally (the aggregate of cells in your body) and aggregates determined by fiat (a baseball team, a congressional committee). ISBN:978-3-938793-98-5pp124-158#Thomas Bittner and Barry Smith, 'A Theory of Granular Partitions', in K. Munn and B. Smith (eds.), Applied Ontology: An Introduction, Frankfurt/Lancaster: ontos, 2008, 125-158. b is an object aggregate means: b is a material entity consisting exactly of a plurality of objects as member_parts at all times at which b exists. (axiom label in BFO2 Reference: [025-004]) (forall (x) (if (ObjectAggregate x) (and (MaterialEntity x) (forall (t) (if (existsAt x t) (exists (y z) (and (Object y) (Object z) (memberPartOfAt y x t) (memberPartOfAt z x t) (not (= y z)))))) (not (exists (w t_1) (and (memberPartOfAt w x t_1) (not (Object w)))))))) // axiom label in BFO2 CLIF: [025-004] object aggregate An entity a is an object aggregate if and only if there is a mutually exhaustive and pairwise disjoint partition of a into objects An entity a is an object aggregate if and only if there is a mutually exhaustive and pairwise disjoint partition of a into objects ISBN:978-3-938793-98-5pp124-158#Thomas Bittner and Barry Smith, 'A Theory of Granular Partitions', in K. Munn and B. Smith (eds.), Applied Ontology: An Introduction, Frankfurt/Lancaster: ontos, 2008, 125-158. b is an object aggregate means: b is a material entity consisting exactly of a plurality of objects as member_parts at all times at which b exists. (axiom label in BFO2 Reference: [025-004]) (forall (x) (if (ObjectAggregate x) (and (MaterialEntity x) (forall (t) (if (existsAt x t) (exists (y z) (and (Object y) (Object z) (memberPartOfAt y x t) (memberPartOfAt z x t) (not (= y z)))))) (not (exists (w t_1) (and (memberPartOfAt w x t_1) (not (Object w)))))))) // axiom label in BFO2 CLIF: [025-004] BFO:0000028 3d-s-region ThreeDimensionalSpatialRegion a cube-shaped region of space a sphere-shaped region of space, A three-dimensional spatial region is a spatial region that is of three dimensions. (axiom label in BFO2 Reference: [040-001]) (forall (x) (if (ThreeDimensionalSpatialRegion x) (SpatialRegion x))) // axiom label in BFO2 CLIF: [040-001] three-dimensional spatial region A three-dimensional spatial region is a spatial region that is of three dimensions. (axiom label in BFO2 Reference: [040-001]) (forall (x) (if (ThreeDimensionalSpatialRegion x) (SpatialRegion x))) // axiom label in BFO2 CLIF: [040-001] BFO:0000029 site Site Manhattan Canyon) a hole in the interior of a portion of cheese a rabbit hole an air traffic control region defined in the airspace above an airport the Grand Canyon the Piazza San Marco the cockpit of an aircraft the hold of a ship the interior of a kangaroo pouch the interior of the trunk of your car the interior of your bedroom the interior of your office the interior of your refrigerator the lumen of your gut your left nostril (a fiat part – the opening – of your left nasal cavity) b is a site means: b is a three-dimensional immaterial entity that is (partially or wholly) bounded by a material entity or it is a three-dimensional immaterial part thereof. (axiom label in BFO2 Reference: [034-002]) (forall (x) (if (Site x) (ImmaterialEntity x))) // axiom label in BFO2 CLIF: [034-002] site b is a site means: b is a three-dimensional immaterial entity that is (partially or wholly) bounded by a material entity or it is a three-dimensional immaterial part thereof. (axiom label in BFO2 Reference: [034-002]) (forall (x) (if (Site x) (ImmaterialEntity x))) // axiom label in BFO2 CLIF: [034-002] BFO:0000030 object Object atom cell cells and organisms engineered artifacts grain of sand molecule organelle organism planet solid portions of matter star BFO 2 Reference: BFO rests on the presupposition that at multiple micro-, meso- and macroscopic scales reality exhibits certain stable, spatially separated or separable material units, combined or combinable into aggregates of various sorts (for example organisms into what are called ‘populations’). Such units play a central role in almost all domains of natural science from particle physics to cosmology. Many scientific laws govern the units in question, employing general terms (such as ‘molecule’ or ‘planet’) referring to the types and subtypes of units, and also to the types and subtypes of the processes through which such units develop and interact. The division of reality into such natural units is at the heart of biological science, as also is the fact that these units may form higher-level units (as cells form multicellular organisms) and that they may also form aggregates of units, for example as cells form portions of tissue and organs form families, herds, breeds, species, and so on. At the same time, the division of certain portions of reality into engineered units (manufactured artifacts) is the basis of modern industrial technology, which rests on the distributed mass production of engineered parts through division of labor and on their assembly into larger, compound units such as cars and laptops. The division of portions of reality into units is one starting point for the phenomenon of counting. BFO 2 Reference: Each object is such that there are entities of which we can assert unproblematically that they lie in its interior, and other entities of which we can assert unproblematically that they lie in its exterior. This may not be so for entities lying at or near the boundary between the interior and exterior. This means that two objects – for example the two cells depicted in Figure 3 – may be such that there are material entities crossing their boundaries which belong determinately to neither cell. Something similar obtains in certain cases of conjoined twins (see below). BFO 2 Reference: To say that b is causally unified means: b is a material entity which is such that its material parts are tied together in such a way that, in environments typical for entities of the type in question,if c, a continuant part of b that is in the interior of b at t, is larger than a certain threshold size (which will be determined differently from case to case, depending on factors such as porosity of external cover) and is moved in space to be at t at a location on the exterior of the spatial region that had been occupied by b at t, then either b’s other parts will be moved in coordinated fashion or b will be damaged (be affected, for example, by breakage or tearing) in the interval between t and t.causal changes in one part of b can have consequences for other parts of b without the mediation of any entity that lies on the exterior of b. Material entities with no proper material parts would satisfy these conditions trivially. Candidate examples of types of causal unity for material entities of more complex sorts are as follows (this is not intended to be an exhaustive list):CU1: Causal unity via physical coveringHere the parts in the interior of the unified entity are combined together causally through a common membrane or other physical covering\. The latter points outwards toward and may serve a protective function in relation to what lies on the exterior of the entity [13, 47 BFO 2 Reference: an object is a maximal causally unified material entity BFO 2 Reference: ‘objects’ are sometimes referred to as ‘grains’ [74 b is an object means: b is a material entity which manifests causal unity of one or other of the types CUn listed above & is of a type (a material universal) instances of which are maximal relative to this criterion of causal unity. (axiom label in BFO2 Reference: [024-001]) object b is an object means: b is a material entity which manifests causal unity of one or other of the types CUn listed above & is of a type (a material universal) instances of which are maximal relative to this criterion of causal unity. (axiom label in BFO2 Reference: [024-001]) BFO:0000031 gdc GenericallyDependentContinuant The entries in your database are patterns instantiated as quality instances in your hard drive. The database itself is an aggregate of such patterns. When you create the database you create a particular instance of the generically dependent continuant type database. Each entry in the database is an instance of the generically dependent continuant type IAO: information content entity. the pdf file on your laptop, the pdf file that is a copy thereof on my laptop the sequence of this protein molecule; the sequence that is a copy thereof in that protein molecule. A continuant that is dependent on one or other independent continuant bearers. For every instance of A requires some instance of (an independent continuant type) B but which instance of B serves can change from time to time. b is a generically dependent continuant = Def. b is a continuant that g-depends_on one or more other entities. (axiom label in BFO2 Reference: [074-001]) (iff (GenericallyDependentContinuant a) (and (Continuant a) (exists (b t) (genericallyDependsOnAt a b t)))) // axiom label in BFO2 CLIF: [074-001] generically dependent continuant b is a generically dependent continuant = Def. b is a continuant that g-depends_on one or more other entities. (axiom label in BFO2 Reference: [074-001]) (iff (GenericallyDependentContinuant a) (and (Continuant a) (exists (b t) (genericallyDependsOnAt a b t)))) // axiom label in BFO2 CLIF: [074-001] BFO:0000034 function Function the function of a hammer to drive in nails the function of a heart pacemaker to regulate the beating of a heart through electricity the function of amylase in saliva to break down starch into sugar BFO 2 Reference: In the past, we have distinguished two varieties of function, artifactual function and biological function. These are not asserted subtypes of BFO:function however, since the same function – for example: to pump, to transport – can exist both in artifacts and in biological entities. The asserted subtypes of function that would be needed in order to yield a separate monoheirarchy are not artifactual function, biological function, etc., but rather transporting function, pumping function, etc. A function is a disposition that exists in virtue of the bearer’s physical make-up and this physical make-up is something the bearer possesses because it came into being, either through evolution (in the case of natural biological entities) or through intentional design (in the case of artifacts), in order to realize processes of a certain sort. (axiom label in BFO2 Reference: [064-001]) (forall (x) (if (Function x) (Disposition x))) // axiom label in BFO2 CLIF: [064-001] function A function is a disposition that exists in virtue of the bearer’s physical make-up and this physical make-up is something the bearer possesses because it came into being, either through evolution (in the case of natural biological entities) or through intentional design (in the case of artifacts), in order to realize processes of a certain sort. (axiom label in BFO2 Reference: [064-001]) (forall (x) (if (Function x) (Disposition x))) // axiom label in BFO2 CLIF: [064-001] BFO:0000035 p-boundary ProcessBoundary the boundary between the 2nd and 3rd year of your life. p is a process boundary =Def. p is a temporal part of a process & p has no proper temporal parts. (axiom label in BFO2 Reference: [084-001]) Every process boundary occupies_temporal_region a zero-dimensional temporal region. (axiom label in BFO2 Reference: [085-002]) (forall (x) (if (ProcessBoundary x) (exists (y) (and (ZeroDimensionalTemporalRegion y) (occupiesTemporalRegion x y))))) // axiom label in BFO2 CLIF: [085-002] (iff (ProcessBoundary a) (exists (p) (and (Process p) (temporalPartOf a p) (not (exists (b) (properTemporalPartOf b a)))))) // axiom label in BFO2 CLIF: [084-001] process boundary p is a process boundary =Def. p is a temporal part of a process & p has no proper temporal parts. (axiom label in BFO2 Reference: [084-001]) Every process boundary occupies_temporal_region a zero-dimensional temporal region. (axiom label in BFO2 Reference: [085-002]) (forall (x) (if (ProcessBoundary x) (exists (y) (and (ZeroDimensionalTemporalRegion y) (occupiesTemporalRegion x y))))) // axiom label in BFO2 CLIF: [085-002] (iff (ProcessBoundary a) (exists (p) (and (Process p) (temporalPartOf a p) (not (exists (b) (properTemporalPartOf b a)))))) // axiom label in BFO2 CLIF: [084-001] BFO:0000038 1d-t-region OneDimensionalTemporalRegion the temporal region during which a process occurs. BFO 2 Reference: A temporal interval is a special kind of one-dimensional temporal region, namely one that is self-connected (is without gaps or breaks). A one-dimensional temporal region is a temporal region that is extended. (axiom label in BFO2 Reference: [103-001]) (forall (x) (if (OneDimensionalTemporalRegion x) (TemporalRegion x))) // axiom label in BFO2 CLIF: [103-001] one-dimensional temporal region A one-dimensional temporal region is a temporal region that is extended. (axiom label in BFO2 Reference: [103-001]) (forall (x) (if (OneDimensionalTemporalRegion x) (TemporalRegion x))) // axiom label in BFO2 CLIF: [103-001] BFO:0000040 material MaterialEntity Collection of random bacteria, a chair, dorsal surface of the body. a flame a forest fire a human being a hurricane a photon a puff of smoke a sea wave a tornado an aggregate of human beings. an energy wave an epidemic the undetached arm of a human being An independent continuant [snap:IndependentContinuant] that is spatially extended whose identity is independent of that of other entities and can be maintained through time. Note: Material entity [snap:MaterialEntity] subsumes object [snap:Object], fiat object part [snap:FiatObjectPart], and object aggregate [snap:ObjectAggregate], which assume a three level theory of granularity, which is inadequate for some domains, such as biology. An independent continuant that is spatially extended whose identity is independent of that of other entities and can be maintained through time. BFO 2 Reference: Material entities (continuants) can preserve their identity even while gaining and losing material parts. Continuants are contrasted with occurrents, which unfold themselves in successive temporal parts or phases [60 BFO 2 Reference: Object, Fiat Object Part and Object Aggregate are not intended to be exhaustive of Material Entity. Users are invited to propose new subcategories of Material Entity. BFO 2 Reference: ‘Matter’ is intended to encompass both mass and energy (we will address the ontological treatment of portions of energy in a later version of BFO). A portion of matter is anything that includes elementary particles among its proper or improper parts: quarks and leptons, including electrons, as the smallest particles thus far discovered; baryons (including protons and neutrons) at a higher level of granularity; atoms and molecules at still higher levels, forming the cells, organs, organisms and other material entities studied by biologists, the portions of rock studied by geologists, the fossils studied by paleontologists, and so on.Material entities are three-dimensional entities (entities extended in three spatial dimensions), as contrasted with the processes in which they participate, which are four-dimensional entities (entities extended also along the dimension of time).According to the FMA, material entities may have immaterial entities as parts – including the entities identified below as sites; for example the interior (or ‘lumen’) of your small intestine is a part of your body. BFO 2.0 embodies a decision to follow the FMA here. BFO A material entity is an independent continuant that has some portion of matter as proper or improper continuant part. (axiom label in BFO2 Reference: [019-002]) Every entity which has a material entity as continuant part is a material entity. (axiom label in BFO2 Reference: [020-002]) every entity of which a material entity is continuant part is also a material entity. (axiom label in BFO2 Reference: [021-002]) (forall (x) (if (MaterialEntity x) (IndependentContinuant x))) // axiom label in BFO2 CLIF: [019-002] (forall (x) (if (and (Entity x) (exists (y t) (and (MaterialEntity y) (continuantPartOfAt x y t)))) (MaterialEntity x))) // axiom label in BFO2 CLIF: [021-002] (forall (x) (if (and (Entity x) (exists (y t) (and (MaterialEntity y) (continuantPartOfAt y x t)))) (MaterialEntity x))) // axiom label in BFO2 CLIF: [020-002] material entity material entity A material entity is an independent continuant that has some portion of matter as proper or improper continuant part. (axiom label in BFO2 Reference: [019-002]) Every entity which has a material entity as continuant part is a material entity. (axiom label in BFO2 Reference: [020-002]) every entity of which a material entity is continuant part is also a material entity. (axiom label in BFO2 Reference: [021-002]) (forall (x) (if (MaterialEntity x) (IndependentContinuant x))) // axiom label in BFO2 CLIF: [019-002] (forall (x) (if (and (Entity x) (exists (y t) (and (MaterialEntity y) (continuantPartOfAt x y t)))) (MaterialEntity x))) // axiom label in BFO2 CLIF: [021-002] (forall (x) (if (and (Entity x) (exists (y t) (and (MaterialEntity y) (continuantPartOfAt y x t)))) (MaterialEntity x))) // axiom label in BFO2 CLIF: [020-002] BFO:0000140 cf-boundary ContinuantFiatBoundary b is a continuant fiat boundary = Def. b is an immaterial entity that is of zero, one or two dimensions and does not include a spatial region as part. (axiom label in BFO2 Reference: [029-001]) BFO 2 Reference: In BFO 1.1 the assumption was made that the external surface of a material entity such as a cell could be treated as if it were a boundary in the mathematical sense. The new document propounds the view that when we talk about external surfaces of material objects in this way then we are talking about something fiat. To be dealt with in a future version: fiat boundaries at different levels of granularity.More generally, the focus in discussion of boundaries in BFO 2.0 is now on fiat boundaries, which means: boundaries for which there is no assumption that they coincide with physical discontinuities. The ontology of boundaries becomes more closely allied with the ontology of regions. BFO 2 Reference: a continuant fiat boundary is a boundary of some material entity (for example: the plane separating the Northern and Southern hemispheres; the North Pole), or it is a boundary of some immaterial entity (for example of some portion of airspace). Three basic kinds of continuant fiat boundary can be distinguished (together with various combination kinds [29 Continuant fiat boundary doesn't have a closure axiom because the subclasses don't necessarily exhaust all possibilites. An example would be the mereological sum of two-dimensional continuant fiat boundary and a one dimensional continuant fiat boundary that doesn't overlap it. The situation is analogous to temporal and spatial regions. Every continuant fiat boundary is located at some spatial region at every time at which it exists (iff (ContinuantFiatBoundary a) (and (ImmaterialEntity a) (exists (b) (and (or (ZeroDimensionalSpatialRegion b) (OneDimensionalSpatialRegion b) (TwoDimensionalSpatialRegion b)) (forall (t) (locatedInAt a b t)))) (not (exists (c t) (and (SpatialRegion c) (continuantPartOfAt c a t)))))) // axiom label in BFO2 CLIF: [029-001] continuant fiat boundary b is a continuant fiat boundary = Def. b is an immaterial entity that is of zero, one or two dimensions and does not include a spatial region as part. (axiom label in BFO2 Reference: [029-001]) Continuant fiat boundary doesn't have a closure axiom because the subclasses don't necessarily exhaust all possibilites. An example would be the mereological sum of two-dimensional continuant fiat boundary and a one dimensional continuant fiat boundary that doesn't overlap it. The situation is analogous to temporal and spatial regions. (iff (ContinuantFiatBoundary a) (and (ImmaterialEntity a) (exists (b) (and (or (ZeroDimensionalSpatialRegion b) (OneDimensionalSpatialRegion b) (TwoDimensionalSpatialRegion b)) (forall (t) (locatedInAt a b t)))) (not (exists (c t) (and (SpatialRegion c) (continuantPartOfAt c a t)))))) // axiom label in BFO2 CLIF: [029-001] BFO:0000141 immaterial ImmaterialEntity BFO 2 Reference: Immaterial entities are divided into two subgroups:boundaries and sites, which bound, or are demarcated in relation, to material entities, and which can thus change location, shape and size and as their material hosts move or change shape or size (for example: your nasal passage; the hold of a ship; the boundary of Wales (which moves with the rotation of the Earth) [38, 7, 10 immaterial entity BFO:0000142 1d-cf-boundary OneDimensionalContinuantFiatBoundary The Equator all geopolitical boundaries all lines of latitude and longitude the line separating the outer surface of the mucosa of the lower lip from the outer surface of the skin of the chin. the median sulcus of your tongue a one-dimensional continuant fiat boundary is a continuous fiat line whose location is defined in relation to some material entity. (axiom label in BFO2 Reference: [032-001]) (iff (OneDimensionalContinuantFiatBoundary a) (and (ContinuantFiatBoundary a) (exists (b) (and (OneDimensionalSpatialRegion b) (forall (t) (locatedInAt a b t)))))) // axiom label in BFO2 CLIF: [032-001] one-dimensional continuant fiat boundary a one-dimensional continuant fiat boundary is a continuous fiat line whose location is defined in relation to some material entity. (axiom label in BFO2 Reference: [032-001]) (iff (OneDimensionalContinuantFiatBoundary a) (and (ContinuantFiatBoundary a) (exists (b) (and (OneDimensionalSpatialRegion b) (forall (t) (locatedInAt a b t)))))) // axiom label in BFO2 CLIF: [032-001] BFO:0000144 process-profile ProcessProfile On a somewhat higher level of complexity are what we shall call rate process profiles, which are the targets of selective abstraction focused not on determinate quality magnitudes plotted over time, but rather on certain ratios between these magnitudes and elapsed times. A speed process profile, for example, is represented by a graph plotting against time the ratio of distance covered per unit of time. Since rates may change, and since such changes, too, may have rates of change, we have to deal here with a hierarchy of process profile universals at successive levels One important sub-family of rate process profiles is illustrated by the beat or frequency profiles of cyclical processes, illustrated by the 60 beats per minute beating process of John’s heart, or the 120 beats per minute drumming process involved in one of John’s performances in a rock band, and so on. Each such process includes what we shall call a beat process profile instance as part, a subtype of rate process profile in which the salient ratio is not distance covered but rather number of beat cycles per unit of time. Each beat process profile instance instantiates the determinable universal beat process profile. But it also instantiates multiple more specialized universals at lower levels of generality, selected from rate process profilebeat process profileregular beat process profile3 bpm beat process profile4 bpm beat process profileirregular beat process profileincreasing beat process profileand so on.In the case of a regular beat process profile, a rate can be assigned in the simplest possible fashion by dividing the number of cycles by the length of the temporal region occupied by the beating process profile as a whole. Irregular process profiles of this sort, for example as identified in the clinic, or in the readings on an aircraft instrument panel, are often of diagnostic significance. The simplest type of process profiles are what we shall call ‘quality process profiles’, which are the process profiles which serve as the foci of the sort of selective abstraction that is involved when measurements are made of changes in single qualities, as illustrated, for example, by process profiles of mass, temperature, aortic pressure, and so on. b is a process_profile =Def. there is some process c such that b process_profile_of c (axiom label in BFO2 Reference: [093-002]) b process_profile_of c holds when b proper_occurrent_part_of c& there is some proper_occurrent_part d of c which has no parts in common with b & is mutually dependent on b& is such that b, c and d occupy the same temporal region (axiom label in BFO2 Reference: [094-005]) (forall (x y) (if (processProfileOf x y) (and (properContinuantPartOf x y) (exists (z t) (and (properOccurrentPartOf z y) (TemporalRegion t) (occupiesSpatioTemporalRegion x t) (occupiesSpatioTemporalRegion y t) (occupiesSpatioTemporalRegion z t) (not (exists (w) (and (occurrentPartOf w x) (occurrentPartOf w z))))))))) // axiom label in BFO2 CLIF: [094-005] (iff (ProcessProfile a) (exists (b) (and (Process b) (processProfileOf a b)))) // axiom label in BFO2 CLIF: [093-002] process profile b is a process_profile =Def. there is some process c such that b process_profile_of c (axiom label in BFO2 Reference: [093-002]) b process_profile_of c holds when b proper_occurrent_part_of c& there is some proper_occurrent_part d of c which has no parts in common with b & is mutually dependent on b& is such that b, c and d occupy the same temporal region (axiom label in BFO2 Reference: [094-005]) (forall (x y) (if (processProfileOf x y) (and (properContinuantPartOf x y) (exists (z t) (and (properOccurrentPartOf z y) (TemporalRegion t) (occupiesSpatioTemporalRegion x t) (occupiesSpatioTemporalRegion y t) (occupiesSpatioTemporalRegion z t) (not (exists (w) (and (occurrentPartOf w x) (occurrentPartOf w z))))))))) // axiom label in BFO2 CLIF: [094-005] (iff (ProcessProfile a) (exists (b) (and (Process b) (processProfileOf a b)))) // axiom label in BFO2 CLIF: [093-002] BFO:0000145 r-quality RelationalQuality John’s role of husband to Mary is dependent on Mary’s role of wife to John, and both are dependent on the object aggregate comprising John and Mary as member parts joined together through the relational quality of being married. a marriage bond, an instance of requited love, an obligation between one person and another. b is a relational quality = Def. for some independent continuants c, d and for some time t: b quality_of c at t & b quality_of d at t. (axiom label in BFO2 Reference: [057-001]) (iff (RelationalQuality a) (exists (b c t) (and (IndependentContinuant b) (IndependentContinuant c) (qualityOfAt a b t) (qualityOfAt a c t)))) // axiom label in BFO2 CLIF: [057-001] relational quality b is a relational quality = Def. for some independent continuants c, d and for some time t: b quality_of c at t & b quality_of d at t. (axiom label in BFO2 Reference: [057-001]) (iff (RelationalQuality a) (exists (b c t) (and (IndependentContinuant b) (IndependentContinuant c) (qualityOfAt a b t) (qualityOfAt a c t)))) // axiom label in BFO2 CLIF: [057-001] BFO:0000146 2d-cf-boundary TwoDimensionalContinuantFiatBoundary a two-dimensional continuant fiat boundary (surface) is a self-connected fiat surface whose location is defined in relation to some material entity. (axiom label in BFO2 Reference: [033-001]) (iff (TwoDimensionalContinuantFiatBoundary a) (and (ContinuantFiatBoundary a) (exists (b) (and (TwoDimensionalSpatialRegion b) (forall (t) (locatedInAt a b t)))))) // axiom label in BFO2 CLIF: [033-001] two-dimensional continuant fiat boundary a two-dimensional continuant fiat boundary (surface) is a self-connected fiat surface whose location is defined in relation to some material entity. (axiom label in BFO2 Reference: [033-001]) (iff (TwoDimensionalContinuantFiatBoundary a) (and (ContinuantFiatBoundary a) (exists (b) (and (TwoDimensionalSpatialRegion b) (forall (t) (locatedInAt a b t)))))) // axiom label in BFO2 CLIF: [033-001] BFO:0000147 0d-cf-boundary ZeroDimensionalContinuantFiatBoundary the geographic North Pole the point of origin of some spatial coordinate system. the quadripoint where the boundaries of Colorado, Utah, New Mexico, and Arizona meet zero dimension continuant fiat boundaries are not spatial points. Considering the example 'the quadripoint where the boundaries of Colorado, Utah, New Mexico, and Arizona meet' : There are many frames in which that point is zooming through many points in space. Whereas, no matter what the frame, the quadripoint is always in the same relation to the boundaries of Colorado, Utah, New Mexico, and Arizona. a zero-dimensional continuant fiat boundary is a fiat point whose location is defined in relation to some material entity. (axiom label in BFO2 Reference: [031-001]) (iff (ZeroDimensionalContinuantFiatBoundary a) (and (ContinuantFiatBoundary a) (exists (b) (and (ZeroDimensionalSpatialRegion b) (forall (t) (locatedInAt a b t)))))) // axiom label in BFO2 CLIF: [031-001] zero-dimensional continuant fiat boundary zero dimension continuant fiat boundaries are not spatial points. Considering the example 'the quadripoint where the boundaries of Colorado, Utah, New Mexico, and Arizona meet' : There are many frames in which that point is zooming through many points in space. Whereas, no matter what the frame, the quadripoint is always in the same relation to the boundaries of Colorado, Utah, New Mexico, and Arizona. requested by Melanie Courtot a zero-dimensional continuant fiat boundary is a fiat point whose location is defined in relation to some material entity. (axiom label in BFO2 Reference: [031-001]) (iff (ZeroDimensionalContinuantFiatBoundary a) (and (ContinuantFiatBoundary a) (exists (b) (and (ZeroDimensionalSpatialRegion b) (forall (t) (locatedInAt a b t)))))) // axiom label in BFO2 CLIF: [031-001] BFO:0000148 0d-t-region ZeroDimensionalTemporalRegion a temporal region that is occupied by a process boundary right now the moment at which a child is born the moment at which a finger is detached in an industrial accident the moment of death. temporal instant. A zero-dimensional temporal region is a temporal region that is without extent. (axiom label in BFO2 Reference: [102-001]) (forall (x) (if (ZeroDimensionalTemporalRegion x) (TemporalRegion x))) // axiom label in BFO2 CLIF: [102-001] zero-dimensional temporal region A zero-dimensional temporal region is a temporal region that is without extent. (axiom label in BFO2 Reference: [102-001]) (forall (x) (if (ZeroDimensionalTemporalRegion x) (TemporalRegion x))) // axiom label in BFO2 CLIF: [102-001] BFO:0000182 history History A history is a process that is the sum of the totality of processes taking place in the spatiotemporal region occupied by a material entity or site, including processes on the surface of the entity or within the cavities to which it serves as host. (axiom label in BFO2 Reference: [138-001]) history A history is a process that is the sum of the totality of processes taking place in the spatiotemporal region occupied by a material entity or site, including processes on the surface of the entity or within the cavities to which it serves as host. (axiom label in BFO2 Reference: [138-001]) IAO:0000001 conditional specification A directive information entity that specifies what should happen if the trigger condition is fulfilled. PlanAndPlannedProcess Branch OBI branch derived OBI_0000349 conditional specification IAO:0000003 measurement unit label Examples of measurement unit labels are liters, inches, weight per volume. A measurement unit label is as a label that is part of a scalar measurement datum and denotes a unit of measure. 2009-03-16: provenance: a term measurement unit was proposed for OBI (OBI_0000176) , edited by Chris Stoeckert and Cristian Cocos, and subsequently moved to IAO where the objective for which the original term was defined was satisfied with the definition of this, different, term. 2009-03-16: review of this term done during during the OBI workshop winter 2009 and the current definition was considered acceptable for use in OBI. If there is a need to modify this definition please notify OBI. PERSON: Alan Ruttenberg PERSON: Melanie Courtot measurement unit label IAO:0000005 objective specification In the protocol of a ChIP assay the objective specification says to identify protein and DNA interaction. A directive information entity that describes an intended process endpoint. When part of a plan specification the concretization is realized in a planned process in which the bearer tries to effect the world so that the process endpoint is achieved. 2009-03-16: original definition when imported from OBI read: "objective is an non realizable information entity which can serve as that proper part of a plan towards which the realization of the plan is directed." 2014-03-31: In the example of usage ("In the protocol of a ChIP assay the objective specification says to identify protein and DNA interaction") there is a protocol which is the ChIP assay protocol. In addition to being concretized on paper, the protocol can be concretized as a realizable entity, such as a plan that inheres in a person. The objective specification is the part that says that some protein and DNA interactions are identified. This is a specification of a process endpoint: the boundary in the process before which they are not identified and after which they are. During the realization of the plan, the goal is to get to the point of having the interactions, and participants in the realization of the plan try to do that. Answers the question, why did you do this experiment? PERSON: Alan Ruttenberg PERSON: Barry Smith PERSON: Bjoern Peters PERSON: Jennifer Fostel goal specification OBI Plan and Planned Process/Roles Branch OBI_0000217 objective specification IAO:0000006 narrative object Examples of narrative objects are reports, journal articles, and patents submission. A narrative object is an information content entity that is a set of propositions. 2009-08-10 Alan Ruttenberg: Larry Hunter suggests that this be obsoleted and replaced by 'textual entity' and 'figure'. Alan restored as there are OBI dependencies and this merits further discussion agree - DENRIE. Issue(alan) do we only mean text? What about a story told by mime. Does music count? (no) what about an oral report. Regarding definition, saying it is a set of propositions means we loose the idea that wording matters. Maybe adjust saying a narrative object has some relationshop to a set of propositions person:Chris Stoeckert OBI_0000013 group:OBI narrative object IAO:0000007 Pour the contents of flask 1 into flask 2 A directive information entity that describes an action the bearer will take. Alan Ruttenberg OBI Plan and Planned Process branch action specification IAO:0000008 obsolete_artifact true IAO:0000009 datum label A label is a symbol that is part of some other datum and is used to either partially define the denotation of that datum or to provide a means for identifying the datum as a member of the set of data with the same label http://www.golovchenko.org/cgi-bin/wnsearch?q=label#4n GROUP: IAO 9/22/11 BP: changed the rdfs:label for this class from 'label' to 'datum label' to convey that this class is not intended to cover all kinds of labels (stickers, radiolabels, etc.), and not even all kind of textual labels, but rather the kind of labels occuring in a datum. datum label IAO:0000010 software Software is a plan specification composed of a series of instructions that can be interpreted by or directly executed by a processing unit. see sourceforge tracker discussion at http://sourceforge.net/tracker/index.php?func=detail&aid=1958818&group_id=177891&atid=886178 PERSON: Alan Ruttenberg PERSON: Bjoern Peters PERSON: Chris Stoeckert PERSON: Melanie Courtot GROUP: OBI software IAO:0000012 obsolete_digital entity A digital entity is an information entity which is a collection of bits that can be interpreted by a computer. Two digital entities are the same if they are bitwise identical. 3/22/2009 Alan Ruttenberg, obsoleted per http://groups.google.com/group/information-ontology/browse_thread/thread/789ad4b7708d5cf4 Superclass was 'digitial quality' person:Chris Stoeckert OBI_0000261 group:OBI obsolete2_digital entity true IAO:0000013 journal article Examples are articles published in the journals, Nature and Science. The content can often be cited by reference to a paper based encoding, e.g. Authors, Title of article, Journal name, date or year of publication, volume and page number. A report that is published in a journal. PERSON: Alan Ruttenberg PERSON: Chris Stoeckert OBI_0000159 group:OBI journal article IAO:0000015 information carrier In the case of a printed paperback novel the physicality of the ink and of the paper form part of the information bearer. The qualities of appearing black and having a certain pattern for the ink and appearing white for the paper form part of the information carrier in this case. A quality of an information bearer that imparts the information content 12/15/09: There is a concern that some ways that carry information may be processes rather than qualities, such as in a 'delayed wave carrier'. 2014-03-10: We are not certain that all information carriers are qualities. There was a discussion of dropping it. PERSON: Alan Ruttenberg Smith, Ceusters, Ruttenberg, 2000 years of philosophy information carrier IAO:0000017 model number A model number is an information content entity specifically borne by catalogs, design specifications, advertising materials, inventory systems and similar that is about manufactured objects of the same class. The model number is an alternative term for the class. The manufactered objects may or may not also bear the model number. Model numbers can be encoded in a variety of other information objects, such as bar codes, numerals, or patterns of dots. manufactered items may have more than one model number, sometimes by rebranding, or because companies are sold and the products issued new model numbers Person: Alan Ruttenberg model number IAO:0000018 obsolete_material_entity true IAO:0000019 binary digital entity MS Word document, ZIP file, DICOM file, JPEG file A binary digital entity is a digital entity that is encoded in a way that is not easily human readable and that contains other than text characters. 3/22/2009 Alan Ruttenberg, obsoleted per http://groups.google.com/group/information-ontology/browse_thread/thread/789ad4b7708d5cf4 Superclass was 'digital entity' digital_entity person:Chris Stoeckert OBI_0000244 group:OBI obsolete2_binary digital entity true IAO:0000024 The length of a ruler. a unit of measure is the quality of some material entity compared to which another quality is some multiple of. Alan Ruttenberg Smith, Ceusters, Ruttenberg, 2000 years of philosophy obsolete_unit of measure true IAO:0000025 programming language R, Perl, Java A language in which source code is written that is intended to be executed/run by a software interpreter. Programming languages are ways to write instructions that specify what to do, and sometimes, how to do it. A language in which source code is written, intended to executed/run by a software interpreter. Programming languages are ways to write instructions that specify what to do, and sometimes, how to do it. person:Alan Ruttenberg person:Chris Stoeckert IAO OBI_0000058 group:OBI programming language programming language IAO:0000027 data item Data items include counts of things, analyte concentrations, and statistical summaries. An information content entity that is intended to be a truthful statement about something (modulo, e.g., measurement precision or other systematic errors) and is constructed/acquired by a method which reliably tends to produce (approximately) truthful statements. a data item is an information content entity that is intended to be a truthful statement about something (modulo, e.g., measurement precision or other systematic errors) and is constructed/acquired by a method which reliably tends to produce (approximately) truthful statements. 2/2/2009 Alan and Bjoern discussing FACS run output data. This is a data item because it is about the cell population. Each element records an event and is typically further composed a set of measurment data items that record the fluorescent intensity stimulated by one of the lasers. 2009-03-16: data item deliberatly ambiguous: we merged data set and datum to be one entity, not knowing how to define singular versus plural. So data item is more general than datum. 2009-03-16: removed datum as alternative term as datum specifically refers to singular form, and is thus not an exact synonym. 2014-03-31: See discussion at http://odontomachus.wordpress.com/2014/03/30/aboutness-objects-propositions/ JAR: datum -- well, this will be very tricky to define, but maybe some information-like stuff that might be put into a computer and that is meant, by someone, to denote and/or to be interpreted by some process... I would include lists, tables, sentences... I think I might defer to Barry, or to Brian Cantwell Smith JAR: A data item is an approximately justified approximately true approximate belief PERSON: Alan Ruttenberg PERSON: Chris Stoeckert PERSON: Jonathan Rees data data item http://www.ontobee.org/browser/rdf.php?o=IAO&iri=http://purl.obolibrary.org/obo/IAO_0000027 IAO:0000028 symbol a serial number such as "12324X" a stop sign a written proper name such as "OBI" An information content entity that is a mark(s) or character(s) used as a conventional representation of another entity. 20091104, MC: this needs work and will most probably change 2014-03-31: We would like to have a deeper analysis of 'mark' and 'sign' in the future (see https://github.com/information-artifact-ontology/IAO/issues/154). PERSON: James A. Overton PERSON: Jonathan Rees based on Oxford English Dictionary symbol IAO:0000029 numeral A symbol that denotes a number. PERSON: Jonathan Rees numeral IAO:0000030 information content entity Examples of information content entites include journal articles, data, graphical layouts, and graphs. Examples of information content entites include journal articles, data, graphical layouts, and graphs. A generically dependent continuant that is about some thing. An information content entity is an entity that is generically dependent on some artifact and stands in relation of aboutness to some entity. 2014-03-10: The use of "thing" is intended to be general enough to include universals and configurations (see https://groups.google.com/d/msg/information-ontology/GBxvYZCk1oc/-L6B5fSBBTQJ). information_content_entity 'is_encoded_in' some digital_entity in obi before split (040907). information_content_entity 'is_encoded_in' some physical_document in obi before split (040907). Previous. An information content entity is a non-realizable information entity that 'is encoded in' some digital or physical entity. PERSON: Chris Stoeckert IAO OBI_0000142 information content entity information content entity IAO:0000031 integer numeral A numeral that denotes an integer PERSON: Jonathan Rees integer numeral 1 1 IAO:0000032 10 feet. 3 ml. A scalar measurement datum is a measurement datum that is composed of two parts, numerals and a unit label. 2009-03-16: we decided to keep datum singular in scalar measurement datum, as in this case we explicitly refer to the singular form Would write this as: has_part some 'measurement unit label' and has_part some numeral and has_part exactly 2, except for the fact that this won't let us take advantage of OWL reasoning over the numbers. Instead use has measurment value property to represent the same. Use has measurement unit label (subproperty of has_part) so we can easily say that there is only one of them. PERSON: Alan Ruttenberg PERSON: Melanie Courtot scalar measurement datum IAO:0000033 An information content entity whose concretizations indicate to their bearer how to realize them in a process. 2009-03-16: provenance: a term realizable information entity was proposed for OBI (OBI_0000337) , edited by the PlanAndPlannedProcess branch. Original definition was "is the specification of a process that can be concretized and realized by an actor" with alternative term "instruction".It has been subsequently moved to IAO where the objective for which the original term was defined was satisfied with the definitionof this, different, term. 2013-05-30 Alan Ruttenberg: What differentiates a directive information entity from an information concretization is that it can have concretizations that are either qualities or realizable entities. The concretizations that are realizable entities are created when an individual chooses to take up the direction, i.e. has the intention to (try to) realize it. 8/6/2009 Alan Ruttenberg: Changed label from "information entity about a realizable" after discussions at ICBO Werner pushed back on calling it realizable information entity as it isn't realizable. However this name isn't right either. An example would be a recipe. The realizable entity would be a plan, but the information entity isn't about the plan, it, once concretized, *is* the plan. -Alan PERSON: Alan Ruttenberg PERSON: Bjoern Peters directive information entity IAO:0000034 time trigger PlanAndPlannedProcess Branch time trigger IAO:0000035 obsolete_study interpretation A study interpretation is a textual entity about the implications of a study result. Examples include discussion of whether a hypothesis is false, whether the study failed to address the hypothesis, and whether the study results have led to new hypotheses 2009-03-16: definition was "A conclusion is a narrative object which can be published in a paper summerizing and interpreting a protocol application." 2009-03-16: work has been done on this term during during the OBI workshop winter 2009 and the current definition was considered acceptable for use in OBI. If there is a need to modify this definition please notify OBI. The obsoleting of narrative object required a modest change in the definition of this term. Circularity with "interpretation... interprets" has been removed, using "about the implications" instead. Lawrence Hunter PERSON: Alan Ruttenberg PERSON: Jennifer Fostel PERSON: Melanie Courtot conclusion OBI_0000005 obsolete_study interpretation true IAO:0000037 dot plot Dot plot of SSC-H and FSC-H. A dot plot is a report graph which is a graphical representation of data where each data point is represented by a single dot placed on coordinates corresponding to data point values in particular dimensions. person:Allyson Lister person:Chris Stoeckert OBI_0000123 group:OBI dot plot IAO:0000038 graph A diagram that presents one or more tuples of information by mapping those tuples in to a two dimensional space in a non arbitrary way. PERSON: Lawrence Hunter person:Alan Ruttenberg person:Allyson Lister OBI_0000240 group:OBI graph IAO:0000047 text based digital entity XML file, C++ source code file A text based digital entity is a digital entity that is encoded so that it only contains text characters. 3/22/2009 Alan Ruttenberg, obsoleted per http://groups.google.com/group/information-ontology/browse_thread/thread/789ad4b7708d5cf4 superclass was 'digital document' digital_entity person:Chris Stoeckert OBI_0000132 group:OBI obsolete2_text based digital entity true IAO:0000055 rule example to be added A rule is an executable which guides, defines, restricts actions. MSI PRS OBI_0500021 PRS rule IAO:0000057 contour plot Contour plot of SSC-H, FSC-H, and FL1-H. generically_dependent_continuants person:Allyson Lister person:Chris Stoeckert OBI_0000246 group:Flow Cytometry community contour plot IAO:0000059 report figure A report figure is a report display element that has some aspect of illustration, but may be a composite of figures, images, and other elements I prepended the 'report ' to make it clear that we mean parts of reports here. We may want a more generic version of 'figure', in which case this would become a defined class - figure and part_of some report Replaced by defined version of figure person:Alan Ruttenberg person:Allyson Lister OBI_0000027 group:OBI obsolete2_report figure true IAO:0000064 algorithm PMID: 18378114.Genomics. 2008 Mar 28. LINKGEN: A new algorithm to process data in genetic linkage studies. A plan specification which describes inputs, output of mathematical functions as well as workflow of execution for achieving an predefined objective. Algorithms are realized usually by means of implementation as computer programs for execution by automata. A plan specification which describes the inputs and output of mathematical functions as well as workflow of execution for achieving an predefined objective. Algorithms are realized usually by means of implementation as computer programs for execution by automata. An algorithm is a set of instructions for performing a paticular calculation. Philippe Rocca-Serra PlanAndPlannedProcess Branch IAO OBI_0000270 adapted from discussion on OBI list (Matthew Pocock, Christian Cocos, Alan Ruttenberg) algorithm algorithm An algorithm is a set of instructions for performing a paticular calculation. IAO:0000065 software interpreter R program, Perl interpreter, Java virtual machine A software interpreter is a software application that executes some specified input software. Do we care? Jennifer: Yes, there was a particular version of R that had a bug and it was fixed later. That would imply that we mean specific version of an interpreter. So an instance of this would be a particular version of the interpreter person:Alan Ruttenberg person:Chris Stoeckert OBI_0000199 group:OBI software interpreter IAO:0000078 curation status specification The curation status of the term. The allowed values come from an enumerated list of predefined terms. See the specification of these instances for more detailed definitions of each enumerated value. Better to represent curation as a process with parts and then relate labels to that process (in IAO meeting) PERSON:Bill Bug GROUP:OBI:<http://purl.obolibrary.org/obo/obi> OBI_0000266 curation status specification IAO:0000079 density plot Density plot of SSC-H and FSC-H. A density plot is a report graph which is a graphical representation of data where the tint of a particular pixel corresponds to some kind of function corresponding the the amount of data points relativelly with their distance from the the pixel. person:Allyson Lister person:Chris Stoeckert OBI_0000179 group:Flow Cytometry community density plot IAO:0000088 report Examples of reports are gene lists and investigation reports. These are not published (journal) articles but may be included in a journal article. A document assembled by an author for the purpose of providing information for the audience. A report is the output of a documenting process and has the objective to be consumed by a specific audience. Topic of the report is on something that has completed. A report is not a single figure. Examples of reports are journal article, patent application, grant progress report, case report (not patient record). 2009-03-16: comment from Darren Natale: I am slightly uneasy with the sentence "Topic of the report is on something that has completed." Should it be restricted to those things that are completed? For example, a progress report is (usually) about something that definitely has *not* been completed, or may include (only) projections. I think the definition would not suffer if the whole sentence is deleted. 2009-03-16: this was report of results with definition: A report is a narrative object that is a formal statement of the results of an investigation, or of any matter on which definite information is required, made by some person or body instructed or required to do so. 2009-03-16: work has been done on this term during during the OBI workshop winter 2009 and the current definition was considered acceptable for use in OBI. If there is a need to modify this definition please notify OBI. 2009-08-10 Alan Ruttenberg: Larry Hunter suggests that this be obsoleted and replaced by 'document'. Alan restored as there are OBI dependencies and this merits further discussion disagreement about where reports go. alan: only some gene lists are reports. Is a report all the content of some document? The example of usage suggests that a report may be part of some article. Term needs clarification PERSON: Alan Ruttenberg PERSON: Chris Stoeckert PERSON: Melanie Courtot GROUP: OBI OBI_0000099 report IAO:0000091 report element A report element is a narrative object in which information is presented and consumed by a human being, and is part of a report. Examples of report elements are figure (dot plot), table, text portion (may include a movie or audio clip on a web page). 2009-03-16: needs some more work (clarify relations). 2009-03-16: was report display element with definition: A report display element is a narrative object that is part of a report. Report display elements are set off from the textual parts of a report and are typically given a label(e.g. Figure 2) which is used to refer to the element from the text. Typically the 2d layout is part of the identity of such elements. 2009-03-16: work has been done on this term during during the OBI workshop winter 2009 and the current definition was considered acceptable for use in OBI. If there is a need to modify this definition please notify OBI. 2009-08-10 Alan Ruttenberg: Larry Hunter suggests that this be obsoleted and replaced by 'textual entity' and 'figure'. Alan restored as there are OBI dependencies and this merits further discussion Replaced by textual entity and figure There will be some issue here about whether these are defined classes. As intended these are meant to denote the parts of the report that are not textual but are typically boxed and set within the text, labelled with some identifier, and referred to in the text PERSON: Alan Ruttenberg PERSON: Allyson Lister PERSON: Melanie Courtot GROUP:OBI OBI_0000001 obsolete_report element true IAO:0000093 binary executable Binary executable is a digital entity consisting of the binary representation of machine instructions of a specific processor or they may be binary pseudocode for a virtual machine. A non-source executable file is also called an object program. It is assumed that the binary executable file contains properly-formatted computer instructions. (derived from Wikipedia, Nov 1, 2007) 3/22/2009 Alan Ruttenberg, obsoleted per http://groups.google.com/group/information-ontology/browse_thread/thread/789ad4b7708d5cf4 superclass was 'digital entity' person:Jennifer Fostel OBI_0000222 group:OBI obsolete2_binary executable true IAO:0000096 source code module The written source code that implements part of an algorithm. Test - if you know that it was written in a specific language, then it can be source code module. We mean here, roughly, the wording of a document such as a perl script. A source code module is a directive information entity that specifies, using a programming language, some algorithm. person:Alan Ruttenberg person:Chris Stoeckert OBI_0000039 group:OBI source code module IAO:0000097 report table A report table is a report display element consisting of a matrix of cells layed out in a grid, some set of which are filled with some information content 2009-08-10 Alan Ruttenberg: Larry Hunter suggests that this be obsoleted and replaced by 'textual entity table'. Alan restored as there are OBI dependencies and this merits further discussion person:Alan Ruttenberg person:Allyson Lister OBI_0000265 group:OBI obsolete_report table true IAO:0000098 data format specification A data format specification is the information content borne by the document published defining the specification. Example: The ISO document specifying what encompasses an XML document; The instructions in a XSD file The syntax by which data is specified which renders it valid for a given format. 2009-03-16: provenance: term imported from OBI_0000187, which had original definition "A data format specification is a plan which organizes information. Example: The ISO document specifying what encompasses an XML document; The instructions in a XSD file" PERSON: Alan Ruttenberg PlanAndPlannedProcess Branch OBI branch derived OBI_0000187 data format specification The syntax by which data is specified which renders it valid for a given format. IAO:0000100 data set Intensity values in a CEL file or from multiple CEL files comprise a data set (as opposed to the CEL files themselves). A data item that is an aggregate of other data items of the same type that have something in common. Averages and distributions can be determined for data sets. 2009/10/23 Alan Ruttenberg. The intention is that this term represent collections of like data. So this isn't for, e.g. the whole contents of a cel file, which includes parameters, metadata etc. This is more like java arrays of a certain rather specific type 2014-05-05: Data sets are aggregates and thus must include two or more data items. We have chosen not to add logical axioms to make this restriction. person:Allyson Lister person:Chris Stoeckert OBI_0000042 group:OBI data set IAO:0000101 image An image is an affine projection to a two dimensional surface, of measurements of some quality of an entity or entities repeated at regular intervals across a spatial range, where the measurements are represented as color and luminosity on the projected on surface. person:Alan Ruttenberg person:Allyson person:Chris Stoeckert OBI_0000030 group:OBI image IAO:0000102 data about an ontology part Data about an ontology part is a data item about a part of an ontology, for example a term Person:Alan Ruttenberg data about an ontology part IAO:0000104 plan specification PMID: 18323827.Nat Med. 2008 Mar;14(3):226.New plan proposed to help resolve conflicting medical advice. A directive information entity with action specifications and objective specifications as parts that, when concretized, is realized in a process in which the bearer tries to achieve the objectives by taking the actions specified. A directive information entity with action specifications and objective specifications as parts, and that may be concretized as a realizable entity that, if realized, is realized in a process in which the bearer tries to achieve the objectives by taking the actions specified. 2009-03-16: provenance: a term a plan was proposed for OBI (OBI_0000344) , edited by the PlanAndPlannedProcess branch. Original definition was " a plan is a specification of a process that is realized by an actor to achieve the objective specified as part of the plan". It has been subsequently moved to IAO where the objective for which the original term was defined was satisfied with the definitionof this, different, term. 2014-03-31: A plan specification can have other parts, such as conditional specifications. 2022-01-16 Updated definition to that proposed by Clint Dowloand, IAO Issue 231. Alternative previous definition: a plan is a set of instructions that specify how an objective should be achieved Alan Ruttenberg Clint Dowland OBI Plan and Planned Process branch OBI_0000344 2/3/2009 Comment from OBI review. Action specification not well enough specified. Conditional specification not well enough specified. Question whether all plan specifications have objective specifications. Request that IAO either clarify these or change definitions not to use them plan specification https://github.com/information-artifact-ontology/IAO/issues/231#issuecomment-1010455131 IAO:0000105 digital document A digital document is a digital entity consisting of an electronic file which can be rendered into human-readable form by one or more computational applications. The digital document does not refer to the information content of the document but to an instance of the file. 3/22/2009 Alan Ruttenberg, obsoleted per http://groups.google.com/group/information-ontology/browse_thread/thread/789ad4b7708d5cf4 superclass was 'digial entity' person:Jennifer Fostel OBI_0000195 group:OBI obsolete2_digital document true IAO:0000109 measurement datum Examples of measurement data are the recoding of the weight of a mouse as {40,mass,"grams"}, the recording of an observation of the behavior of the mouse {,process,"agitated"}, the recording of the expression level of a gene as measured through the process of microarray experiment {3.4,luminosity,}. A measurement datum is an information content entity that is a recording of the output of a measurement such as produced by a device. 2/2/2009 is_specified_output of some assay? person:Chris Stoeckert OBI_0000305 group:OBI measurement datum IAO:0000128 _identifier is a container under information content entity for collecting types of terms to indicate a specific instance or clas of what was used or participated in an investigation. Identifiers are borne by a product or its packaging, and can be encoded in a variety of other information objects, such as bar codes, numerals, or patterns of dots. Note: everybody agreed that identifier is probably a too general term. We however felt that it would be appropriate to group "identifiying" terms under some kind of umbrella. We therefore propose to use _identifier for that purpose. As per OBI conventions, the _ prefixing identifier indicates that this is a helper class and shouldn't be considered as final. obsolete_identifier true IAO:0000129 version number A version number is an information content entity which is a sequence of characters borne by part of each of a class of manufactured products or its packaging and indicates its order within a set of other products having the same name. Note: we feel that at the moment we are happy with a general version number, and that we will subclass as needed in the future. For example, see 7. genome sequence version GROUP: IAO version name version number IAO:0000131 serial number A serial number is an information content entity which is a unique sequence of characters borne by part of manufactured product or its packaging that is assigned to each individual in some class of products, and so can serve as a way to identify an individual product within the class. Serial numbers can be encoded in a variety of other information objects, such as bar codes, numerals, or patterns of dots. Note: during the call there was some confusion between serial number and model number. We agreed that it would be very helpful for all those terms to have example of usages - please add if you have any :-) GROUP: IAO serial number IAO:0000132 lot number A lot number is an information content entity which is an identical sequence of character borne by part of manufactured product or its packaging for each instances of a product class in a discrete batch of an item. Lot numbers are usually assigned to each separate production run of an item. Manufacturing as a lot might be due to a variety of reasons, for example, a single process during which many individuals are made from the same portion of source material. Lot numbers can be encoded in a pattern of other information objects, such as bar codes, numerals, or patterns of dots. GROUP: IAO batch number lot number IAO:0000140 A settings datum is a datum that denotes some configuration of an instrument. 2/3/2009 Feedback from OBI This should be a "setting specification". There is a question of whether it is information about a realizable or not. Pro other specification are about realizables. Cons sometimes specifies a quality which is not a realizable. Alan grouped these in placeholder for the moment. Name by analogy to measurement datum. setting datum IAO:0000141 3/22/2009 Alan Ruttenberg, obsoleted per http://groups.google.com/group/information-ontology/browse_thread/thread/789ad4b7708d5cf4 Need to rework digital entity. Digital quality was suggested by Barry. obsolete_digital quality true IAO:0000144 conclusion textual entity that fucoidan has a small statistically significant effect on AT3 level but no useful clinical effect as in-vivo anticoagulant, a paraphrase of part of the last paragraph of the discussion section of the paper 'Pilot clinical study to evaluate the anticoagulant activity of fucoidan', by Lowenthal et. al.PMID:19696660 A textual entity that expresses the results of reasoning about a problem, for instance as typically found towards the end of scientific papers. 2009/09/28 Alan Ruttenberg. Fucoidan-use-case 2009/10/23 Alan Ruttenberg: We need to work on the definition still Person:Alan Ruttenberg conclusion textual entity IAO:0000178 material information bearer A page of a paperback novel with writing on it. The paper itself is a material information bearer, the pattern of ink is the information carrier. a brain a hard drive A material entity in which a concretization of an information content entity inheres. GROUP: IAO material information bearer IAO:0000179 histogram A histogram is a report graph which is a statistical description of a distribution in terms of occurrence frequencies of different event classes. PERSON:Chris Stoeckert PERSON:James Malone PERSON:Melanie Courtot GROUP:OBI histogram IAO:0000180 heatmap A heatmap is a report graph which is a graphical representation of data where the values taken by a variable(s) are shown as colors in a two-dimensional map. PERSON:Chris Stoeckert PERSON:James Malone PERSON:Melanie Courtot GROUP:OBI heatmap IAO:0000181 Venn diagram A Venn diagram is a report graph showing all hypothetically possible logical relations between a finite collection of sets. PERSON:Chris Stoeckert PERSON:James Malone PERSON:Melanie Courtot WEB: http://en.wikipedia.org/wiki/Venn_diagram Venn diagram IAO:0000182 obsolete_survival curve A survival curve is a report graph which is a graphical representation of data where the percentage of survival is plotted as a function of time. PERSON:Chris Stoeckert PERSON:James Malone PERSON:Melanie Courtot WEB: http://www.graphpad.com/www/book/survive.htm obsolete_survival curve true IAO:0000183 dendrogram Dendrograms are often used in computational biology to illustrate the clustering of genes. A dendrogram is a report graph which is a tree diagram frequently used to illustrate the arrangement of the clusters produced by a clustering algorithm. PERSON:Chris Stoeckert PERSON:James Malone PERSON:Melanie Courtot WEB: http://en.wikipedia.org/wiki/Dendrogram dendrogram IAO:0000184 scatter plot Comparison of gene expression values in two samples can be displayed in a scatter plot A scatterplot is a graph which uses Cartesian coordinates to display values for two variables for a set of data. The data is displayed as a collection of points, each having the value of one variable determining the position on the horizontal axis and the value of the other variable determining the position on the vertical axis. PERSON:Chris Stoeckert PERSON:James Malone PERSON:Melanie Courtot scattergraph WEB: http://en.wikipedia.org/wiki/Scatterplot scatter plot IAO:0000185 A photograph is created by projecting an image onto a photosensitive surface such as a chemically treated plate or film, CCD receptor, etc. PERSON:Alan Ruttenberg PERSON:Joanne Luciano PERSON:Melanie Courtot WEB: http://en.wiktionary.org/wiki/photograph photograph IAO:0000186 photographic print A photographic print is a material entity upon which a photograph generically depends. PERSON:Alan Ruttenberg PERSON:Melanie Courtot photographic print IAO:0000225 obsolescence reason specification The reason for which a term has been deprecated. The allowed values come from an enumerated list of predefined terms. See the specification of these instances for more detailed definitions of each enumerated value. The creation of this class has been inspired in part by Werner Ceusters' paper, Applying evolutionary terminology auditing to the Gene Ontology. PERSON: Alan Ruttenberg PERSON: Melanie Courtot obsolescence reason specification IAO:0000300 textual entity Words, sentences, paragraphs, and the written (non-figure) parts of publications are all textual entities A textual entity is a part of a manifestation (FRBR sense), a generically dependent continuant whose concretizations are patterns of glyphs intended to be interpreted as words, formulas, etc. AR, (IAO call 2009-09-01): a document as a whole is not typically a textual entity, because it has pictures in it - rather there are parts of it that are textual entities. Examples: The title, paragraph 2 sentence 7, etc. MC, 2009-09-14 (following IAO call 2009-09-01): textual entities live at the FRBR (http://en.wikipedia.org/wiki/Functional_Requirements_for_Bibliographic_Records) manifestation level. Everything is significant: line break, pdf and html versions of same document are different textual entities. PERSON: Lawrence Hunter text textual entity IAO:0000301 citation Verspoor, K., Cohen, KB., Hunter, L. Textual characteristics of traditional and Open Access scientific journals are similar, BMC Bioinformatics 2009, 10:183. A textual entity intended to identify a particular publication. PERSON: Lawrence Hunter citation IAO:0000302 author identification L. Hunter A textual entity intended to identify a particular author PERSON: Lawrence Hunter author identification IAO:0000303 institutional identification University of Colorado Denver School of Medicine A textual entity intended to identify a particular institution PERSON: Lawrence Hunter institutional identification IAO:0000304 caption Figure 1: A system diagram describing the modules of the Hanalyzer. Reading methods (green) take external sources of knowledge (blue) and extract information from them, either by parsing structured data or biomedical language processing to extract information from unstructured data. Reading modules are responsible for tracking the provenance of all knowledge. Reasoning methods (yellow) enrich the knowledge that results from reading by, for example, noting two genes that are annotated to the same ontology term or database entry. All knowledge sources, read or reasoned, are assigned a reliability score, and all are combined using that score into a knowledge network (orange) that represents the integration of all sorts of relationship between a pair of genes and a combined reliability score. A data network (also orange) is created from experimental results to be analyzed. The reporting modules (pink) integrate the data and knowledge networks, producing visualizations that can be queried with the associated drill-down tool. A textual entity that describes a figure PERSON: Lawrence Hunter caption IAO:0000305 document title Textual characteristics of traditional and Open Access scientific journals are similar A textual entity that names a document PERSON: Lawrence Hunter document title IAO:0000306 table | T F --+----- T | T F F | F F A textual entity that contains a two-dimensional arrangement of texts repeated at regular intervals across a spatial range, such that the spatial relationships among the constituent texts expresses propositions PERSON: Lawrence Hunter table IAO:0000307 table of abbreviations IAO information artifact ontology OBI ontology of biomedical investiations GO gene ontology A table where the constituent texts are abbreviations and their expansions PERSON: Lawrence Hunter table of abbreviations IAO:0000308 figure Any picture, diagram or table An information content entity consisting of a two dimensional arrangement of information content entities such that the arrangement itself is about something. PERSON: Lawrence Hunter figure IAO:0000309 diagram A molecular structure ribbon cartoon showing helices, turns and sheets and their relations to each other in space. A figure that expresses one or more propositions PERSON: Lawrence Hunter diagram IAO:0000310 document A journal article, patent application, laboratory notebook, or a book A collection of information content entities intended to be understood together as a whole PERSON: Lawrence Hunter document IAO:0000311 publication journal article, newspaper story, book, etc. A document that is the output of a publishing process. PERSON: Chris Stoeckert PERSON: Jie Zheng PERSON: Lawrence Hunter published document Revisit the term in Octorber 2020. Improve the defintion. publication IAO:0000312 publication about an investigation Most scientific journal articles A publication that is about an investigation PERSON: Lawrence Hunter scientific publication publication about an investigation IAO:0000313 patent US Patent 6,449,603 A document that has been accepted by a patent authority PERSON: Lawrence Hunter patent IAO:0000314 document part An abstract, introduction, method or results section. An information content entity that is part of a document. PERSON: Lawrence Hunter document part IAO:0000315 abstract The profusion of high-throughput instruments and the explosion of new results in the scientific literature, particularly in molecular biomedicine, is both a blessing and a curse to the bench researcher. Even knowledgeable and experienced scientists can benefit from computational tools that help navigate this vast and rapidly evolving terrain. In this paper, we describe a novel computational approach to this challenge, a knowledge-based system that combines reading, reasoning and reporting methods to facilitate analysis of experimental data. Reading methods extract information from external resources, either by parsing structured data or biomedical language processing to extract information from unstructured data, and track knowledge provenance. Reasoning methods enrich the knowledge that results from reading by, for example, noting two genes that are annotated to the same ontology term or database entry. Reasoning is also used to combine all sources into a knowledge network that represents the integration of all sorts of relationships between a pair of genes, and to calculate a combined reliability score. Reporting methods combine the knowledge network with a congruent network constructed from experimental data and visualize the combined network in a tool that facilitates the knowledge-based analysis of that data. A summary of the entire document that is substantially smaller than the document it summarizes. It is about the document it summarizes. PERSON: Lawrence Hunter precis abstract IAO:0000316 introduction to a publication about an investigation Section labelled 'introduction' of a typical scientific journal article A part of a publication about an investigation that is about the objective specification (why the investigation is being done) PERSON: Lawrence Hunter background introduction overview introduction to a publication about an investigation IAO:0000317 methods section The section labelled 'Methods' or 'Materials and Methods' in a typical scientific journal article. A part of a publication about an investigation that is about the study design of the investigation PERSON: Lawrence Hunter experimental experimental methods experimental procedures experimental section method methodology methods methods section IAO:0000318 results section The section labelled 'results' in a typical scientific journal article A part of a publication about an investigation that is about a study design execution PERSON: Lawrence Hunter results results section IAO:0000319 discussion section of a publication about an investigation A part of a publication about an investigation that is about the study interpretation of the investigation PERSON: Lawrence Hunter discussion discussion section discussions discussion section of a publication about an investigation IAO:0000320 references section The list of citations found at the end of a scientific publication, grant proposal or patent application, sometimes called "literature cited" or "bibliography" A part of a document that has citations as parts PERSON: Lawrence Hunter literature cited reference reference list references references section IAO:0000321 author list Lawrence Hunter and Kevin Brettonel Cohen A part of a document that enumerates the authors of the document PERSON: Lawrence Hunter author list IAO:0000322 institution list The University of Colorado Denver School of Medicine and the University of Colorado Boulder. A part of a document that has parts that are institution identifications associated with the authors of the document PERSON: Lawrence Hunter institution list IAO:0000323 author contributions section LH conceived of the hypothesis, designed the study and contributed to the writing of the manuscript. KBC executed the experiments, analyzed the data, and contributed to the writing of the manuscript. A part of a publication that is about the specific contributions of each author PERSON: Lawrence Hunter author contributions authors' contribution authors' contributions authors' roles contributions by the authors contributorship author contributions section IAO:0000324 acknowledgements section The authors wish to thank Alan Ruttenberg for his constructive comments about an earlier draft of this manuscript Part of a publication that is about the contributions of people or institutions other than the authors. PERSON: Lawrence Hunter acknowledgement acknowledgements acknowledgment acknowledgments acknowledgements section IAO:0000325 footnote The referent in the text is usually indicated by a special typographic character such as * or a superscripted number, which is also used to indicate the footnote that refers to that text. A part of a document that is about a specific other part of the document. Usually footnotes are spatially segregated from the rest of the document. PERSON: Lawrence Hunter endnote footnotes footnote IAO:0000326 supplementary material to a document A part of a document that is segregated from the rest of the document due to its size PERSON: Lawrence Hunter additional file additional files additional information appendix electronic supplementary material electronic supplementary materials supplemental data supplemental information supplemental material supplementary data supplementary files supplementary information supplementary material supplementary materials supporting information supplementary material to a document IAO:0000327 table of contents A table that relates document parts to specific locations in a document (usually page numbers). This is also a document part (subsumption there should be inferred). PERSON: Lawrence Hunter table of contents IAO:0000328 table of figures A table that relates figures in a document to specific locations in that document (usually page numbers). This is also a document part (subsumption there should be inferred). PERSON: Lawrence Hunter table of figures IAO:0000329 running title A shorter version of a document title PERSON: Lawrence Hunter running title IAO:0000330 copyright section This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License. A document part that describes legal restrictions on making or distributing copies of the document PERSON: Lawrence Hunter copyright section 1 IAO:0000400 A cartesian spatial coordinate datum is a representation of a point in a spatial region, in which equal changes in the magnitude of a coordinate value denote length qualities with the same magnitude 2009-08-18 Alan Ruttenberg - question to BFO list about whether the BFO sense of the lower dimensional regions is that they are always part of actual space (the three dimensional sort) http://groups.google.com/group/bfo-discuss/browse_thread/thread/9d04e717e39fb617 Alan Ruttenberg AR notes: We need to discuss whether it should include site. cartesian spatial coordinate datum http://groups.google.com/group/bfo-discuss/browse_thread/thread/9d04e717e39fb617 1 IAO:0000401 A cartesion spatial coordinate datum that uses one value to specify a position along a one dimensional spatial region Alan Ruttenberg one dimensional cartesian spatial coordinate datum 1 1 IAO:0000402 A cartesion spatial coordinate datum that uses two values to specify a position within a two dimensional spatial region Alan Ruttenberg two dimensional cartesian spatial coordinate datum 1 1 1 IAO:0000403 A cartesion spatial coordinate datum that uses three values to specify a position within a three dimensional spatial region Alan Ruttenberg three dimensional cartesian spatial coordinate datum IAO:0000408 A scalar measurement datum that is the result of measurement of length quality Alan Ruttenberg length measurement datum IAO:0000409 denotator type The Basic Formal Ontology ontology makes a distinction between Universals and defined classes, where the formal are "natural kinds" and the latter arbitrary collections of entities. A denotator type indicates how a term should be interpreted from an ontological perspective. Alan Ruttenberg Barry Smith, Werner Ceusters denotator type IAO:0000414 A scalar measurement datum that is the result of measurement of mass quality 2009/09/28 Alan Ruttenberg. Fucoidan-use-case Person:Alan Ruttenberg mass measurement datum IAO:0000415 hypothesis textual entity that fucoidan has a small statistically significant effect on AT3 level but no useful clinical effect as in-vivo anticoagulant, a paraphrase of part of the last paragraph of the discussion section of the paper 'Pilot clinical study to evaluate the anticoagulant activity of fucoidan', by Lowenthal et. al.PMID:19696660 A textual entity that expresses an assertion that is intended to be tested. 2009/09/28 Alan Ruttenberg. Fucoidan-use-case Person:Alan Ruttenberg hypothesis textual entity IAO:0000416 A scalar measurement datum that is the result of measuring a temporal interval 2009/09/28 Alan Ruttenberg. Fucoidan-use-case Person:Alan Ruttenberg time measurement datum IAO:0000422 A textual entity that is used as directive to deliver something to a person, or organization 2010-05-24 Alan Ruttenberg. Use label for the string representation. See issue https://github.com/information-artifact-ontology/IAO/issues/59 postal address IAO:0000429 email address Alan Ruttenberg 1/3/2012 - Provisional id, see issue at https://github.com/information-artifact-ontology/IAO/issues/130&thanks=130&ts=1325636583 Person:Alan Ruttenberg Person:Chris Stoeckart email address IAO:0000442 author role A role inhering in a person or organization that is realized when the bearer participates in the work which is the basis of the document, in the writing of the document, and signs it with their name. PERSON: Alan Ruttenberg PERSON: Melanie Courtot author role IAO:0000443 A planned process in which journal articles are read or processed and data items are extracted, typically for further analysis or indexing Person:Alan Ruttenberg data item extraction from journal article IAO:0000444 A planned process of making information, such as literature, music, and software etc., available to the public for sale or for free. Person: Jie Zheng https://en.wikipedia.org/wiki/Publishing VEuPathDB publishing process IAO:0000445 A document that is in preparation for submission to be published. PERSON: Jie Zheng EFO_0001795 in preparation VEuPathDB document in preparation for publication IAO:0000572 Recording the current temperature in a laboratory notebook. Writing a journal article. Updating a patient record in a database. A planned process in which a document is created or added to by including the specified input in it. 6/11/9: Edited at OBI workshop. We need to be able identify a child form of information artifact which corresponds to something enduring (not brain like). This used to be restricted to physical document or digital entity as the output, but that excludes e.g. an audio cassette tape Bjoern Peters wikipedia http://en.wikipedia.org/wiki/Documenting documenting IAO:0000573 line graph A line graph is a type of graph created by connecting a series of data points together with a line. PERSON:Chris Stoeckert PERSON:Melanie Courtot line chart GROUP:OBI WEB: http://en.wikipedia.org/wiki/Line_chart line graph IAO:0000574 A new pubmed ID being created for a journal article, and the associated pubmed record containing information to the journal article. A license plate number registered at the DMV to be belonging to a specific vehicle and owner. Placing a barcode on a product and entering information in a database that this barcode is assigned. A planned process in which a new CRID is created, associated with an entity, and stored in the CRID registry thereby registering it as being associated with some entity 2014-05-05: It is the CRID registry that assigns CRIDs, not the users of the registry. Person:Alan Ruttenberg Person:Bjoern Peters Person:Melanie Courtot assigning a CRID assigning a centrally registered identifier IAO:0000575 Articles in Pubmed are reviewed by curators who add MESH terms to the Pubmed records in order to categorize them better and improve the ability to search for them. A planned process in which a CRID registry associates an information content entity with a CRID symbol PERSON:Alan Ruttenberg associating information with a CRID in the CRID registry associating information with a centrally registered identifier in its registry IAO:0000576 a planned process with the objective to establish a system that allows to refer to specific entities of a certain kind and store information about them, by establishing a CRID registry and plan specifications for the process of 1) assigning a CRID and 2) looking up a CRID. MC, 20101124: deprecated following discussion at IAO call 20101124. Term was deemed not necessary - no use case for now. obsolete_establishing a CRID registry true IAO:0000577 The sentence "The article has Pubmed ID 12345." contains a CRID that has two parts: one part is the CRID symbol, which is '12345'; the other part denotes the CRID registry, which is Pubmed. A symbol that is part of a CRID and that is sufficient to look up a record from the CRID's registry. PERSON: Alan Ruttenberg PERSON: Bill Hogan PERSON: Bjoern Peters PERSON: Melanie Courtot CRID symbol Original proposal from Bjoern, discussions at IAO calls centrally registered identifier symbol IAO:0000578 The sentence "The article has Pubmed ID 12345." contains a CRID that has two parts: one part is the CRID symbol, which is '12345'; the other part denotes the CRID registry, which is Pubmed. An information content entity that consists of a CRID symbol and additional information about the CRID registry to which it belongs. 2014-05-05: In defining this term we take no position on what the CRID denotes. In particular do not assume it denotes a *record* in the CRID registry (since the registry might not have 'records'). Alan, IAO call 20101124: potentially the CRID denotes the instance it was associated with during creation. Note, IAO call 20101124: URIs are not always CRID, as not centrally registered. We acknowledge that CRID is a subset of a larger identifier class, but this subset fulfills our current needs. OBI PURLs are CRID as they are registered with OCLC. UPCs (Universal Product Codes from AC Nielsen)are not CRID as they are not centrally registered. PERSON: Alan Ruttenberg PERSON: Bill Hogan PERSON: Bjoern Peters PERSON: Melanie Courtot CRID Original proposal from Bjoern, discussions at IAO calls centrally registered identifier IAO:0000579 PubMed is a CRID registry. It has a code set of PubMed identifiers associated with journal articles. A code set of CRID records, each consisting of a CRID symbol and additional information which was recorded in the code set through an assigning a centrally registered identifier process. Justin Whorton PERSON: Alan Ruttenberg PERSON: Bill Hogan PERSON: Bjoern Peters PERSON: Melanie Courtot CRID registry Original proposal from Bjoern, discussions at IAO calls https://github.com/information-artifact-ontology/IAO/issues/237 centrally registered identifier registry IAO:0000580 Going to the PubMed website and entering a PubMed ID in order to retrieve the Pubmed information associated with that ID. A planned process in which a request to a CRID registry is made to return the information associated with a CRID symbol PERSON: Alan Ruttenberg PERSON: Bill Hogan PERSON: Bjoern Peters PERSON: Melanie Courtot looking up a CRID looking up a centrally registered identifier IAO:0000582 time stamped measurement datum IAO:0000584 pmid:20604925 - time-lapse live cell microscopy A data set that is an aggregate of data recording some measurement at a number of time points. The time series data set is an ordered list of pairs of time measurement data and the corresponding measurement data acquired at that time. Alan Ruttenberg experimental time series time sampled measurement data set IAO:0000590 written name "Bill Clinton" "The Eiffel Tower" "United States of America" A textual entity that denotes a particular in reality. PERSON: Bill Hogan https://github.com/information-artifact-ontology/IAO/issues/114 The qualifier "written" is to set it apart from spoken names. Also, note the restrictions to particulars. We are not naming universals. We could however, be naming, attributive collections which are particulars, so "All people located in the boundaries of the city of Little Rock, AR on June 18, 2011 at 9:50a CDT" would be a name. written name IAO:0000591 A software method (also called subroutine, subprogram, procedure, method, function, or routine) is software designed to execute a specific task. PERSON: Melanie Courtot PERSON: Michel Dumontier https://github.com/information-artifact-ontology/IAO/issues/80 software method IAO:0000592 A software module is software composed of a collection of software methods. PERSON: Melanei Courtot PERSON: Michel Dumontier https://github.com/information-artifact-ontology/IAO/issues/80 software module IAO:0000593 A software library is software composed of a collection of software modules and/or software methods in a form that can be statically or dynamically linked to some software application. PERSON: Melanie Courtot PERSON: Michel Dumontier https://github.com/information-artifact-ontology/IAO/issues/80 software library IAO:0000594 A software application is software that can be directly executed by some processing unit. PERSON: Melanie Courtot PERSON: Michel Dumontier https://github.com/information-artifact-ontology/IAO/issues/80 software application IAO:0000595 A software script is software whose instructions can be executed using a software interpreter. PERSON: Melanie Courtot PERSON: Michel Dumontier https://github.com/information-artifact-ontology/IAO/issues/80 software script IAO:0000605 abbreviation textual entity From Shiba et al. Acta Neuropathol Commun. 2013; 1: 45. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3893467/): BAC: Bacterial artificial chromosome; CR: Calretinin; GFAP: Glial fibrillary acidic protein; MAP: Microtubule-associated protein; MRI: Magnetic resonance imaging; NSC: Neural stem cell; PDA: Patent ductus arteriosus; PMG: Polymicrogyria; PNH: Periventricular nodular heterotopia; VSD: Ventricular septal defect. A textual entity listing abbreviations and their expansions that are used in a document. PERSON: Bill Baumgartner abbreviation textual entity IAO:0000606 abbreviations section The section labelled 'abbreviations' in a typical scientific journal article. A part of a document where abbreviations and their long-forms used within the document are listed. PERSON: Bill Baumgartner abbreviation and acronyms abbreviation list abbreviations abbreviations and acronyms abbreviations list abbreviations used definitions for abbreviations list of abbreviations list of abbreviations used non-standard abbreviations nonstandard abbreviations nonstandard abbreviations and acronyms abbreviations section IAO:0000607 author information section The section labelled 'author information' in a typical scientific journal article, e.g. in Takon. Ann Gen Psychiatry. 2011; 10: 25. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3204268/) A part of a document about the authors that provides biographical information and may discuss how the authors' professional experiences are relevant to the work described in the document. PERSON: Bill Baumgartner author information authors’ information biographies contributor information author information section IAO:0000608 author information textual entity From Takon. Ann Gen Psychiatry. 2011; 10: 25. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3204268/): IT [the author] is the lead paediatrician for ADHD services in East Hertfordshire, UK, where she runs a weekly joint ADHD clinic with the Child and Adolescent psychiatrist and works within an ADHD specialist team. IT also sees children with other neurodisability issues who may have comorbid ADHD, where the presentation may be more complex and challenging to manage. IT has vast experience in managing children with complex ADHD. She has 18 years of experience in paediatrics and also has extensive experience in the use of psychopharmacologic agents in managing children with ADHD. A textual entity expression information about an author of a document. This information may include biographical information and may discuss how the authors' professional experiences are relevant to the work described in the document. PERSON: Bill Baumgartner author information textual entity IAO:0000609 author summary section The section labelled 'synopsis' in a typical scientific journal article, e.g. in Pendse et al. BMC Genomics. 2013; 14: 136. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3608171/) A part of a document, distinct from the abstract, that describes the significance and broader context of the document content. The author summary is often written in a non-technical manner and is aimed at both scientists and non-scientist readers. PERSON: Bill Baumgartner author summary summary synopsis Article submission guidelines for PLoS Genetics (http://journals.plos.org/plosgenetics/s/submission-guidelines) author summary section IAO:0000610 author summary textual entity From Pendse et al. BMC Genomics. 2013; 14: 136. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3608171/): The search for genetic risk factors for common human diseases often relies on the use of linkage and association studies to establish correlation between genomic markers and disease risk. These studies require additional functional evaluation of candidate genes, including their possible interaction with diet and environment. The number of candidate genes is typically large and the development of appropriate genetic tools in mammalian systems is slow. By contrast, large-scale genetic screens, using widely available genetic tools, are routinely conducted in the fruit fly Drosophila melanogaster. In this study, we used Drosophila to screen candidate genes identified in human genome-wide scans as associated with risk of metabolic abnormalities such as type 2 diabetes. We show that a number of human candidate genes have fly orthologs that play an important role in Drosophila tolerance to high dietary sucrose. We further explored some of the specific metabolic abnormalities that can result when these genes’ activities are reduced in flies, focusing on a gene we call dHHEX (CG7056), the fly ortholog of human HHEX. A textual entity, distinct from the abstract, that describes the significance and broader context of the document content. The author summary is often written in a non-technical manner and is aimed at both scientists and non-scientist readers, e.g as described in the article submission guidelines for PLoS Genetics (http://journals.plos.org/plosgenetics/s/submission-guidelines). PERSON: Bill Baumgartner Article submission guidelines for PLoS Genetics (http://journals.plos.org/plosgenetics/s/submission-guidelines). author summary textual entity IAO:0000611 availability section The section labelled 'availability and requirements' in a typical scientific journal article, e.g. Qi et al. BMC Bioinformatics. 2014; 15: 11. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3897912/). A part of a document about a resource described in the document, e.g. software, that describes where and/or how that resource can be obtained. PERSON: Bill Baumgartner availability availability of data data archiving data availability data availability statement data sharing statement availability section IAO:0000612 availability textual entity From Qi et al. BMC Bioinformatics. 2014; 15: 11. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3897912/): Project home page:http://krux.googlecode.com A textual entity expressing the location of a resource, e.g. software, or the manner in which a resource can be obtained. PERSON: Bill Baumgartner availability textual entity IAO:0000613 case report section The section labelled 'case report' in a typical scientific journal article, e.g. in Taglia et al. Acta Myol. 2012 Dec; 31(3): 201–203. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3631801/) A part of a document about the medical history of a specific patient as it relates to the topic of the document. PERSON: Bill Baumgartner case presentation case report case report section IAO:0000614 case report textual entity Excerpt from Taglia et al. Acta Myol. 2012 Dec; 31(3): 201–203. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3631801/): The patient is a 50-year-old man. His medical history was not contributory. At the age of 37 years, he complained of persistent fatigue and dyspnoea even for modest efforts and oedema of lower limbs. The patient was examined at the department of internal medicine of the local hospital, and hospitalised with a diagnosis of dilated cardiomyopathy probably consequence of a myocarditis process. Soon after he was transferred to the cardiologic department of the regional hospital, and pharmacologically treated for heart failure and pulmonary hypertension. A textual entity that expresses a detailed account of a portion of the medical history for a specific patient. PERSON: Bill Baumgartner case report textual entity IAO:0000615 conclusion section The section labelled 'conclusion' in a typical scientific journal article. A part of a document used to summarize the findings discussed in the document. The conclusion section is typically found near the end of a document. PERSON: Bill Baumgartner concluding remarks conclusion conclusions findings summary conclusion section IAO:0000616 conflict of interest section The section labelled 'conflict of interest statement' in a typical scientific journal article. A part of a document used to declare any competing interests regarding the authors and/or funding organization for the work described in the document. PERSON: Bill Baumgartner authors' disclosures of potential conflicts of interest competing financial interests competing interests conflict of interest conflict of interest statement conflict of interests conflicts of interest declaration of competing interest declaration of competing interests declaration of interest declaration of interests disclosure of conflict of interest disclosure of potential conflicts of interest duality of interest statement of interest conflict of interest section IAO:0000617 conflict of interest statement SD [an author] is a Merck employee and Merck is the sponsor of this study. [Taken from 'Effects of obstructive sleep apnoea risk on postoperative respiratory complications: protocol for a hospital-based registry study' Shin et al. 2016 (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4735131/)] A textual entity that expresses a situation involving one or more of the authors, or the funding source of a document whereby the authors or funding source stand to potentially gain (typically financially) from the results reported in the document. PERSON: Bill Baumgartner conflict of interest textual entity IAO:0000618 consent section The section labelled 'consent' in a typical scientific journal article, e.g. Shiba et al. Acta Neuropathol Commun. 2013; 1: 45. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3893467/) A part of a document about the consent process that was used to enroll patients in a study. PERSON: Bill Baumgartner consent consent section IAO:0000619 consent textual entity From Shiba et al. Acta Neuropathol Commun. 2013; 1: 45. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3893467/): Written informed consent was obtained from the patient’s parents for publication of this Case report and any accompanying images. A copy of the written consent is available for review by the Editor-in chief of this journal. A textual entity that documents the consenting process used to enroll patients in a study. PERSON: Bill Baumgartner consent textual entity IAO:0000620 ethical approval section The section labelled 'ethical approval' in a typical scientific journal article. A part of a document about the governance body responsible for approving the work discussed in a document on an ethical basis. PERSON: Bill Baumgartner ethical approval ethical requirements ethics ethics statement ethical approval section IAO:0000621 ethical approval textual entity From McLean et al. Br J Gen Pract. 2014 Jul; 64(624): e440–e447 (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4073730/): The NHS National Research Ethics Service had previously approved the use of these anonymised data for research purposes and this analysis did not require independent review. A textual entity that documents the ethical approval of some study design. PERSON: Bill Baumgartner ethical approval textual entity IAO:0000622 figures section The section labelled 'figures' in a typical scientific journal article. A part of a document that contains one or more figures. PERSON: Bill Baumgartner figures figures section IAO:0000623 funding source declaration section The section labelled 'funding' in a typical scientific journal article. A part of a document used to detail information regarding the source of funding used in support of the generation of the document content. PERSON: Bill Baumgartner financial support funding funding information funding sources funding statement funding/support grants role of the funding source source of funding sources of funding study funding funding source declaration section IAO:0000624 funding souce declaration textual entity From Stephan et al. Accid Anal Prev. 2011 May; 43(3): 1062–1067. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3062852/): This study was supported by the International Collaborative Research Grants Scheme with joint grants from the Wellcome Trust UK (GR071587MA) and the Australian NHMRC (268055). The funding sources played no role in study design, data collection, analysis or interpretation, writing the report, or the decision to submit the paper for publication. A textual entity documenting the source of funding that supported some study. PERSON: Bill Baumgartner funding source declaration textual entity IAO:0000625 future directions section The section labelled 'future directions' in a typical scientific journal article. A part of a document detailing extensions of the described work that may be implemented at some future point in time. PERSON: Bill Baumgartner future challenges future considerations future developments future directions future outlook future perspectives future plans future prospects future research future research directions future studies future work outlook future directions section IAO:0000626 future directions textual entity Excerpt from Wang and Li. Acta Pharmacol Sin. 2016 Jan; 37(1): 25–33. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4722976/): In the future, several questions will need to be resolved regarding the physiological assembly of KCNQ channels and their functional implications in complex neural circuits. First, we still lack sufficiently selective inhibitors and activators among the KCNQ family members. A textual entity expressing ideas regarding future work relevant to work described in a document that could be done. PERSON: Bill Baumgartner future directions textual entity IAO:0000627 genome announcement section The section labelled 'genome announcement' in a typical scientific journal article, e.g. in Kim et al. J Bacteriol. 2011 Oct; 193(19): 5537. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3187466/) A document part announcing the publication of a novel draft genome sequence. PERSON: Bill Baumgartner genome announcement genome announcement section IAO:0000628 genome announcement textual entity Excerpt from Kim et al. J Bacteriol. 2011 Oct; 193(19): 5537. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3187466/): Here we report the genome sequence of Lactobacillus malefermentans KCTC 3548, which we obtained using a whole-genome shotgun strategy (4) with Roche 454 GS (FLX Titanium) pyrosequencing (257,559 reads totaling ∼89.8 Mb; ∼45-fold coverage of the genome) at the Genome Resource Center, Korea Research Institute of Bioscience and Biotechnology (KRIBB). A textual entity that describes the generation and public release of a novel, draft genome sequence. PERSON: Bill Baumgartner genome announcement textual entity IAO:0000629 keyword textual entity From: Fu and Lin. Identification of gene-oriented exon orthology between human and mouse. BMC Genomics. 2012; 13(Suppl 1): S10. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3303729/): Exon orthology; alternative splicing; exon duplication; intron-exon structure. A textual entity listing keywords indicating the major theme(s) of a document. PERSON: Bill Baumgartner keyword textual entity IAO:0000630 keywords section The section labelled 'keywords' in a typical scientific journal article. A part of a document where keywords selected by the author to categorize the major theme(s) of a document are listed. PERSON: Bill Baumgartner keywords keywords section IAO:0000631 study limitations section The section labelled 'limitations' in a typical scientific journal article. A part of a document about biases or short comings related to the study design and execution. PERSON: Bill Baumgartner limitations study limitations Author guidelines published by The Society for Academic Emergency Medicine. (http://onlinelibrary.wiley.com/journal/10.1111/(ISSN)1553-2712/homepage/ForAuthors.html) study limitations section IAO:0000632 study limitations textual entity Excerpt from the Limitations section of Fermann et al 2015, Acad Emerg Med. 2015 Mar; 22(3): 299–307 (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4405051/). Owing to the nature of a post hoc study, any significant values must be interpreted with caution. In the current analysis, no multiple testing was conducted and p-values remain unadjusted. Moreover, a selection bias arising from the randomized open-label design of the original EINSTEIN PE study cannot be ruled out. A textual entity addressing a shortcoming or bias of a study design or execution. PERSON: Bill Baumgartner Author guidelines published by The Society for Academic Emergency Medicine. (http://onlinelibrary.wiley.com/journal/10.1111/(ISSN)1553-2712/homepage/ForAuthors.html) study limitations textual entity IAO:0000633 materials section The section labelled 'materials' in a typical scientific journal article, e.g. Nguyen et al. BMC Bioinformatics. 2010; 11: 279. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2889936/) A part of a document about the materials required to reproduce the content of the document. PERSON: Bill Baumgartner materials materials section IAO:0000634 notes section The section labelled 'notes' in a typical scientific journal article, e.g. McLean et al. Br J Gen Pract. 2014 Jul; 64(624): e440–e447 (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4073730/): A part of a document containing typically short notes about the document itself and/or the authors. Often the notes section contains subsections related to funding, competing interests, ethical approval, etc. PERSON: Bill Baumgartner notes notes section IAO:0000635 patients section The section labelled 'patients' in a typical scientific journal article, e.g. in Citak et al. Acta Orthop. 2013 Jun; 84(3): 326–327. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3715825/) A part of a document about the patients that participated in a study. PERSON: Bill Baumgartner patients section IAO:0000636 patients textual entity Excerpt from Citak et al. Acta Orthop. 2013 Jun; 84(3): 326–327. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3715825/): Between January 1996 and February 2012, we treated 4 patients with interprosthetic femoral fractures (3 of them women) (Figure 2) using a custom-made interposition device (Waldemar Link GmbH, Hamburg, Germany) (Figure 1). Mean age was 74 (59–86) years. The fractures occurred mean 18 (13–28) years after primary THA and mean 14 (10–17) years after primary TKA. At the latest follow-up, after mean 8 (0.5–16) years, revision surgery with a total femur replacement was required in 1 case due to aseptic loosening. No other complications requiring revision surgery occurred. A textual entity expressing information regarding the patients used in a study. PERSON: Bill Baumgartner patients textual entity IAO:0000637 pre-publication history section The section labelled 'pre-publication history' in a typical scientific journal article, e.g. in Xiao et al. BMC Anesthesiol. 2013; 13: 33. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4016475/) A part of the document about the publication history of a document. This section typically details dates of document submission to a journal and dates of any re-submissions as well as reviewer comments and responses to reviewers by the authors. PERSON: Bill Baumgartner notice of republication pre-publication history pre-publication history section IAO:0000638 pre-publication history textual entity From Xiao et al. BMC Anesthesiol. 2013; 13: 33. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4016475/): The pre-publication history for this paper can be accessed here: http://www.biomedcentral.com/1471-2253/13/33/prepub A textual entity that expresses the pre-publication history (submission dates, reviewer comments, etc) for a document, often including a hyperlink to a web page detailing the information. PERSON: Bill Baumgartner pre-publication history textual entity IAO:0000639 related work section The section labelled 'related work' in a typical scientific journal article, e.g. Žitnik and Zupan. Bioinformatics. 2015 Jun 15; 31(12): i230–i239. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4542780/) A part of a document about work in other publications that is relevant to the content of the document. PERSON: Bill Baumgartner related literature related work related work section IAO:0000640 related work textual entity Excerpt from Žitnik and Zupan. Bioinformatics. 2015 Jun 15; 31(12): i230–i239. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4542780/): Our work presented here is similar in spirit to our recently developed methodology for data fusion via collective matrix factorization (Žitnik and Zupan, 2015). A textual entity that discusses work from other publications and expresses their relevancy to the content of a document. PERSON: Bill Baumgartner related work textual entity IAO:0000641 requirements section The section labelled 'availability and requirements' in a typical scientific journal article, e.g. Qi et al. BMC Bioinformatics. 2014; 15: 11. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3897912/). A part of a document about a resource described in the document, e.g. software, that describes the requirements necessary to use the resource, e.g. operating systems, hardware, etc. in the case of a software resource. PERSON: Bill Baumgartner requirements requirements section IAO:0000642 requirements textual entity From Qi et al. BMC Bioinformatics. 2014; 15: 11. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3897912/): • Operating systems: Platform independent • Programming language: Matlab, R, Python • Other requirements: None • License: GNU GPL v3 • Any restrictions to use by non-academics: None A textual entity that expresses the requirements necessary to use a resource, e.g. software. PERSON: Bill Baumgartner requirements textual entity IAO:0000643 statistical analysis textual entity From Mondo et al. Cardiovasc J Afr. 2013 Mar; 24(2): 28–33. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3734881/): Data were captured into EPI-DATA (version 3.1), cleaned and then exported to Stata version 10 for analysis. Continuous variables were summarised as mean (± standard deviation) and median (inter-quartile range), and presented in the tables. Categorical data were analysed using frequency and percentages, and results are presented in frequency tables and bar charts. Test of significance (p-value) was determined using the chi-square test. A p-value of less than 0.05 was considered significant. A textual entity documenting statistical analysis tools and techniques employed. PERSON: Bill Baumgartner statistical analysis textual entity IAO:0000644 statistical analysis section The section labelled 'statistical analysis' in a typical scientific journal article, e.g. Mondo et al. Cardiovasc J Afr. 2013 Mar; 24(2): 28–33. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3734881/) A part of the document used to describe the statistical methodologies employed in the work presented in the document. PERSON: Bill Baumgartner statistical analysis statistical analysis section IAO:0000645 tables section The section labelled 'tables' in a typical scientific journal article. A part of a document that contains one or more tables. PERSON: Bill Baumgartner tables tables section IAO:0000646 An identifier that denotes some postal delivery route, some aggregate of postal delivery routes or a geographical region and was created for the purpose of sorting and delivering mail. Mathias Brochhausen postal code IAO:0000647 A plan specification that if realized, is realized by the delivery of mail to some facility or mailbox within some geographical region. Mathias Brochhausen Postal delivery route IAO:0000648 A postal code that is used in the United States for the purpose of sorting and delivering mail, and that denotes some postal delivery route or some aggregate of postal delivery routes. Mathias Brochhausen ZIP code zone improvement plan code IAO:0000650 database extract, transform, and load process A planned process which takes as input a database and fills another database by extracting concretizations of information entities from the first, transforming them, and loading the transformed concretizations into the second. Alan Ruttenberg 12/21/16: Maybe this definition instead: A planned process which takes as input a database and copies concretizations from the first, optionally transforms then copies the result to the second Alan Ruttenberg 12/21/16: We don't define database in IAO, currently, as the bare word is ambiguous. Reasonable interpretations of the word might be the material entity, an information structure, an information content entity. However this definition commits, at least, to there being some material thing which bear concretizations of information entities and that there are new concretizations created during the process. We consider the ETL process in terms of information entities rather than the concretizations. No committment is made as to whether the specified output. PERSON:Alan Ruttenberg ETL WEB:https://en.wikipedia.org/wiki/Extract,_transform,_load database extract, transform, and load process IAO:0000701 descriptive data section A document part that lists and defines data variables, describes data characteristics (e.g. missing data information) and any assumptions and simplifications made. PERSON: Chen Yang PERSON: Jie Zheng https://www.equator-network.org/reporting-guidelines/prisma/ ONE ontology descriptive data section IAO:0000702 additional results section A results section that reports analyses other than main results of the study (e.g. subgroups analyses, adjusted analyses, sensitivity analyses, etc.) PERSON: Chen Yang PERSON: Jie Zheng https://www.equator-network.org/reporting-guidelines/consort/ https://www.equator-network.org/reporting-guidelines/prisma/ https://www.equator-network.org/reporting-guidelines/strobe/ ONE ontology additional results section IAO:0000703 research participants section A document part that describes human subject(s) that participated in a study (e.g. inclusion & exclusion criteria, recruitment methods, reasons for non-participation, grouping and randomisation, methods of follow-up, etc.). PERSON: Chen Yang PERSON: Jie Zheng https://www.equator-network.org/reporting-guidelines/consort/ https://www.equator-network.org/reporting-guidelines/prisma/ https://www.equator-network.org/reporting-guidelines/strobe-nut/ ONE ontology research participants section IAO:0000704 measurement methods section A methods section that describes details of data assessment methods (data measurement). PERSON: Chen Yang PERSON: Jie Zheng https://www.equator-network.org/reporting-guidelines/strobe/ ONE ontology measurement methods section IAO:0000705 research settings section A document part that describes the physical/social/cultural conditions around a research trial. PERSON: Chen Yang PERSON: Jie Zheng https://www.ncbi.nlm.nih.gov/books/NBK262175/ ONE ontology research settings section IAO:0000706 study bias section A study limitations section that describes systematic error introduced into sampling or testing by selecting or encouraging one outcome or answer over others. PERSON: Chen Yang PERSON: Jie Zheng DOI: 10.1097/PRS.0b013e3181de24bc ONE ontology study bias section IAO:0000707 graphical abstract An abstract that is pictorial summary of the main findings described in the document. PERSON: Jie Zheng PERSON: Tim Beck visual abstract https://www.elsevier.com/authors/journal-authors/graphical-abstract Biomedical literature NLP project graphical abstract IAO:0000708 A centrally registered identifier that is issued by ORCID (https://orcid.org/) and used to persistantly identify oneself as a human researcher or contributor. "You can connect your iD with your professional information — affiliations, grants, publications, peer review, and more. You can use your iD to share your information with other systems, ensuring you get recognition for all your contributions, saving you time and hassle, and reducing the risk of errors." [https://orcid.org/] This class was originally defined in Apollo_SV (http://purl.obolibrary.org/obo/APOLLO_SV_00000496) but due to it being more in scope of IAO, it was decided to add it to IAO and deprecate its Apollo_SV equivalent. (2022-10-25) http://orcid.org/0000-0002-1595-3213 ORCID ID ORCiD Open Researcher and Contributor ID Open Researcher and Contributor Identifier https://orcid.org/ https://github.com/information-artifact-ontology/IAO/issues/259 ORCID identifier IAO:0020000 identifier An information content entity that is the outcome of a dubbing process and is used to refer to one instance of entity shared by a group of people to refer to that individual entity. Justin Whorton Mathias Brochhausen proper name https://github.com/information-artifact-ontology/IAO/issues/237 Mathias Brochhausen Sep 29, 2016: The current definition has been amended from the previous version: "A proper name is an information content entity that is the outcome of a dubbing process and is used to refer to one instance of entity shared by a group of people to refer to that individual entity." to more accuratly reflect the necessary and sufficient condition on the class. (MB) identifier IAO:0020001 alphabetic letters, Chinese characters, numerical digits, punctuation marks, and the individual symbols of any of the world's writing systems An information content entity that is a fundamental unit in a written language. Justin Whorton http://en.wikipedia.org/wiki/Grapheme https://github.com/information-artifact-ontology/IAO/issues/237 Mathias Brochhausen Grapheme is not about anything and hence is likely to not be an information content entity. If a new subclass of GDC for information structure entities is created it should move there. grapheme IAO:0020010 A planned process that provides a reference to an individual entity shared by a group of subscribers to refer to that individual entity. Justin Whorton Mathias Brochhausen dubbing process naming https://github.com/information-artifact-ontology/IAO/issues/237 Mathias Brochhausen identifier creating process IAO:0020015 An identifier referring to an individual entity that is ascribed personhood by the user of the identifier. Justin Whorton Mathias Brochhausen http://en.wikipedia.org/wiki/Personal_name https://github.com/information-artifact-ontology/IAO/issues/237 Personal names "today usually comprises a given name bestowed at birth or at a young age plus a surname. It is nearly universal for a human to have a name; except in rare cases, for example feral children growing up in isolation, or infants orphaned by natural disaster for whom no written record survives.[citation needed] The Convention on the Rights of the Child specifies that a child has the right from birth to a name. Certain isolated tribes, such as the Machiguenga of the Amazon, also lack personal names." (http://en.wikipedia.org/wiki/Personal_name) Personal names to not include names of fictional characters, e.g. Sherlock Holmes. Sep 29, 2016: The comment that including the wikipedia definition of personal name is not to be interpreted in a way that restricts this class to only contain strings of letters. A numerical or alphanumerical identifier that denotes a human is being is a personal name, too. (MB) personal name IAO:0020016 A personal name that specifies and differentiates between members of a group of individuals, especially in a family, all of whose members usually share the same family name (surname). A given name is purposefully given, usually by a child's parents at or near birth, in contrast to an inherited one such as a family name Justin Whorton Mathias Brochhausen first name http://en.wikipedia.org/wiki/Given_name https://github.com/information-artifact-ontology/IAO/issues/237 given name IAO:0020017 An identifier that is typically a part of a person's name which has been passed, according to law or custom, from one or both parents to their children. Justin Whorton Mathias Brochhausen last name surname http://en.wikipedia.org/wiki/Family_name https://github.com/information-artifact-ontology/IAO/issues/237 family name IAO:0020020 An information content entity that is a collection of other information content entities that has been created to identify or annotate things in a specified domain, and where the intention of its creators is that the collection has a one-to-one correspondence with those things. Alan Ruttenberg Justin Whorton Mathias Brochhausen code map code system codeset coding system controlled vocabulary https://github.com/information-artifact-ontology/IAO/issues/237 Alan Ruttenberg Clint Dowland Matt Diller Sarah Bost William R. Hogan Code sets might include non-entities/things (e.g. missing thumbs). Does not imply absence vs. presence of any taxonomy. Does not imply that aggregated entities denote particulars, universals, or defined classes (a.k.a. attributive collections) or even that they denote only one of these three types of entities. Each aggregated entity is often (but not necessarily) associated with a text string—variously called a “description,” “name,” “title,” or “label”—that helps humans reach the target of denotation. When there is no such string, it is almost always because the entities take the form of human language words. For example, a “sex” or “gender” code set could contain “MALE” and “FEMALE,” or even “M” and “F” (by convention, we understand what these mean). For National Drug Codes (NDCs) and similar code sets, there doesn’t even have to be a single, fully-concretized copy somewhere (for example, for NDCs there is no centralized database or repository where they all live as one instance of concretization of code set). The code set can be “distributively” concretized. This seems like an unusual exception, but it also likely applies to Universal Product Codes (UPCs) and their follow on Global Trade Item Numbers (GTINs). For each given domain, there can potentially exist multiple code sets. The multiplicity of code sets is partially due to the different specific purposes of those code sets. Many code sets are created for a specific purpose in addition to merely identifying or annotating core ideas of a specified domain. The information content entities do not denote each other. code set IAO:8000000 ontology module I have placed this under 'data about an ontology part', but this can be discussed. I think this is OK if 'part' is interpreted reflexively, as an ontology module is the whole ontology rather than part of it. ontology file This class and it's subclasses are applied to OWL ontologies. Using an rdf:type triple will result in problems with OWL-DL. I propose that dcterms:type is instead used to connect an ontology URI with a class from this hierarchy. The class hierarchy is not disjoint, so multiple assertions can be made about a single ontology. ontology module IAO:8000001 base ontology module An ontology module that comprises only of asserted axioms local to the ontology, excludes import directives, and excludes axioms or declarations from external ontologies. base ontology module IAO:8000002 editors ontology module An ontology module that is intended to be directly edited, typically managed in source control, and typically not intended for direct consumption by end-users. source ontology module editors ontology module IAO:8000003 main release ontology module An ontology module that is intended to be the primary release product and the one consumed by the majority of tools. TODO: Add logical axioms that state that a main release ontology module is derived from (directly or indirectly) an editors module main release ontology module IAO:8000004 bridge ontology module An ontology module that consists entirely of axioms that connect or bridge two distinct ontology modules. For example, the Uberon-to-ZFA bridge module. bridge ontology module IAO:8000005 import ontology module A subset ontology module that is intended to be imported from another ontology. TODO: add axioms that indicate this is the output of a module extraction process. import file import ontology module IAO:8000006 subset ontology module An ontology module that is extracted from a main ontology module and includes only a subset of entities or axioms. ontology slim subset ontology subset ontology module IAO:8000007 curation subset ontology module A subset ontology that is intended as a whitelist for curators using the ontology. Such a subset will exclude classes that curators should not use for curation. curation subset ontology module IAO:8000008 analysis ontology module An ontology module that is intended for usage in analysis or discovery applications. analysis subset ontology module IAO:8000009 single layer ontology module A subset ontology that is largely comprised of a single layer or strata in an ontology class hierarchy. The purpose is typically for rolling up for visualization. The classes in the layer need not be disjoint. ribbon subset single layer subset ontology module IAO:8000010 exclusion subset ontology module A subset of an ontology that is intended to be excluded for some purpose. For example, a blacklist of classes. antislim exclusion subset ontology module IAO:8000011 external import ontology module An imported ontology module that is derived from an external ontology. Derivation methods include the OWLAPI SLME approach. external import external import ontology module IAO:8000012 species subset ontology module A subset ontology that is crafted to either include or exclude a taxonomic grouping of species. taxon subset species subset ontology module IAO:8000013 reasoned ontology module An ontology module that contains axioms generated by a reasoner. The generated axioms are typically direct SubClassOf axioms, but other possibilities are available. reasoned ontology module IAO:8000014 generated ontology module An ontology module that is automatically generated, for example via a SPARQL query or via template and a CSV. TODO: Add axioms (using PROV-O?) that indicate this is the output-of some reasoning process generated ontology module IAO:8000015 template generated ontology module An ontology module that is automatically generated from a template specification and fillers for slots in that template. template generated ontology module IAO:8000016 taxonomic bridge ontology module taxonomic bridge ontology module IAO:8000017 ontology module subsetted by expressivity ontology module subsetted by expressivity IAO:8000018 obo basic subset ontology module A subset ontology that is designed for basic applications to continue to make certain simplifying assumptions; many of these simplifying assumptions were based on the initial version of the Gene Ontology, and have become enshrined in many popular and useful tools such as term enrichment tools. Examples of such assumptions include: traversing the ontology graph ignoring relationship types using a naive algorithm will not lead to cycles (i.e. the ontology is a DAG); every referenced term is declared in the ontology (i.e. there are no dangling clauses). An ontology is OBO Basic if and only if it has the following characteristics: DAG Unidirectional No Dangling Clauses Fully Asserted Fully Labeled No equivalence axioms Singly labeled edges No qualifier lists No disjointness axioms No owl-axioms header No imports obo basic subset ontology module IAO:8000019 ontology module subsetted by OWL profile ontology module subsetted by OWL profile IAO:8000020 EL++ ontology module EL++ ontology module MCRO:0000001 The Model Card (MC) is the document designed for transparent reporting of AI model provenance, usage, and ethics-informed evaluation. A report that details characteristics of machine learning model to supplement its release to the public. Margaret Mitchell, Simone Wu, Andrew Zaldivar, Parker Barnes, Lucy Vasserman, Ben Hutchinson, Elena Spitzer, Inioluwa Deborah Raji, Timnit Gebru. 2019. Model Cards for Model Reporting. In FAT* ’19: Conference on Fairness, Accountability, and Transparency, January 29–31, 2019, Atlanta, GA, USA. ACM, New York, NY, USA, 10 pages. https://doi.org/10.1145/3287560. 3287596 Model Card Report MCRO:0000002 Section content in this section should describe information in "how close or far off a given set of measurements (observations or readings) are to their true value" https://en.wikipedia.org/wiki/Accuracy_and_precision Accuracy Information Section MCRO:0000003 The content describes information pertaining to the area under the ROC curve. Area Under the Curve Information Section AUC MCRO:0000004 information relating to the citation for the targetted model. This is part of the model details component of the model card report Citation Information Section MCRO:0000005 This section pertains to "Factors" of the model card report by Mitchell et al., 2019. The considerations section includes qualitative information about your model, including some analysis of its risks and limitations. As such, this section usually requires careful consideration, and conversations with many relevant stakeholders, including other model developers, dataset producers, and downstream users likely to interact with your model, or be affected by its outputs. Consideration Information Section Factors MCRO:0000006 Information about the data that was used to develop the model Dataset Information Section MCRO:0000007 Content information that is a type of risk information that is specific to ethical consideration if using the model. Ethical Consideration Section MCRO:0000008 The section is devoted in describing the evaluation dataset. "Evaluation datasets should include datasets that are publicly available for third-party use. These could be existing datasets or new ones provided alongside the model card analyses to enable further benchmarking... the evaluation datasets should not only be representative of the model’s typical use cases but also anticipated test scenarios and challenging cases." Details on the dataset(s) used for the quantitative analyses in the card. - Datasets - Motivation - Preprocessing" (Mitchell et al., 2019) Margaret Mitchell, Simone Wu, Andrew Zaldivar, Parker Barnes, Lucy Vasserman, Ben Hutchinson, Elena Spitzer, Inioluwa Deborah Raji, Timnit Gebru. 2019. Model Cards for Model Reporting. In FAT* ’19: Conference on Fairness, Accountability, and Transparency, January 29–31, 2019, Atlanta, GA, USA. ACM, New York, NY, USA, 10 pages. https://doi.org/10.1145/3287560. 3287596 Evaluation Data Information Section MCRO:0000009 The F1 score is the harmonic mean of the precision and recall. This section describes information relating to the F1 score revealed by the performance of the machine learning model. https://en.wikipedia.org/wiki/F-score F1-Score Information Section MCRO:0000010 The section describes information about the false discovery rate of the machine learning model. "The false discovery rate (FDR) is a method of conceptualizing the rate of type I errors in null hypothesis testing when conducting multiple comparisons. FDR-controlling procedures are designed to control the FDR, which is the expected proportion of "discoveries" (rejected null hypotheses) that are false (incorrect rejections of the null)". quivalently, the FDR is the expected ratio of the number of false positive classifications (false discoveries) to the total number of positive classifications (rejections of the null). The total number of rejections of the null include both the number of false positives (FP) and true positives (TP). Simply put, FDR = FP / (FP + TP). FDR-controlling procedures provide less stringent control of Type I errors compared to familywise error rate (FWER) controlling procedures (such as the Bonferroni correction), which control the probability of at least one Type I error. Thus, FDR-controlling procedures have greater power, at the cost of increased numbers of Type I errors." https://en.wikipedia.org/wiki/False_discovery_rate False Discovery Rate Information Section MCRO:0000011 This section describes information relating to false ommision rate of the performance of the machine learning model. FOR is the probability that the true value is positive. False Ommission Rate Section Information FOR MCRO:0000012 This content describes the information pertaining to the model's false postive rate. "A false positive error, or false positive, is a result that indicates a given condition exists when it does not. For example, a pregnancy test which indicates a woman is pregnant when she is not, or the conviction of an innocent person. A false positive error is a type I error where the test is checking a single condition, and wrongly gives an affirmative (positive) decision." https://en.wikipedia.org/wiki/False_positives_and_false_negatives#False_positive_error False Positive Rate Information Section MCRO:0000013 This content summarizes the input and output data format for the model. Format Information Section MCRO:0000014 A section describing the set of graphics accompanying the model card's dataset Graphic Collection Section MCRO:0000015 This secton content serves to describe the inputed data's format for the machine learning model. Input Format Information Section MCRO:0000016 Section for information about the licensing for the machine learning model. License Information Section MCRO:0000017 Content section relating to the technical limits of the machine learning model (e.g. trained on ungeneralized data). Limitation Information Section MCRO:0000018 Content section of the model card that addresses the risk or ethical consideration of the model. Mitigation Strategy Section MCRO:0000019 Content section summarizing the architecture of the model (software used, algortihm, etc.) Model Architecture Information Section MCRO:0000020 a graph content specifically for a model card report Model Card Graphic MCRO:0000021 Basic information about the model that includes licensing information, owner information, the architecture of the model (algorthim employed), references (cited papers), and versioning information. Margaret Mitchell, Simone Wu, Andrew Zaldivar, Parker Barnes, Lucy Vasserman, Ben Hutchinson, Elena Spitzer, Inioluwa Deborah Raji, Timnit Gebru. 2019. Model Cards for Model Reporting. In FAT* ’19: Conference on Fairness, Accountability, and Transparency, January 29–31, 2019, Atlanta, GA, USA. ACM, New York, NY, USA, 10 pages. https://doi.org/10.1145/3287560. 3287596 Model Detail Section MCRO:0000022 Section summarizing the content relating to the parameters for the development of the model. Model Parameter Section MCRO:0000023 "for use on black-and-white images only; please consider our research group’s full-color-image classifier for color images.” "not for use on text examples shorter than 100 tokens" "Here, the model card should highlight technology that the model might easily be confused with, or related contexts that users could try to apply the model to. This section may provide an opportunity to recommend a related or similar model that was designed to better meet that particular need, where possible. This section is inspired by warning labels on food and toys, and similar disclaimers presented in electronic datasheets." Content that is a type of use case information but specific to use cases that are out of scope of the intended use case. Margaret Mitchell, Simone Wu, Andrew Zaldivar, Parker Barnes, Lucy Vasserman, Ben Hutchinson, Elena Spitzer, Inioluwa Deborah Raji, Timnit Gebru. 2019. Model Cards for Model Reporting. In FAT* ’19: Conference on Fairness, Accountability, and Transparency, January 29–31, 2019, Atlanta, GA, USA. ACM, New York, NY, USA, 10 pages. https://doi.org/10.1145/3287560. 3287596 Out of Scope Use Case Section Information MCRO:0000024 This secton content serves to describe the outputted data's format for the machine learning model. Output Format Information Section MCRO:0000025 Section for the information about the individuals involved in the development of the machine learning model. This includes contact information, the names of the individuals, etc. Owner Information Section MCRO:0000026 This section is for the description of the precision and recall information of the machine learning model's performance. Percision-Recall Curve Information Section MCRO:0000027 Section content here summarizing the information about the metrics (precision, recall, f1 score, etc.) that measured the performance of the model. One can report the values and portion of the data (slice). Performance Metric Information Section MCRO:0000028 personally identifiable information as "any information about an individual maintained by an agency, including (1) any information that can be used to distinguish or trace an individual's identity, such as name, social security number, date and place of birth, mother's maiden name, or biometric records; and (2) any other information that is linked or linkable to an individual, such as medical, educational, financial, and employment information." The section should specificially describe information about the personally identifiable datasets. https://en.wikipedia.org/wiki/Personal_data https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-122.pdf Personally Identifiable Data Information Section MCRO:0000029 "This section details whether the model was developed with general or specific tasks in mind (e.g., plant recognition worldwide or in the Pacific Northwest). The use cases may be as broadly or narrowly defined as the developers intend. For example, if the model was built simply to label images, then this task should be indicated as the primary intended use case." Margaret Mitchell, Simone Wu, Andrew Zaldivar, Parker Barnes, Lucy Vasserman, Ben Hutchinson, Elena Spitzer, Inioluwa Deborah Raji, Timnit Gebru. 2019. Model Cards for Model Reporting. In FAT* ’19: Conference on Fairness, Accountability, and Transparency, January 29–31, 2019, Atlanta, GA, USA. ACM, New York, NY, USA, 10 pages. https://doi.org/10.1145/3287560. 3287596 Primary Intended Use Case Information Section MCRO:0000030 This section describes the primary intended user for the machine learning model. "For example, was the model developed for entertainment purposes, for hobbyists, or enterprise solutions? This helps users gain insight into how robust the model may be to different kinds of inputs." Margaret Mitchell, Simone Wu, Andrew Zaldivar, Parker Barnes, Lucy Vasserman, Ben Hutchinson, Elena Spitzer, Inioluwa Deborah Raji, Timnit Gebru. 2019. Model Cards for Model Reporting. In FAT* ’19: Conference on Fairness, Accountability, and Transparency, January 29–31, 2019, Atlanta, GA, USA. ACM, New York, NY, USA, 10 pages. https://doi.org/10.1145/3287560. 3287596 Primary Intended User Information Section MCRO:0000031 content overview of the quantatitve analysis of the model, specifically the performance of the model Quantative Analysis Section need to connect evaluation data information and training data information should their be a specified graphic collection for Quantative Analysis? Quantative Analysis MCRO:0000032 information for any references related to the machine learning model (research papers, website, etc.) Reference Information Section MCRO:0000033 Content information relating to potential uncertainity about utilizing the model Risk Information Section MCRO:0000034 Information relating to sensitive datasets that contain info like personal information that was used to develop the machine learning model Sensitive Data Information Section MCRO:0000035 The section is devoted in descrbing the synthetic evaluation datasets used for a machine learning model. Synthetic evaluation datasets are a type of evaluation dataset. "It is often difficult to find datasets that represent populations outside of the initial domain used in training. In some of these situations, synthetically generated datasets may provide representation for use cases that would otherwise go unevaluated" (Mitchell et al., 2019). This section should described the aforementioned. Margaret Mitchell, Simone Wu, Andrew Zaldivar, Parker Barnes, Lucy Vasserman, Ben Hutchinson, Elena Spitzer, Inioluwa Deborah Raji, Timnit Gebru. 2019. Model Cards for Model Reporting. In FAT* ’19: Conference on Fairness, Accountability, and Transparency, January 29–31, 2019, Atlanta, GA, USA. ACM, New York, NY, USA, 10 pages. https://doi.org/10.1145/3287560. 3287596 Synthetic Evaluation Data Information Section MCRO:0000036 Content involving known trade-offs for the use of the model. Trade offs might include performance or technical or ethical. "This section should list additional concerns that were not covered in the previous sections. For example, did the results suggest any further testing? Were there any relevant groups that were not represented in the evaluation dataset? Are there additional recommendations for model use? What are the ideal characteristics of an evaluation dataset for this model?" Margaret Mitchell, Simone Wu, Andrew Zaldivar, Parker Barnes, Lucy Vasserman, Ben Hutchinson, Elena Spitzer, Inioluwa Deborah Raji, Timnit Gebru. 2019. Model Cards for Model Reporting. In FAT* ’19: Conference on Fairness, Accountability, and Transparency, January 29–31, 2019, Atlanta, GA, USA. ACM, New York, NY, USA, 10 pages. https://doi.org/10.1145/3287560. 3287596 Trade-off Information Section Caveats Recommendations MCRO:0000037 The section is for information about the training data used for evaluation of a machine learning model. Margaret Mitchell, Simone Wu, Andrew Zaldivar, Parker Barnes, Lucy Vasserman, Ben Hutchinson, Elena Spitzer, Inioluwa Deborah Raji, Timnit Gebru. 2019. Model Cards for Model Reporting. In FAT* ’19: Conference on Fairness, Accountability, and Transparency, January 29–31, 2019, Atlanta, GA, USA. ACM, New York, NY, USA, 10 pages. https://doi.org/10.1145/3287560. 3287596 Training Data Information Section MCRO:0000038 The content here involves information about intential uses of the model. "This section should allow readers to quickly grasp what the model should and should not be used for, and why it was created. It can also help frame the statistical analysis presented in the rest of the card, including a short description of the user(s), use-case(s), and context(s) for which the model was originally developed." Margaret Mitchell, Simone Wu, Andrew Zaldivar, Parker Barnes, Lucy Vasserman, Ben Hutchinson, Elena Spitzer, Inioluwa Deborah Raji, Timnit Gebru. 2019. Model Cards for Model Reporting. In FAT* ’19: Conference on Fairness, Accountability, and Transparency, January 29–31, 2019, Atlanta, GA, USA. ACM, New York, NY, USA, 10 pages. https://doi.org/10.1145/3287560. 3287596 Use Case Information Section Intended Use MCRO:0000039 Content information pertaining to intended users of the model. This includes individuals that may be impacted as an outcome of the use of the model. target user for the model User Information Section Intended User Information MCRO:0000040 This content section describes any versioning information for the machine learning model. Version Information Section OBI:0000011 planned process planned process Injecting mice with a vaccine in order to test its efficacy A process that realizes a plan which is the concretization of a plan specification. A processual entity that realizes a plan which is the concretization of a plan specification. 'Plan' includes a future direction sense. That can be problematic if plans are changed during their execution. There are however implicit contingencies for protocols that an agent has in his mind that can be considered part of the plan, even if the agent didn't have them in mind before. Therefore, a planned process can diverge from what the agent would have said the plan was before executing it, by adjusting to problems encountered during execution (e.g. choosing another reagent with equivalent properties, if the originally planned one has run out.) We are only considering successfully completed planned processes. A plan may be modified, and details added during execution. For a given planned process, the associated realized plan specification is the one encompassing all changes made during execution. This means that all processes in which an agent acts towards achieving some objectives is a planned process. Bjoern Peters branch derived 6/11/9: Edited at workshop. Used to include: is initiated by an agent This class merges the previously separated objective driven process and planned process, as they the separation proved hard to maintain. (1/22/09, branch call) planned process OBI:0000066 investigation a planned process that consists of parts: planning, study design execution, documentation and which produce conclusion(s). investigation OBI:0000245 organization PMID: 16353909.AAPS J. 2005 Sep 22;7(2):E274-80. Review. The joint food and agriculture organization of the United Nations/World Health Organization Expert Committee on Food Additives and its role in the evaluation of the safety of veterinary drug residues in foods. An entity that can bear roles, has members, and has a set of organization rules. Members of organizations are either organizations themselves or individual people. Members can bear specific organization member roles that are determined in the organization rules. The organization rules also determine how decisions are made on behalf of the organization by the organization members. BP: The definition summarizes long email discussions on the OBI developer, roles, biomaterial and denrie branches. It leaves open if an organization is a material entity or a dependent continuant, as no consensus was reached on that. The current placement as material is therefore temporary, in order to move forward with development. Here is the entire email summary, on which the definition is based: 1) there are organization_member_roles (president, treasurer, branch editor), with individual persons as bearers 2) there are organization_roles (employer, owner, vendor, patent holder) 3) an organization has a charter / rules / bylaws, which specify what roles there are, how they should be realized, and how to modify the charter/rules/bylaws themselves. It is debatable what the organization itself is (some kind of dependent continuant or an aggregate of people). This also determines who/what the bearer of organization_roles' are. My personal favorite is still to define organization as a kind of 'legal entity', but thinking it through leads to all kinds of questions that are clearly outside the scope of OBI. Interestingly enough, it does not seem to matter much where we place organization itself, as long as we can subclass it (University, Corporation, Government Agency, Hospital), instantiate it (Affymetrix, NCBI, NIH, ISO, W3C, University of Oklahoma), and have it play roles. This leads to my proposal: We define organization through the statements 1 - 3 above, but without an 'is a' statement for now. We can leave it in its current place in the is_a hierarchy (material entity) or move it up to 'continuant'. We leave further clarifications to BFO, and close this issue for now. PERSON: Alan Ruttenberg PERSON: Bjoern Peters PERSON: Philippe Rocca-Serra PERSON: Susanna Sansone GROUP: OBI organization organization OBI:0000471 study design execution a planned process that carries out a study design study design execution OBI:0200000 data transformation The application of a clustering protocol to microarray data or the application of a statistical testing method on a primary data set to determine a p-value. A planned process that produces output data from input data. Elisabetta Manduchi Helen Parkinson James Malone Melanie Courtot Philippe Rocca-Serra Richard Scheuermann Ryan Brinkman Tina Hernandez-Boussard data analysis data processing Branch editors data transformation OBI:0200111 data visualization Generation of a heatmap from a microarray dataset An planned process that creates images, diagrams or animations from the input data. Elisabetta Manduchi James Malone Melanie Courtot Tina Boussard data encoding as image visualization PERSON: Elisabetta Manduchi PERSON: James Malone PERSON: Melanie Courtot PERSON: Tina Boussard Possible future hierarchy might include this: information_encoding >data_encoding >>image_encoding data visualization OBI:0500000 study design A plan specification comprised of protocols (which may specify how and what kinds of data will be gathered) that are executed as part of an investigation and is realized during a study design execution. study design PATO:0000051 morphology A quality of a single physical entity inhering in the bearer by virtue of the bearer's size or shape or structure. morphology PATO:0000122 length A 1-D extent quality which is equal to the distance between two points. length PATO:0000125 mass A physical quality that inheres in a bearer by virtue of the proportion of the bearer's amount of matter. mass PATO:0001018 physical quality A quality of a physical entity that exists through action of continuants at the physical level of organisation in relation to other entities. physical quality PATO:0001241 physical object quality A quality which inheres in a continuant. physical object quality UO:0000001 length unit length unit UO:0000002 mass unit mass unit UO:0000003 time unit time unit swo:SWO_0000001 Computer software, or generally just software, is any set of machine-readable instructions (most often in the form of a computer program) that conform to a given syntax (sometimes referred to as a language) that is interpretable by a given processor and that directs a computer's processor to perform specific operations. James Malone Modified in parts from https://en.wikipedia.org/wiki/Software Robert Stevens software swo:SWO_0000002 A licence is a legal instrument (usually by way of contract law, with or without printed material) governing the use or redistribution of the resource containing the licence. Modified from http://en.wikipedia.org/wiki/Software_license James Malone licence software license swo:SWO_0000008 Racket is a Scheme-based language interpreter and programming environment Racket swo:SWO_0000012 Java swo:SWO_0000049 binning clustering method- The algorithm uses single-linkage clustering to join compounds into similarity groups, where every member in a cluster shares with at least one other member a similarity value above a user-specified threshold. The algorithm is optimized for speed and memory eciency by avoiding the calculation of an all-against-all distance matrix. Binning clustering method swo:SWO_0000083 This role can be borne by any software which is a plugin for another piece of software. It can be used, for example, with an axiom such as "ParentSoftware 'uses software' some (PluginSoftware has_role some Plugin)" Allyson Lister Plugin swo:SWO_0000084 CEL binary format is a binary data format specification created by Affymetrix where values are stored in little-endian format. The CEL format stores the results of the intensity calculations on the pixel values of the DAT file. This includes an intensity value, standard deviation of the intensity, the number of pixels used to calculate the intensity value, a flag to indicate an outlier as calculated by the algorithm and a user defined flag indicating the feature should be excluded from future analysis. The file stores the previously stated data for each feature on the probe array. http://www.affymetrix.com/support/developer/powertools/changelog/gcos-agcc/cel.html, accessed 22 May 2013. Allyson Lister It is unclear whether, originally, this format was intended to be the ASCII or binary version of the CEL format. As such, this class has been renamed as the binary format, and a new class created (CEL ASCII format) to make both options available. (22/05/2013) CEL binary format swo:SWO_0000091 http://dbpedia.org/resource/ActionScript ActionScript swo:SWO_0000092 http://dbpedia.org/resource/Ada_(programming_language) Ada swo:SWO_0000093 http://dbpedia.org/resource/AppleScript AppleScript swo:SWO_0000094 Assembly swo:SWO_0000095 http://dbpedia.org/resource/C_(programming_language) C swo:SWO_0000096 http://dbpedia.org/resource/C_Sharp_(programming_language) C Sharp swo:SWO_0000097 http://dbpedia.org/resource/C++ C++ swo:SWO_0000098 http://dbpedia.org/resource/COBOL COBOL swo:SWO_0000099 http://dbpedia.org/resource/ColdFusion_Markup_Language ColdFusion swo:SWO_0000100 http://dbpedia.org/resource/D_(programming_language) D swo:SWO_0000101 Delphi swo:SWO_0000102 http://dbpedia.org/resource/Dylan_(programming_language) Dylan swo:SWO_0000103 http://dbpedia.org/resource/Eiffel_(programming_language) Eiffel swo:SWO_0000104 http://dbpedia.org/resource/Forth_(programming_language) Forth swo:SWO_0000105 http://dbpedia.org/resource/Fortran Fortran swo:SWO_0000106 http://dbpedia.org/resource/Groovy_(programming_language) Groovy swo:SWO_0000107 http://dbpedia.org/resource/Haskell_(programming_language) Haskell swo:SWO_0000108 http://dbpedia.org/resource/JavaScript JavaScript swo:SWO_0000109 LabVIEW swo:SWO_0000110 http://dbpedia.org/resource/Lisp_(programming_language) Lisp swo:SWO_0000111 http://dbpedia.org/resource/Lua_(programming_language) Lua swo:SWO_0000112 Maple swo:SWO_0000113 Mathematica swo:SWO_0000114 http://dbpedia.org/resource/Pascal_(programming_language) Pascal swo:SWO_0000115 http://dbpedia.org/resource/Perl Perl swo:SWO_0000116 http://dbpedia.org/resource/PHP PHP swo:SWO_0000117 http://dbpedia.org/resource/Prolog Prolog swo:SWO_0000118 Python is a widely used general-purpose, high-level programming language. Its design philosophy emphasizes code readability, and its syntax allows programmers to express concepts in fewer lines of code than would be possible in languages such as C. The language provides constructs intended to enable clear programs on both a small and large scale.Python supports multiple programming paradigms, including object-oriented, imperative and functional programming or procedural styles. http://dbpedia.org/resource/Python_(programming_language), accessed 27 November 2014. Python swo:SWO_0000119 http://dbpedia.org/resource/REXX REXX swo:SWO_0000120 http://dbpedia.org/resource/Ruby_(programming_language) Ruby swo:SWO_0000121 SAS swo:SWO_0000122 http://dbpedia.org/resource/Scala_(programming_language) Scala swo:SWO_0000123 http://dbpedia.org/resource/Scheme_(programming_language) Scheme swo:SWO_0000124 Shell swo:SWO_0000125 http://dbpedia.org/resource/Smalltalk Smalltalk swo:SWO_0000126 http://dbpedia.org/resource/SQL SQL swo:SWO_0000127 http://dbpedia.org/resource/Turing_(programming_language) Turing swo:SWO_0000128 http://dbpedia.org/resource/Verilog Verilog swo:SWO_0000129 http://dbpedia.org/resource/VHDL VHDL swo:SWO_0000130 http://dbpedia.org/resource/Visual_Basic Visual Basic swo:SWO_0000134 MLXTRAN swo:SWO_0000136 NMTRAN swo:SWO_0000139 Web content search is the searching for information on the World Wide Web. website content search web content search swo:SWO_0000143 The storing of digital information. Often this is done for archiving and retrieval purposes. data storage swo:SWO_0000146 Version 2.6 of the Python programming language. Allyson Lister Allyson Lister Python 2.6 swo:SWO_0000147 Version 2.7 of the Python programming language. Allyson Lister Allyson Lister Python 2.7 swo:SWO_0000148 Firth's bias reduction procedure swo:SWO_0000159 GNU Octave is a high-level interpreted language, primarily intended for numerical computations. It provides capabilities for the numerical solution of linear and nonlinear problems, and for performing other numerical experiments. It also provides extensive graphics capabilities for data visualization and manipulation. Octave is normally used through its interactive command line interface, but it can also be used to write non-interactive programs. The Octave language is quite similar to Matlab so that most programs are easily portable. https://www.gnu.org/software/octave/, accessed 27 March 2015. Allyson Lister GNU Octave swo:SWO_0000160 GWT swo:SWO_0000161 S language swo:SWO_0000162 Excel swo:SWO_0000165 Modified version of the GLAD algorithm (Gain and Loss Analysis of DNA) swo:SWO_0000169 Gene Recommender algorithm swo:SWO_0000172 Gamma-Gamma hierarchical model swo:SWO_0000173 Gaussian locally weighted regression swo:SWO_0000174 Gene-Set Enrichment Analysis swo:SWO_0000212 Hexagon binning algorithm swo:SWO_0000215 Heterogeneous Error Model (HEM) swo:SWO_0000216 Hubert’s gamma swo:SWO_0000217 Hidden Markov Model swo:SWO_0000218 Hierarchical Ordered Partitioning and Collapsing Hybrid (HOPACH) algorithm swo:SWO_0000219 Technique which predicts a given transcription factor activity and then uses this infor- mation to predict its targets. Hidden Variable Dynamic Modelling HVDM) swo:SWO_0000220 HaarSeg algorithm swo:SWO_0000221 Hardy-Weinberg equilibrium swo:SWO_0000227 Hypergeometric probability swo:SWO_0000229 Iteratively ReWeighted Least Squares swo:SWO_0000233 ILLUMINA data swo:SWO_0000243 Jaccard’s index swo:SWO_0000249 KGML swo:SWO_0000250 'KLD' swo:SWO_0000251 KS measures how biased the ranks of a subset of items are among the ranks of the entire set Kolmogorov Smirnov rank-sum based algorithm swo:SWO_0000253 LC-MS data swo:SWO_0000255 Locally Moderated Weighted-t (LMW) method swo:SWO_0000256 Lognormal Normal Model swo:SWO_0000257 Lognormal Normal with Modied Variance Model swo:SWO_0000260 A publisher role is a role borne by an organization or individual in which they are responsible for making software available to a particular consumer group. Such organizations or individuals do need to be involved in the development of the software. James Malone publisher role swo:SWO_0000261 Langmuir Isotherm swo:SWO_0000262 Laplace mixture model swo:SWO_0000263 Library Search Algorithm swo:SWO_0000264 Loess algorithm swo:SWO_0000265 Logic regression swo:SWO_0000267 Median Average Difference Algorithm swo:SWO_0000270 MAQC data swo:SWO_0000274 MATLAB language swo:SWO_0000276 Multivariate correlation estimator swo:SWO_0000277 Markov Chain Monte Carlo swo:SWO_0000278 minimum common regions (MCR) algorithm- Minimal common regions (MCRs) are dened as contiguous spans having at least a recurrence rate dened by a parameter (recurrence) across samples. MCR algorithm swo:SWO_0000281 'MI' swo:SWO_0000282 Mutual information matrix (MIM) swo:SWO_0000284 MMD describes the distributions of gene expression levels directly via the marginal distributions. It includes EM algorithm, FDR, it is the percentage of nondifferentially expressed genes among selected genes), false non-discovery rate (denoted as FNDR; it is the percentage of differentially expressed genes among unselected genes),false positive rate (denoted as FPR; it is the percentage of selected genes among nondifferentially expressed genes), and false negative rate (denoted as FNR; it is the percentage of un-selected genes among differentially expressed genes), MMD swo:SWO_0000287 Mahalanobis distance swo:SWO_0000296 Misclassification-Penalized Posteriors (MiPP) swo:SWO_0000298 Mixed model equations swo:SWO_0000304 'Needleman-Wunsch' swo:SWO_0000305 This includes exhaustive enumeration, triple-based inference,pairwise heuristic, module based inference, greedy hillclimbing Nested Effects Models swo:SWO_0000306 Nonlinear Estimation by Iterative Partial Least Squares swo:SWO_0000313 Presence-Absence calls with Negative Probesets (PANP) swo:SWO_0000315 Pearson correlation estimator swo:SWO_0000318 it is where we fit a model with probe level and chip level parameters on a probeset by probeset basis 'PLM' swo:SWO_0000320 Probe level Locally moderated Weighted median-t (PLW) method swo:SWO_0000321 PPC algorithm swo:SWO_0000323 Included are summarisation, differential expression detection, clustering and PCA methods, together with useful plotting and data manipulation functions Propagation of uncertainty in microarray analysis swo:SWO_0000326 Power Law Global Error Model (PLGEM) analysis method swo:SWO_0000328 PLIER (Probe Logarithmic Error Intensity Estimate) method swo:SWO_0000332 Radial basis function swo:SWO_0000334 R interface to boost graph library algorithm (RBGL) swo:SWO_0000336 Random effects model swo:SWO_0000337 for the Support Vector Machine (SVM), as presented in [3] and the Nearest Shrunken Centroid (NSC) Recursive Feature Elimination (RFE) swo:SWO_0000339 Regression model swo:SWO_0000340 RMA swo:SWO_0000341 RMA+ swo:SWO_0000342 RMA++ swo:SWO_0000363 Rnw swo:SWO_0000364 Robust likelihood-based survival modeling swo:SWO_0000371 S-Score algorithm swo:SWO_0000372 Serial Analysis of Gene Expression (SAGE) swo:SWO_0000374 Note: It is unclear from just the label what is meant by a SAM algorithm. It may or may not be related to the SAM sequence alignment software described by the class SWO_0000077 (Allyson Lister) SAM swo:SWO_0000378 SBMLR format swo:SWO_0000381 SDF format swo:SWO_0000386 SNPRMA algorithm swo:SWO_0000389 Semantic Similarity Measures- Four methods proposed by Resnik[Philip, 1999], Jiang[Jiang and Conrath, 1997], Lin[Lin, 1998] and Schlicker[Schlicker et al., 2006] respectively have presented to determine the semantic similarities of two GO terms based on the annotation statistics of their common ancestor terms. Wang [Wang et al., 2007] proposed a new method to measure the similarities based on the graph structure of GO. Semantic Similarity Measures swo:SWO_0000391 SVDimpute algorithm swo:SWO_0000392 Software developer role is a role borne by an organization or individual in which they are responsible for authoring software. James Malone software developer role swo:SWO_0000396 An organization or legal entity (including single person) that is responsible for developing software. Developing includes aspects of design, coding and testing. software developer organization swo:SWO_0000397 An organization or legal entity (including single person) that is responsible for publishing software. Publishing here includes tasks such as designing and producing physical products, technical customer support, licensing arrangements and marketing. software publisher organization swo:SWO_0000398 Classical multivariate analysis-of-variance tests perform poorly in cases with several highly correlated responses and the tests collapse when the number of responses exceeds the number of observations. This paper presents a new method which handles this problem. The dimensionality of the data is reduced by using principal component decompositions and the final tests are still based on the classical test statistics and their distributions. The methodology is illustrated with an example from the production of sausages with responses from near infrared reflectance spectroscopy. A closely related method for testing relationships in uniresponse regression with collinear explanatory variables is also presented. The new test, which is called the 50-50 F-test, uses the first k components to calculate SSMODEL. The next d components are not involved in SSERROR and they are called buffer components. Langsrud, &Oslash. (2002), 50-50 Multivariate Analysis of Variance for Collinear Responses, The Statistician, 51, 305-317. 50-50 MANOVA algorithm swo:SWO_0000406 Gene list swo:SWO_0000408 Clustered data set swo:SWO_0000409 R data frame swo:SWO_0000415 R language swo:SWO_0000423 Signaling Pathway Impact Analysis (SPIA) algorithm swo:SWO_0000425 Similarity score swo:SWO_0000426 'Smith-Waterman' swo:SWO_0000437 Theodore Ts’o’s swo:SWO_0000441 Variance-stabilizing transformation (VST) algorithm swo:SWO_0000444 WilcEbam swo:SWO_0000445 Wilcoxon swo:SWO_0000449 Xba.CQV and Xba.regions swo:SWO_0000467 data annotation swo:SWO_0000469 Annotation data packages swo:SWO_0000477 Associative T method swo:SWO_0000478 AvgNRRs swo:SWO_0000484 Bitmap object swo:SWO_0000490 Bootstrap swo:SWO_0000493 cdt swo:SWO_0000497 chamber slide format swo:SWO_0000498 Categorical (e.g tumor vs normal) class file format http://www.broadinstitute.org/cancer/software/gsea/wiki/index.php/Data_formats#CLS:_Categorical_.28e.g_tumor_vs_normal.29_class_file_format_.28.2A.cls.29 cls swo:SWO_0000502 dataset comparison swo:SWO_0000503 Concordance swo:SWO_0000508 covdesc file swo:SWO_0000509 An objective in which the aim is to create a new database instance. PERSON: James Malone James Malone database creation swo:SWO_0000516 .data swo:SWO_0000518 debian control file format dcf swo:SWO_0000519 design file swo:SWO_0000524 Dynamic programming algorithm swo:SWO_0000531 f-test swo:SWO_0000548 Gene Cluster Text file format http://www.broadinstitute.org/cancer/software/gsea/wiki/index.php/Data_formats#GCT:_Gene_Cluster_Text_file_format_.28.2A.gct.29 gct swo:SWO_0000552 Gene array analysis algorithm swo:SWO_0000553 gene expression analysis swo:SWO_0000554 Gene expression dataset swo:SWO_0000560 global test allows the unit of analysis of the microarray experiment to be shifted from the single gene level to the pathway level, where a ‘pathway’ may be any set of genes, e.g. chosen using the Gene Ontology database or from earlier experiments. Global test swo:SWO_0000562 gmt format swo:SWO_0000566 GenePix Pro Results file format gpr format swo:SWO_0000569 gtr swo:SWO_0000570 gxl format swo:SWO_0000573 Hierarchical clustering swo:SWO_0000575 HTML report swo:SWO_0000576 Hypergeometric enrichment swo:SWO_0000584 Iterative local regression and model selection swo:SWO_0000587 k-cores swo:SWO_0000588 k-means swo:SWO_0000589 k-nearest neighbour classification swo:SWO_0000592 Likelihood method swo:SWO_0000595 Linear modelling swo:SWO_0000596 lma swo:SWO_0000597 Local-pooled-error swo:SWO_0000598 log file swo:SWO_0000600 logicFS dataset swo:SWO_0000602 Logit-t algorithm swo:SWO_0000614 'MAS5' swo:SWO_0000615 mas5 format swo:SWO_0000618 M-estimation regression swo:SWO_0000620 Meta data swo:SWO_0000626 mrnet algorithm swo:SWO_0000627 Multinomial probit regression with Gaussian Process priors swo:SWO_0000628 multiple testing which includes controlling the family-wise error rate (FWER), generalized family-wise error rate (gFWER), tail probability of the proportion of false positives (TPPFP), and false discovery rate (FDR). Tests based on a variety of t- and F-statistics (including t-statistics based on regression parameters from linear and survival models as well as those based on correlation parameters) are included. Multiple testing swo:SWO_0000629 Multivariate t mixture models swo:SWO_0000631 Negative binomial distribution swo:SWO_0000633 Neural networks models swo:SWO_0000640 OMICS data swo:SWO_0000644 pair file swo:SWO_0000648 parse swo:SWO_0000655 pedigree data file swo:SWO_0000661 Graph plot swo:SWO_0000664 Position weight matrix (PWM ) swo:SWO_0000670 qPCR data swo:SWO_0000673 Quantile normalization swo:SWO_0000674 Quantile regression techniques swo:SWO_0000680 Rank-invariant set normalization swo:SWO_0000681 Rank product non-parametric method swo:SWO_0000682 .raw files swo:SWO_0000684 rda swo:SWO_0000687 .rma format swo:SWO_0000695 Sim method swo:SWO_0000708 sproc swo:SWO_0000709 sqlite swo:SWO_0000713 A statistical test is an algorithm for making quantitative decisions to determine which outcomes of a study would lead to a rejection of the null hypothesis for a pre-specified level of significance. Modified from http://en.wikipedia.org/wiki/Statistical_test, accessed 9 May 2013; http://www.itl.nist.gov/div898/handbook/prc/section1/prc13.htm, accessed 9 May 2013. Statistical tests swo:SWO_0000715 't-test' swo:SWO_0000722 Two-stage measurement error model swo:SWO_1100000 2-sample pooled t-test swo:SWO_1100003 The ACME algorithm is quite straightforward. Using a user-dened quantile of the data,called the threshold, any probes in the data that are above that threshold are considered positive probes. A p-value is then assigned to each probe. 'ACME' swo:SWO_1100007 Average log expression across arrays (ALE) swo:SWO_1100008 ALL/AML data set swo:SWO_1100009 AMDIS swo:SWO_1100010 The ANCOVA global test is a test for the association between expression values and clinical entities. The test is carried out by comparison of linear models via the extra sum of squares principle. If the mean expression level for at least one gene diers between corresponding models the global null hypothesis, which is the intersection of all single gene null hypotheses, is violated. FDR ANCOVA swo:SWO_1100011 ANOVA or Analysis of Variance is a hypothesis testing algorithm which a variable is partitioned into components attributable to different sources of variation. ANNOVA 'ANOVA' swo:SWO_1100012 AP-MS data swo:SWO_1100013 ARACNE algorithm swo:SWO_1100014 ARR swo:SWO_1100015 AWS algorithm swo:SWO_1100030 BGL implements Depth First Search, Breadth First Search,Dijkstra's, Bellman Ford's and DAG,Johnson's and Floyd Warshall's.Kruskal's algorithm and Prim's algorithm Cuthill-McKee's algorithm Minimum degree Ordering BGL swo:SWO_1100033 Iterative Bayesian Model Averaging (BMA) swo:SWO_1100034 Base-Pair-Distance Kernel swo:SWO_1100035 BPMAP is a binary data format specification created by Affymetrix where the data is stored in big-endian format. The BPMAP format contains information relating to the design of the Affymetrix tiling arrays. http://www.affymetrix.com/support/developer/powertools/changelog/gcos-agcc/bpmap.html, accessed 22 May 2013. Allyson Lister BPMAP swo:SWO_1100039 BaldiLongT swo:SWO_1100041 Bayesian Model swo:SWO_1100054 The CDF binary format is a binary data format specification created by Affymetrix was created for faster access and smaller file size in comparison to the CDF ASCII format. The values in the file are stored in little-endian format. CDF binary format describes the layout for an Affymetrix GeneChip array. An array may contain Expression, Genotyping, CustomSeq, Copy Number and/or Tag probe sets. All probe set names within an array are unique. Multiple copies of a probe set may exist on a single array as long as each copy has a unique name. http://www.affymetrix.com/support/developer/powertools/changelog/gcos-agcc/cdf.html, accessed 22 May 2013. It is unclear whether, originally, this format was intended to be the ASCII or binary version of the CDF format. As such, this class has been renamed as the binary format, and a new class created (CDF ASCII format) to make both options available. CDF binary format swo:SWO_1100056 CMA- it implements k-fold cross validation, MCMC cross validation, bootstrap and (t.test or welch.test or wilcox.test or f.test or kruskal.test or One-step Recursive Feature Elimination or random forest variable importance measure or lasso or elastic net or componentwise boosting) CMA swo:SWO_1100058 This algorithm offers improved confidence scores, quality scores for SNP’s and batches, higher accuracy on different datasets and better performance. CRLMM algorithm swo:SWO_1100059 Continuous Wavelet Transform (CWT)-based peak detection algorithm swo:SWO_1100061 Category analysis swo:SWO_1100070 PCMG- a bipartite graph in which one set of nodes represents proteins, the other set represents complexes, and an edge from a protein node to a complex node represents membership of the protein in that complex. PCMG swo:SWO_1100072 Chi-square swo:SWO_1100074 distance calculation swo:SWO_1100076 BCRANK is a method that takes a ranked list of genomic regions as input and outputs short DNA sequences that are overrepresented in some part of the list. BCRANK swo:SWO_1100077 cosmo allows the user to target the motif search by specifying a set of constraints that the unknown position weight matrix must satisfy. The algorithm is based on a probabilistic model that describes the DNA sequences of interest through a two- component multinomial mixture model with estimates of the position weight matrix entries obtained by maximizing the observed data likelihood over the smaller parameter space corresponding to the imposed constraints. It includes methods such as Probabilistic models and one-occurrence-per-sequence and zero-or-one-occurrence-per-sequence and two-component mixture Cosmo swo:SWO_1100078 F test swo:SWO_1100080 Text data set swo:SWO_1100081 CSV data set swo:SWO_1100082 non-linear functional regression model with both additive and multiplicative error terms Non-linear functional regression model swo:SWO_1100086 Complex Estimation Algorithm swo:SWO_1100090 A DFP version of a FP (fuzzy pattern) only includes those genes that can serve to differentiate it from the rest of the patterns.This algorithm is based on the discretization of float values (gene expression values) stored in an ExpressionSet object into labels combining 'Low', 'Medium' and 'High' Discriminant Fuzzy Pattern Algorithm swo:SWO_1100091 DFW swo:SWO_1100092 Digital gene expression (DGE) datasets swo:SWO_1100096 Expectation-Maximization(EM) algorithm swo:SWO_1100097 Empirical Bayes rule swo:SWO_1100099 FACS data is data which describes flow cytometry data sets. http://www.bioconductor.org/packages/2.12/bioc/vignettes/prada/inst/doc/fcs3.html, accessed 29 May 2013. Allyson Lister FACS data swo:SWO_1100100 FARMS swo:SWO_1100101 FC swo:SWO_1100102 'FDR' swo:SWO_1100103 Fixed effect model swo:SWO_1100105 Fischer's Exact Test swo:SWO_1100107 GASSCO method swo:SWO_1100110 GEO data type swo:SWO_1100114 Gamma Gamma Model swo:SWO_1100117 The circular binary segmentation (CBS) algorithm divides the genome into regions of equal copy number . The algorithm tests for change-points using a maximal t-statistic with a permutation reference distribution to obtain the corresponding p-value. The number of computations required for the maximal test statistic is O(N^2),where N is the number of markers. This makes the full permutation approach computationally prohibitive for the newer arrays that contain tens of thousands markers and highlights the need for a faster algorithm. CBS swo:SWO_1100118 CBS algorithm swo:SWO_1100122 CHP binary format is a binary data format specification created by Affymetrix, stored in little-endian format and used to store expression, resequencing and genotyping results from algorithms implemented in the GCOS 1.2, 1.3 and 1.4 and BRLMM Analysis Tool software applications. http://www.affymetrix.com/support/developer/powertools/changelog/gcos-agcc/chp.html, http://www.affymetrix.com/support/developer/powertools/changelog/gcos-agcc/chp-xda.html, accessed 22 May 2013. Allyson Lister As this is a child of Binary format, it is assumed that this class is intended to represent the binary form of this format. As described in the definition sources, there are other formats for CHP available. CHP binary format swo:SWO_1100123 CLR algorithm swo:SWO_1100125 FoxDimmicT swo:SWO_1100126 GEO Matrix Series format swo:SWO_9000005 A licence clause is a component of a licence which defines some aspect of a restriction or conversely permission in how something corresponding to a licence may be legally redistributed, partially redistrubed, extended, modified or otherwise used in some way. James Malone clause licence clause swo:SWO_9000006 An Attribution clause is a license clause intended to provide a specified level of recognition of the licensor as the copyright holder of the work. This can take many forms, including the requirement to preserve any copyright notice, attribution statements and the URL (link) to the original work. The attribution requirement thus serves the dual purpose of ensuring that the publisher receives appropriate credit, and that provenance information is kept intact. There are varying strengths of these clauses, from licensors requesting not to be attributed at all to requiring attribution for all uses of the resource. Modified by Allyson Lister from http://creativecommons.org/tag/attribution Attribution clause swo:SWO_9000007 Derivatives clauses are license clauses which state what requirements on derivative resource, if any, are attached to a license. The license for a resource may or may not allow the creation of new resources derived from it. If it is allowed, such usage may be restricted in a variety of ways. Allyson Lister Derivatives clause swo:SWO_9000008 A source code clause is a license clause which states the restrictions placed on the source code for the licensed software, if any. The license for a piece of software may or may not allow access to the source code. If such access is allowed, usage may be restricted in a variety of ways. Allyson Lister Source code clause swo:SWO_9000009 A Platform clause is a license clause which states the platform restrictions for the licensed resource, if any. The license for a resource may or may not allow the use of any platform. If it is allowed, such usage may be restricted in a variety of ways. Allyson Lister Platform clause swo:SWO_9000010 A Number of installations clause is a license clause which may limit the number of installations a particular licensee may peform. Allyson Lister Number of installations clause swo:SWO_9000011 A Number of users clause is a license clause which may limit the number of users a particular licensee may allow to use the resource. Allyson Lister Number of users clause swo:SWO_9000012 A time clause is a license clause which states the restrictions placed on the length of time the licensed resource may be used, if any. The license for a resource may or may not allow access to the resource for an unlimited time. If such access is allowed, usage may be restricted in a variety of ways. Allyson Lister Time clause swo:SWO_9000013 A usage clause is a license clause which states the restrictions placed on how the licensed resource may be used. The license for a resource may restrict how the licensee may use the software. If such access is allowed, usage may be restricted in a variety of ways. Allyson Lister Usage clause swo:SWO_9000016 No restrictions on derivatives is a derivatives clause which places no rules or restrictions on how derivative software is created. Allyson Lister No restrictions on derivatives swo:SWO_9000017 Restrictions on derivative software is a derivatives clause which allows the creation of derivatives but which also places some kind of restriction on how derivative software may be created. Allyson Lister Restrictions on derivative software swo:SWO_9000018 Derivatives not allowed clauses are derivatives clauses which state that derivative resources are never allowed using the licensed resource. Allyson Lister Derivatives not allowed swo:SWO_9000019 Derivative code same license is a restrictive derivatives clause where derivative software must be released under the same license. Allyson Lister derivative code same license swo:SWO_9000020 A source code available clause is a source code clause which states that the source code for the licensed software is available to the licensee. However, usage of the source code may or may not be restricted in a variety of ways. Allyson Lister Source code available swo:SWO_9000021 A source code unavailable clause is a source code clause which states that the source code for the licensed software is not available to the licensee. Allyson Lister Source code unavailable swo:SWO_9000022 Platform restricted is a platform clause which places restrictions on which platform the licensed resource may be installed on. Allyson Lister Platform restricted swo:SWO_9000023 Platform unrestrictred is a platform clause which does not place any restrictions on which type of platform the resource may be licensed for. Allyson Lister Platform unrestricted swo:SWO_9000024 A Number of installations restricted clause is a number of installations clause which restricts the number of times the resource may be installed by any given licensee. Allyson Lister Number of installations restricted swo:SWO_9000025 A Number of installations unrestricted clause is a number of installations clause which does not restrict the number of times the resource may be installed by any given licensee. Allyson Lister Number of installations unrestricted swo:SWO_9000026 A Number of users restricted clause is a number of users clause which restricts the number of users the resource may have for a particular licensee. This may be number of total users, or number of concurrent users. Allyson Lister Number of users restricted swo:SWO_9000027 A Number of users unrestricted clause is a number of users clause which does not restrict the number of users of the licensed resource. Allyson Lister Number of users unrestricted swo:SWO_9000028 Time for use restricted is a time clause which places restrictions on the length of time the licensed resource may be used. Allyson Lister Time for use restricted swo:SWO_9000029 Time for use unrestrictred is a time clause which does not place any restrictions on the length of time the resource may be licensed for. Time for use unrestricted swo:SWO_9000030 Usage unrestricted is a usage clause which places no restrictions on how the licensed resource may be used. Allyson Lister Usage unrestricted swo:SWO_9000031 Usage restricted is a usage clause which places restrictions on how the licensed resource may be used. These restrictions will vary according to the individual license. Allyson Lister Usage restricted swo:SWO_9000032 Non-commercial use only is a usage restricted clause which restricts the use of the licensed resource only to licensees who are not commercial entites. Non-commercial use only swo:SWO_9000033 Academic use only is a usage restricted clause which restricts the use of the licensed resource to academic licensees only. Allyson Lister Academic use only swo:SWO_9000034 Derivative code linked same license is a restrictive derivatives clause where code may only be linked to in derivative software that is released under the same license. Allyson Lister derivative code linked same license swo:SWO_9000050 The mode of interaction with a piece of software. software interface A stochastic algorithm for population pharmacology modeling http://www.math.u-bordeaux1.fr/MAS10/DOC/PDF-PRES/Lavielle.pdf SAEM A Dynamic Bayesian Network model is a Bayesian Network which relates variables to each other over adjacent time steps. http://en.wikipedia.org/wiki/Dynamic_Bayesian_network, accessed 27 November 2014. dynamic Bayesian network model In mathematics, an ordinary differential equation or ODE is an equation containing a function of one independent variable and its derivatives. The term "ordinary" is used in contrast with the term partial differential equation which may be with respect to more than one independent variable. Ordinary Differential Equation Algorithm http://en.wikipedia.org/wiki/Ordinary_differential_equation, accessed 25 March 2015. Allyson Lister ODE Algorithm Gillespie's Stochastic Simulation Algorithm is an algorithm which generates a statistically correct trajectory (possible solution) of a stochastic equation. It can be used to simulate chemical or biochemical systems of reactions efficiently and accurately using limited computational power. The algorithm is particularly useful for simulating reactions within cells where the number of reagents typically number in the tens of molecules (or less). Mathematically, it is a variety of a dynamic Monte Carlo method and similar to the kinetic Monte Carlo methods. It is used heavily in computational systems biology http://en.wikipedia.org/wiki/Gillespie_algorithm, accessed 25 March 2015. Allyson Lister Gillespie's Stochastic Simulation Algorithm Monte Carlo is a discrete stochastic simulation algorithm and an estimation procedure algorithm. If it is necessary to know the average value of some random variable and its distribution can not be stated, and if it is possible to take samples from the distribution, we can estimate it by taking the samples, independently, and averaging them. If there are sufficiently enough samples, then the law of large numbers says the average must be close to the true value. The central limit theorem says that the average has a Gaussian distribution around the true value. http://en.wikipedia.org/wiki/Stochastic_simulation#Monte_Carlo_simulation, accessed 25 March 2015, and http://www.async.ece.utah.edu/iBioSim/docs/iBioSim.html, accessed 25 March 2015. Allyson Lister Monte Carlo Differential Algebraic equations (DAEs) are a general form of (systems of) differential equations for vector–valued functions in one independent variable. In practical terms, the distinction between DAEs and ODEs is often that the solution of a DAE system depends on the derivatives of the input signal and not just the signal itself as in the case of ODEs. Differential Algebraic Equation Algorithm http://en.wikipedia.org/wiki/Differential_algebraic_equation, accessed 26 March 2015. Allyson Lister DAE Algorithm A partial differential equation (PDE) is a differential equation that contains unknown multivariable functions and their partial derivatives. This is in contrast to ordinary differential equations, which deal with functions of a single variable and their derivatives. Partial Differential Equation Algorithm http://en.wikipedia.org/wiki/Partial_differential_equation, accessed 26 March 2015. Allyson Lister PDE Algorithm A spreadsheet data format is one in which data is organised into a matrix (or matrices) of columns and rows to form cells in which values are entered. James Malone spreadsheet format A spreadsheet data format designed for Microsoft Excel. James Malone XLS spreadsheet A spreadsheet data format in which the structure of the data is described using XML, such as column and row headers and cell identity. James Malone XML spreadsheet James Malone Matlab .m file "Resource Description Framework (RDF) format." [http://edamontology.org] format bioinformatics edam formats The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web. http://www.w3.org/TR/REC-rdf-syntax/ James Malone Jon Ison Data in RDF format can be serialised into XML, textual, or binary format. Merged with now-obsolete EDAM class 'RDF' http://edamontology.org/format_2376 by Allyson Lister. RDF A serialisation of RDF into an XML format. James Malone RDF-XML image format DWG ("drawing") is a binary file format used for storing two and three dimensional design data and metadata http://en.wikipedia.org/wiki/.dwg James Malone DWG DXF (Drawing Interchange Format, or Drawing Exchange Format) is a CAD data file format developed by Autodesk for enabling data interoperability between AutoCAD and other programs. http://en.wikipedia.org/wiki/AutoCAD_DXF James Malone DXF The BMP File Format is a Raster graphics image file format used to store bitmap digital images, independently of the display device (such as a graphics adapter). http://www.fileformat.info/format/bmp/egff.htm James Malone BMP Computer Graphics Metafile (CGM) is a free and open international standard file format for 2D vector graphics, raster graphics, and text, and is defined by ISO/IEC 8632. http://en.wikipedia.org/wiki/Computer_Graphics_Metafile James Malone CGM web page specification document exchange format PDF is an open standard for document exchange. Portable Document Format pdf TIFF is a flexible, adaptable file format for handling images and data within a single file, by including the header tags (size, definition, image-data arrangement, applied image compression) defining the image's geometry. Tagged Image File Format TIFF JPEG is a lossy file format for storing images JPG JPEG PNG is a bitmapped image format and video codec that employs lossless data compression. Portable Network Graphics PNG The Graphics Interchange Format (GIF) is a bitmap image format. The format supports up to 8 bits per pixel thus allowing a single image to reference a palette of up to 256 distinct colors. The colors are chosen from the 24-bit RGB color space. It also supports animations and allows a separate palette of 256 colors for each frame. The color limitation makes the GIF format unsuitable for reproducing color photographs and other images with continuous color, but it is well-suited for simpler images such as graphics or logos with solid areas of color. [wikipedia] Graphics Interchange Format GIF A raster image is a format for representing a rectangular grid of dots (pixels) which contains information on the specific colour of each pixel. raster image format A vector image is a collection of connected lines and curves that produce objects. This geometric description enables the image to be displayed without loss at any size rendering. vector image format Scalable Vector Graphics SVG Adobe Illustrator format AI PostScript is a format used for describing documents. PostScript tex is a format for documents written in the document markup language and document preparation system LaTeX. LaTeX format tex A format specification for data used or produced by outliner software outline document format A proprietary format for documents created and edited using OmniOutliner outliner software, OmniOutline format OPML (Outline Processor Markup Language) is an XML format for outlines Outline Processor Markup Language OPML JPEG 2000 is a compression standard enabling both lossless and lossy storage. The compression methods used are different from the ones in standard JFIF/JPEG; they improve quality and compression ratios, but also require more computational power to process. [wikipedia] JPEG 2000 word processing document format WordStar format A file format for word processing documents for Microsoft Word. Microsoft Word doc programming language format A source code file format which is specified to be used with the Java programming language. James Malone .java file A format in which a .java file has been compiled into bytecode using a Java compiler and which is specified to be executed using the Java virtual machine. James Malone .class file The Web Ontology Language (OWL) in XML serialization OWL-XML Web Ontology Language version 2 in XML Serialization OWL2-XML ASCII format plain text file format Tab delimited file format is a plain text file format where each field value of a record is separated from the next by a tab stop character. http://en.wikipedia.org/wiki/Tab-separated_values, accessed 6 June 2013. Allyson Lister tab delimited file format SIF stands for Simple Interaction Format, and is a text format invented for Cytoscape. If the file contains any tab characters, then tabs are used to delimit the fields and spaces are considered part of the name. If the file contains no tabs, then any spaces are delimiters that separate names (and names cannot contain spaces). http://wiki.cytoscape.org/GettingStarted and http://wiki.cytoscape.org/Cytoscape_User_Manual/Network_Formats, accessed 20 June 2012 Allyson Lister SIF GML stands for Graph Markup Language, and is a standard network file format; supported by multiple generic network software packages http://wiki.cytoscape.org/GettingStarted, accessed 20 June 2012 GML XGMML stands for eXtensible Graph Markup and Modelling Language, and it is a XML standard; similar to but preferred over GML. http://wiki.cytoscape.org/GettingStarted, accessed 20 June 2012 XGMML A type of data which defines interactions between items in the file. This can be simple pairwise interactions or more complex ones. Used to provide a class of data for software requiring specific types of interaction data as input. Allyson Lister Interaction data A knowledge representation role is a role borne by a data format which utilizes formalisms to make complex systems easier to design and build. Knowledge representation is the field of artificial intelligence devoted to representing information about the world in a form that a computer system can utilize to solve complex tasks. Modified from http://en.wikipedia.org/wiki/Knowledge_representation, accessed 10 February 2014 Knowledge representation role The CDF ASCII format is an ASCII data format specification created by Affymetrix similar to the Windows INI format. This format describes the layout for an Affymetrix GeneChip array. An array may contain Expression, Genotyping, CustomSeq, Copy Number and/or Tag probe sets. All probe set names within an array are unique. Multiple copies of a probe set may exist on a single array as long as each copy has a unique name. http://www.affymetrix.com/support/developer/powertools/changelog/gcos-agcc/cdf.html, accessed 22 May 2013 Allyson Lister CDF ASCII format BAR is a binary data format specification created by Affymetrix where the data is stored in big-endian format. The format of the file is a header section followed by sequences sections (one section per sequence defined). The BAR file contains one and two sample analysis results (signal and p-values) from the tiling array software. http://www.affymetrix.com/support/developer/powertools/changelog/gcos-agcc/bar.html, accessed 22 May 2013. Allyson Lister BAR CEL ASCII format is ASCII data format specification created by Affymetrix similar to the Windows INI format. The CEL format stores the results of the intensity calculations on the pixel values of the DAT file. This includes an intensity value, standard deviation of the intensity, the number of pixels used to calculate the intensity value, a flag to indicate an outlier as calculated by the algorithm and a user defined flag indicating the feature should be excluded from future analysis. The file stores the previously stated data for each feature on the probe array. http://www.affymetrix.com/support/developer/powertools/changelog/gcos-agcc/cel.html, accessed 22 May 2013. Allyson Lister CEL ASCII format Affymetrix-compliant data is data produced in a format compatible with Affymetrix software. This is a defined class where other data classes will be inferred to be members if they have a data format specification which has been published by Affymetrix. Allyson Lister Affymetrix-compliant data The flow cytometry data file standard provides the specifications needed to completely describe flow cytometry data sets within the confines of the file containing the experimental data. The principal goal of the Standard is to provide a uniform file format allowing files created by one type of acquisition hardware and software to be analyzed by another type. FCS http://www.bioconductor.org/packages/2.12/bioc/vignettes/prada/inst/doc/fcs3.html, accessed May 29. 2013. Allyson Lister Data File Standard for Flow Cytometry FCS3.0 is version 3.0 of the Data File Standard for Flow Cytometry. It contains a mechanism for handling data sets of 100 megabytes and larger, support for UNICODE text for keyword values, support for cyclic redundancy check (CRC) validation for each data set, a requirement for the inclusion of information describing the method of signal amplification and increased support for the inclusion of time as a measurement parameter. http://www.bioconductor.org/packages/2.12/bioc/vignettes/prada/inst/doc/fcs3.html, accessed May 29. 2013. Allyson Lister FCS3.0 NONMEM data format A nucleic acid sequence that indicate the order of nucleotides within some DNA. DNA nucleotide sequence Data about primary biological sequence information, such as DNA neucleotide sequences. biological sequence data Data which contains information about amino acid sequences of proteins. amino acid protein sequence data sequence feature format Tabix indexes a TAB-delimited genome position file and creates an index file when region is absent from the command-line. The input data file must be position sorted and compressed by bgzip which has a gzip like interface. After indexing, tabix is able to quickly retrieve data lines overlapping regions specified in the format "chr:beginPos-endPos". Fast data retrieval also works over network if URI is given as a file name and in this case the index file will be downloaded if it is not present locally. http://samtools.sourceforge.net/tabix.shtml tabix file format Genomedata provides a way to store and access large-scale functional genomics data in a format which is both space-efficient and allows efficient random-access. Genomedata archives are implemented as one or more HDF5 files, either as single files or as directory archives. HDF5 archives are self describing, like XML, but may also contain more complex structures such contain binary data. http://pmgenomics.ca/hoffmanlab/proj/genomedata/doc/1.3.5/genomedata.html and http://www.hdfgroup.org/why_hdf/, accessed 27 November 2014. Allyson Lister genomedata format The bedGraph format is a line-oriented text file format. Bedgraph data are preceeded by a track definition line, which adds a number of options for controlling the default display of this track. Following the track definition line are the track data in four column BED format. The bedGraph format allows display of continuous-valued data in track format. This display type is useful for probability scores and transcriptome data. This track type is similar to the wiggle (WIG) format, but unlike the wiggle format, data exported in the bedGraph format are preserved in their original state. http://genome.ucsc.edu/goldenpath/help/bedgraph.html, accessed December 3, 2014. Allyson Lister BedGraph GMTK parameter data is a type of data which contains the various parameter files required by GMTK to define a dynamic Bayesian network. These parameter files come in multiple types (e.g. structure files and master files), and therefore this is a data type rather than a single format. Graphical Models Toolkit parameter data Allyson Lister http://noble.gs.washington.edu/proj/philius/README, accessed 3 December 2014. Allyson Lister GMTK parameter data These parameter files come in multiple types (e.g. structure files and master files), and therefore this is a data type rather than a single format. MathML 2.0 is an XML format which is a low-level specification for describing mathematics as a basis for machine to machine communication. It is a W3C Recommendation and was released on 21 Feb 2001. A product of the W3C Math working group, it provides a much needed foundation for the inclusion of mathematical expressions in Web pages. http://www.w3.org/Math/ Allyson Lister James Malone MathML 2.0 FieldML is an XML-based language for describing time-varying and spatially-varying fields. The aims of the language design process are to keep the language concise, consistent, intuitive and flexible. http://www.physiomeproject.org/xml_languages/fieldml James Malone FieldML WKn is a collective name for a spreadsheet format created for Lotus 1-2-3. http://support.sas.com/documentation/cdl/en/acpcref/63184/HTML/default/viewer.htm#a003103772.htm and http://en.wikipedia.org/wiki/Lotus_1-2-3, accessed 3 December 2014. Allyson Lister Please note that this is a collective class for all versions of the WKn format, and the specific version required should be created as necessary and placed as a child of this class. WKn GZipped format .gz Zipped format .zip audio format Resource Interchange File Format RIFF BigWig format .bw Comma-separated value format .csv MASCOT generic format .mgf MySQL format .mysql SQL format .sql A Web User interface is a Graphical User Interface which is loaded and run via a Web browser rather than within the user's operating system. WUI Web UI Allyson Lister web user interface A Desktop Graphical User interface is a Graphical User Interface which is loaded and run within the user's operating system rather than via a Web browser. Desktop GUI Allyson Lister desktop graphical user interface A SOAP service is a Web service which provides a standard, extensible, composable framework for packaging and exchanging XML messages. The service may expose an arbitrary, application-specific set of operations. SOAP Service Modified from http://en.wikipedia.org/wiki/SOAP, accessed 6 June 2013; modified from http://www.w3.org/TR/ws-arch, accessed 6 June 2013. Allyson Lister SOAP service A REST service is a Web service in which the primary purpose of the service is to manipulate XML representations of Web resources using a uniform set of "stateless" operations. RESTful APIs do not require XML-based web service protocols (SOAP and WSDL) to support their light-weight interfaces. REST Service Modified from http://www.w3.org/TR/ws-arch, accessed 6 June 2013, Modified from http://en.wikipedia.org/wiki/Web_service, accessed 6 June 2013. Allyson Lister REST service A web service in which calls invoked return JSON. JSON web service A web service is a software interface which works as a method of communication between two electronic devices over the World Wide Web and which is provided at a particular network address. There are two major classes of Web services: REST-compliant Web services, and arbitrary (or application-specific) Web services. Web Service Modified from http://www.w3.org/TR/ws-arch/, accessed 6 June 2013; Modified from http://en.wikipedia.org/wiki/Web_service, accessed 6 June 2013. Allyson Lister web service A Graphical user interface is a type of software interface that allows users to interact with electronic devices using images rather than text commands. A GUI represents the information and actions available to a user through graphical icons and visual indicators such as secondary notation, as opposed to text-based interfaces, typed command labels or text navigation. https://en.wikipedia.org/wiki/Graphical_user_interface, accessed 6 June 2013. GUI Allyson Lister graphical user interface A command-line interface is a means of interacting with a computer program where the user (or client) issues commands to the program in the form of successive lines of text (command lines). Command line Command line interface Command-line http://en.wikipedia.org/wiki/Command-line_interface, accessed 25 November 2014. command-line interface An application programming interface is a set of routines, protocols, and tools for building software applications. An API expresses a software component in terms of its operations, inputs, outputs, and underlying types. An API defines functionalities that are independent of their respective implementations, which allows definitions and implementations to vary without compromising each other. The API specifies how software components should interact. API http://en.wikipedia.org/wiki/Application_programming_interface, accessed 25 November 2014. application programming interface CC Creative Commons Proprietary commercial software license Mozilla Public License Version 1.1 MPL v1.1 Distribution clauses are license clauses which state the requirements on how the licensed resource is redistributed. The license for a resource may or may not allow the redistribution of that resource. If it is allowed, such usage may be restricted in a variety of ways. Allyson Lister Distribution clause Distribution restricted is a distribution clause which places restrictions on how the licensed resource may be distributed by third parties. These restrictions may be complete, e.g. no further redistribution, or partial. Allyson Lister Distribution restricted Distribution unrestricted is a distribution clause which states that the licensed resource can be redistributed by a third party in whatever manner that party wishes. Allyson Lister Distribution unrestricted Derivatives allowed clauses are derivatives clauses which state that derivative resources are allowed using the licensed resource. Even when allowed, such a clause may or may not restrict the usage of the licensed resource in a variety of ways. Allyson Lister Derivatives allowed GNU General Public License GNU GPL This is a free software license under the definition of "free" by the GNU Project, and is compatible with version 3 of the GNU GPL. http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013. Allyson Lister Apache License Version 2.0 The Academic Free License is a free software license under the definition of "free" by the GNU Project, is not copyleft, and is incompatible with the GNU GPL. AFL http://directory.fsf.org/wiki/License:AFLv3, accessed 12 June 2013; http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013 Allyson Lister Andy Brown Academic Free License version 3 This is the original BSD license with the advertising clause and another clause removed. (It is also sometimes called the “2-clause BSD license”.) It is a lax, permissive non-copyleft free software license, compatible with the GNU GPL. 2-clause BSD License http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013. Allyson Lister Andy Brown FreeBSD Open source software license License without restrictions on derivatives A licensed is a free license according to GNU if the users have the four essential freedoms: The freedom to run the program, for any purpose (freedom 0). The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this. The freedom to redistribute copies so you can help your neighbor (freedom 2). The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this. A program is free software if users have all of these freedoms. Thus, you should be free to redistribute copies, either with or without modifications, either gratis or charging a fee for distribution, to anyone anywhere. Being free to do these things means (among other things) that you do not have to ask or pay for permission to do so. “Free software” does not mean “noncommercial”. A free program must be available for commercial use, commercial development, and commercial distribution. Commercial development of free software is no longer unusual; such free commercial software is very important. You may have paid money to get copies of free software, or you may have obtained copies at no charge. But regardless of how you got your copies, you always have the freedom to copy and change the software, even to sell copies. http://www.gnu.org/philosophy/free-sw.html, accessed 12 June 2013. Allyson Lister Allyson Lister: This class defines those licenses which are free licenses, but which may or may not be compatible with any version of the GNU GPL. GNU Project Free License Type GNU GPL Compatible License Type is a GNU Project Free License Type which is also compatible with one or more versions of the GNU GPL Modified from http://www.gnu.org/copyleft/copyleft.html, accessed 12 June 2013. Allyson Lister GNU GPL Compatible License Type Copyleft is a derivative code same license clause which says that anyone who redistributes the software, with or without changes, must pass along the freedom to further copy and change it. In other words, it requires that all derivative code uses the same license, but further limits the type of license to one which gives everyone the rights to use, modify, and redistribute the program's code, or any program derived from it, but only if the distribution terms are unchanged. To copyleft a program, you first state that it is copyrighted; then the distribution terms described above are added. This makes copyleft a legal instrument ensuring that the code and the freedoms become legally inseparable. Modified from http://www.gnu.org/copyleft/copyleft.html, accessed 12 June 2013. Allyson Lister Copyleft The GNU GPL v3 is the latest version of the GNU GPL: a free software license, and a copyleft license. Please note that GPLv3 is not compatible with GPLv2 by itself. However, most software released under GPLv2 allows you to use the terms of later versions of the GPL as well. When this is the case, you can use the code under GPLv3 to make the desired combination. GNU General Public License Version 3 https://www.gnu.org/licenses/license-list.html, accessed on 23 June 2016. Allyson Lister GNU GPL v3 The GNU GPL v2 is an earlier version of the GNU GPL: a free software license, and a copyleft license. Please note that GPLv2 is, by itself, not compatible with GPLv3. However, most software released under GPLv2 allows you to use the terms of later versions of the GPL as well. When this is the case, you can use the code under GPLv3 to make the desired combination. GNU General Public License Version 2 https://www.gnu.org/licenses/license-list.html, accessed 23 June 2016. GNU GPL v2 CC0 is a public domain dedication from Creative Commons. A work released under CC0 is dedicated to the public domain to the fullest extent permitted by law. If that is not possible for any reason, CC0 also provides a lax, permissive license as a fallback. Both public domain works and the lax license provided by CC0 are compatible with the GNU GPL. CC0 1.0 Universal (CC0 1.0) Public Domain Dedication http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013. Allyson Lister CC0 1.0 CC BY 2.0 is a non-copyleft free (free by the definition of the GNU Project) license which lets others distribute, remix, tweak, and build upon your work, even commercially, as long as they credit you for the original creation. This is the most accommodating of Creative Commons licenses offered. Recommended for maximum dissemination and use of licensed materials. The GNU Project recommend it for art, entertainment works, and educational works. It is compatible with all versions of the GNU GPL; however, like all CC licenses, it should not be used on software. Creative Commons Attribution 2.0 Generic (CC BY 2.0) Modified from http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013 and 28 June 2016; Modified from http://creativecommons.org/licenses/, accessed 12 June 2013. Allyson Lister CC BY 2.0 Attribution required is an attribution clause which states that attribution of the type specified in the license must be provided whenever the resource is used. Allyson Lister Attribution required CC BY-SA 2.0 is a copyleft free (free by the definition of the GNU Project) license which lets others remix, tweak, and build upon your work even for commercial purposes, as long as they credit you and license their new creations under the identical terms. The GNU Project recommend this license for art, entertainment and educational works, but also recommend that it is not used for software or documentation, since it is tricky as to how exactly this license is compatible with the GNU GPL. Creative Commons Attribution-Sharealike 2.0 Generic Modified from http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013; Modified from http://creativecommons.org/licenses/, accessed 12 June 2013. Allyson Lister CC BY-SA 2.0 LPPL v1.3 is a free software license (by the defintion of the GNU Project), with less stringent requirements on distribution than LPPL 1.2. It is still incompatible with the GPL because some modified versions must include a copy of or pointer to an unmodified version.Software projects other than LaTeX rarely use it. Latex Project Public License v1.3c Modified from http://en.wikipedia.org/wiki/LaTeX_Project_Public_License, accessed 12 June 2013; modified from http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013. LPPL v1.3c LPPL v1.2 is a free software license (by the defintion of the GNU Project), This license is an incomplete statement of the distribution terms for LaTeX. While it is a free software license, it is incompatible with the GPL because it has many requirements that are not in the GPL. Software projects other than LaTeX rarely use it. Latex Project Public License v1.2 Modified from http://en.wikipedia.org/wiki/LaTeX_Project_Public_License, accessed 12 June 2013; modified from http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013. LPPL v1.2 MPL v2.0 a free software license as defined by the GNU Project. Section 3.3 provides indirect compatibility between this license and the GNU GPL version 2.0, the GNU LGPL version 2.1, the GNU AGPL version 3.0, and all later versions of those licenses. The MPL allows covered source code to be mixed with other files under a different, even proprietary license. However, code files licensed under the MPL must remain under the MPL and freely available in source form. http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013; http://en.wikipedia.org/wiki/Mozilla_Public_License, accessed 12 June 2013. MPL v2.0 Mozilla Public License Version 2.0 Allyson Lister Artistic License The Artistic License v 2.0 is a free software license by the definition of the GNU Project and compatible with the GPL thanks to the relicensing option in section 4(c)(ii) (as compared with the Artistic License 1.0). http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013. Allyson Lister Artistic License 2.0 Purchase cost is a license clause which states whether there is a cost involved with a particular usage or licensing of a resource. Allyson Lister Allyson Lister In some ways, purchase cost is similar to the already-extant usage clause hierarchy, which includes restricted and unrestricted usage. However, a usage limitation is not necessarily due to whether or not something costs money: even if the usage is academic only, it could still be either free or non-free. A license could have multiple usage clauses, e.g. academic only when free, and unrestricted if a fee is paid. Purchase cost was created which, together with a usage clause, defines both limitations and cost. Purchase cost Free is a type of purchase cost clause which, when applied, means that there is no cost for the users of the resource to which the license is attached. This clause can be combined with other clauses (such as usage clauses) to specify that only certain usages are free. Allyson Lister Allyson Lister This class refers only to the cost of the resource, not to the definition of "free software" as provided by the GNU Project and which is commonly used to describe software that respects users' freedom and community (http://www.gnu.org/philosophy/free-sw.html). Free Not Free is a type of purchase cost clause which, when applied, means that there is a cost for the users of the resource to which the license is attached. This clause can be combined with other clauses (such as usage clauses) to specify that only certain usages incur a purchase cost. Allyson Lister Allyson Lister This class refers only to the cost of the resource, not to the definition of "free software" as provided by the GNU Project and which is commonly used to describe software that respects users' freedom and community (http://www.gnu.org/philosophy/free-sw.html). Not Free A license which allows any form of usage of the artifact. free to use license The CC BY 4.0 license is a Creative Commons license. This is a non-copyleft free license that is good for art and entertainment works, and educational works. It is compatible with all versions of the GNU GPL; however, like all CC licenses, it should not be used on software. People are free to: Share — copy and redistribute the material in any medium or format; Adapt — remix, transform, and build upon the material for any purpose, even commercially. The licensor cannot revoke these freedoms as long as you follow the license terms. But they must conform to the following terms: Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits. Creative Commons Attribution 4.0 International (CC BY 4.0) http://creativecommons.org/licenses/by/4.0/ accessed June 22, 2016; https://www.gnu.org/licenses/license-list.html, accessed on June 28, 2016. Allyson Lister Allyson Lister: The only restriction on derivatives is that of the attribution requirement. CC BY 4.0 Attribution not required is an attribution clause which states that no attribution need be provided whenever the resource is used. Allyson Lister Allyson Lister Attribution not required CC BY 2.0 UK is a UK-specific non-copyleft free (free by the definition of the GNU Project) license which lets others distribute, remix, tweak, and build upon your work, even commercially, as long as they credit you for the original creation. This is the most accommodating of Creative Commons licenses offered. Recommended for maximum dissemination and use of licensed materials. The GNU Project recommend it for art, entertainment works, and educational works. It is compatible with all versions of the GNU GPL; however, like all CC licenses, it should not be used on software. Creative Commons Attribution 2.0 UK: England & Wales (CC BY 2.0 UK) Modified from the definition of http://www.ebi.ac.uk/swo/license/SWO_1000050. Allyson Lister CC BY 2.0 UK This is the latest version of the LGPL: a free software license, but not a strong copyleft license, because it permits linking with nonfree modules. It is compatible with GPLv3. It is therefore recommend for special circumstances only. Please note that LGPLv3 is not compatible with GPLv2 by itself. However, most software released under GPLv2 allows you to use the terms of later versions of the GPL as well. When this is the case, you can use the code under GPLv3 to make the desired combination. GNU Lesser General Public License (LGPL) version 3 https://www.gnu.org/licenses/license-list.html, accessed 23 June 2016. GNU LGPL v3 GNU AGPL This is a free software, copyleft license. Its terms effectively consist of the terms of GPLv3, with an additional paragraph in section 13 to allow users who interact with the licensed software over a network to receive the source for that program. It is recommended that developers consider using the GNU AGPL for any software which will commonly be run over a network. GNU Affero General Public License (AGPL) version 3 https://www.gnu.org/licenses/license-list.html, accessed on 23 June 2016. Allyson Lister GNU AGPL v3 This is the previous version of the LGPL: a free software license, but not a strong copyleft license, because it permits linking with nonfree modules. It is compatible with GPLv2 and GPLv3. We generally recommend the latest version of the LGPL, for special circumstances only. GNU Lesser General Public License (LGPL) version 2.1 https://www.gnu.org/licenses/license-list.html, accessed 28 June 2016. GNU LGPL v2.1 CC BY 2.1 JP is a Japan-specific non-copyleft free (free by the definition of the GNU Project) license which lets others distribute, remix, tweak, and build upon your work, even commercially, as long as they credit you for the original creation. This is the most accommodating of Creative Commons licenses offered. Recommended for maximum dissemination and use of licensed materials. The GNU Project recommend it for art, entertainment works, and educational works. It is compatible with all versions of the GNU GPL; however, like all CC licenses, it should not be used on software. Creative Commons Attribution 2.1 Japan (CC BY 2.1 JP) Modified from the definition of http://www.ebi.ac.uk/swo/license/SWO_1000050. Allyson Lister CC BY 2.1 JP CC BY 2.5 is a non-copyleft free (free by the definition of the GNU Project) license which lets others distribute, remix, tweak, and build upon your work, even commercially, as long as they credit you for the original creation. This is the most accommodating of Creative Commons licenses offered. Recommended for maximum dissemination and use of licensed materials. The GNU Project recommend it for art, entertainment works, and educational works. It is compatible with all versions of the GNU GPL; however, like all CC licenses, it should not be used on software. Creative Commons Attribution 2.5 Generic (CC BY 2.5) Modified from the definition of http://www.ebi.ac.uk/swo/license/SWO_1000050. Allyson Lister CC BY 2.5 CC BY 3.0 AU is an Australia-specific non-copyleft free (free by the definition of the GNU Project) license which lets others distribute, remix, tweak, and build upon your work, even commercially, as long as they credit you for the original creation. This is the most accommodating of Creative Commons licenses offered. Recommended for maximum dissemination and use of licensed materials. The GNU Project recommend it for art, entertainment works, and educational works. It is compatible with all versions of the GNU GPL; however, like all CC licenses, it should not be used on software. Creative Commons Attribution 3.0 Australia (CC BY 3.0 AU) Modified from the definition of http://www.ebi.ac.uk/swo/license/SWO_1000050. Allyson Lister CC BY 3.0 AU CC BY 3.0 is a non-copyleft free (free by the definition of the GNU Project) license which lets others distribute, remix, tweak, and build upon your work, even commercially, as long as they credit you for the original creation. This is the most accommodating of Creative Commons licenses offered. Recommended for maximum dissemination and use of licensed materials. The GNU Project recommend it for art, entertainment works, and educational works. It is compatible with all versions of the GNU GPL; however, like all CC licenses, it should not be used on software. Creative Commons Attribution 3.0 Unported (CC BY 3.0) Modified from the definition of http://www.ebi.ac.uk/swo/license/SWO_1000050. Allyson Lister CC BY 3.0 CC BY 3.0 US is a US-specific non-copyleft free (free by the definition of the GNU Project) license which lets others distribute, remix, tweak, and build upon your work, even commercially, as long as they credit you for the original creation. This is the most accommodating of Creative Commons licenses offered. Recommended for maximum dissemination and use of licensed materials. The GNU Project recommend it for art, entertainment works, and educational works. It is compatible with all versions of the GNU GPL; however, like all CC licenses, it should not be used on software. Creative Commons Attribution 3.0 United States (CC BY 3.0 US) Modified from the definition of http://www.ebi.ac.uk/swo/license/SWO_1000050. Allyson Lister CC BY 3.0 US CC BY-ND 3.0 is a nonfree license, as there are restrictions on distributing modified versions. You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. If you remix, transform, or build upon the material, you may not distribute the modified material. This license is generally used for documentation. Creative Commons Attribution-NoDerivs 3.0 Unported (CC BY-ND 3.0) https://www.gnu.org/licenses/license-list.html accessed 29 June 2016; https://creativecommons.org/licenses/by-nd/3.0/ accessed 29 June 2016. Allyson Lister CC BY-ND 3.0 CC BY-ND 4.0 is a nonfree license, as there are restrictions on distributing modified versions. You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. If you remix, transform, or build upon the material, you may not distribute the modified material. This license is generally used for documentation. Creative Commons Attribution-NoDerivatives 4.0 International (CC BY-ND 4.0) https://www.gnu.org/licenses/license-list.html accessed 29 June 2016; https://creativecommons.org/licenses/by-nd/3.0/ accessed 29 June 2016. Allyson Lister CC BY-ND 4.0 CC BY-NC 3.0 is a nonfree license, as there are restrictions on charging money for copies. You must give appropriate credit, provide a link to the license, use the work for non-commercial purposes, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. The GNU Project does not recommend that you use this license for documentation. In addition, it has a drawback for any sort of work: when a modified version has many authors, in practice getting permission for commercial use from all of them would become infeasible. Creative Commons Attribution-NonCommercial 3.0 Unported (CC BY-NC 3.0) https://www.gnu.org/licenses/license-list.html accessed 29 June 2016. Allyson Lister CC BY-NC 3.0 CC BY-NC 4.0 is a nonfree license, as there are restrictions on charging money for copies. You must give appropriate credit, provide a link to the license, use the work for non-commercial purposes, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. The GNU Project does not recommend that you use this license for documentation. In addition, it has a drawback for any sort of work: when a modified version has many authors, in practice getting permission for commercial use from all of them would become infeasible. Creative Commons Attribution-NonCommercial 4.0 International (CC BY-NC 4.0) https://www.gnu.org/licenses/license-list.html accessed 29 June 2016. Allyson Lister CC BY-NC 4.0 CC BY-NC-ND 3.0 is a nonfree license, as there are restrictions on distributing modified versions and on charging money for copies. You must give appropriate credit, provide a link to the license, and use the work for non-commercial purposes. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. If you remix, transform, or build upon the material, you may not distribute the modified material. Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported (CC BY-NC-ND 3.0) https://www.gnu.org/licenses/license-list.html accessed 29 June 2016. Allyson Lister CC BY-NC-ND 3.0 CC BY-NC-ND 2.5 is a nonfree license, as there are restrictions on distributing modified versions and on charging money for copies. You must give appropriate credit, provide a link to the license, and use the work for non-commercial purposes. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. If you remix, transform, or build upon the material, you may not distribute the modified material. Creative Commons Attribution-NonCommercial-NoDerivs 2.5 Generic (CC BY-NC-ND 2.5) https://www.gnu.org/licenses/license-list.html accessed 29 June 2016. Allyson Lister CC BY-NC-ND 2.5 CC BY-NC-ND 2.5 CH is a nonfree license, as there are restrictions on distributing modified versions and on charging money for copies. You must give appropriate credit, provide a link to the license, and use the work for non-commercial purposes. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. If you remix, transform, or build upon the material, you may not distribute the modified material. Creative Commons Attribution-NonCommercial-NoDerivs 2.5 Switzerland (CC BY-NC-ND 2.5 CH) https://www.gnu.org/licenses/license-list.html accessed 29 June 2016. Allyson Lister CC BY-NC-ND 2.5 CH CC BY-NC-ND 4.0 is a nonfree license, as there are restrictions on distributing modified versions and on charging money for copies. You must give appropriate credit, provide a link to the license, and use the work for non-commercial purposes. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. If you remix, transform, or build upon the material, you may not distribute the modified material. Creative Commons Attribution-NonCommercial-NoDerivs 4.0 International (CC BY-NC-ND 4.0) https://www.gnu.org/licenses/license-list.html accessed 29 June 2016. Allyson Lister CC BY-NC-ND 4.0 CC BY-NC-SA 2.5 is a nonfree license, as there are restrictions on charging money for copies. You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. This license also lets others build upon the original work for non-commercial purposes, as long as they credit you and license their new creations under the identical terms. The GNU Project does not recommend that you use this license for documentation. In addition, it has a drawback for any sort of work: when a modified version has many authors, in practice getting permission for commercial use from all of them would become infeasible. Creative Commons Attribution-NonCommercial-ShareAlike 2.5 Generic (CC BY-NC-SA 2.5) https://www.gnu.org/licenses/license-list.html accessed 29 June 2016. Allyson Lister CC BY-NC-SA 2.5 CC BY-NC-SA 3.0 is a nonfree license, as there are restrictions on charging money for copies. You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. This license also lets others build upon the original work for non-commercial purposes, as long as they credit you and license their new creations under the identical terms. The GNU Project does not recommend that you use this license for documentation. In addition, it has a drawback for any sort of work: when a modified version has many authors, in practice getting permission for commercial use from all of them would become infeasible. Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported (CC BY-NC-SA 3.0) https://www.gnu.org/licenses/license-list.html accessed 29 June 2016. Allyson Lister CC BY-NC-SA 3.0 CC BY-NC-SA 3.0 US is a nonfree license, as there are restrictions on charging money for copies. You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. This license also lets others build upon the original work for non-commercial purposes, as long as they credit you and license their new creations under the identical terms. The GNU Project does not recommend that you use this license for documentation. In addition, it has a drawback for any sort of work: when a modified version has many authors, in practice getting permission for commercial use from all of them would become infeasible. Creative Commons Attribution-NonCommercial-ShareAlike 3.0 United States (CC BY-NC-SA 3.0 US) https://www.gnu.org/licenses/license-list.html accessed 29 June 2016. Allyson Lister CC BY-NC-SA 3.0 US CC BY-NC-SA 2.5 IN is a nonfree license, as there are restrictions on charging money for copies. You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. This license also lets others build upon the original work for non-commercial purposes, as long as they credit you and license their new creations under the identical terms. The GNU Project does not recommend that you use this license for documentation. In addition, it has a drawback for any sort of work: when a modified version has many authors, in practice getting permission for commercial use from all of them would become infeasible. Creative Commons Attribution-NonCommercial-ShareAlike 2.5 India (CC BY-NC-SA 2.5 IN) https://www.gnu.org/licenses/license-list.html accessed 29 June 2016. Allyson Lister CC BY-NC-SA 2.5 IN CC BY-NC-SA 4.0 is a nonfree license, as there are restrictions on charging money for copies. You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. This license also lets others build upon the original work for non-commercial purposes, as long as they credit you and license their new creations under the identical terms. The GNU Project does not recommend that you use this license for documentation. In addition, it has a drawback for any sort of work: when a modified version has many authors, in practice getting permission for commercial use from all of them would become infeasible. Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0) https://www.gnu.org/licenses/license-list.html accessed 29 June 2016. Allyson Lister CC BY-NC-SA 4.0 CC BY-SA 2.1 JP is a copyleft free (free by the definition of the GNU Project) license which lets others remix, tweak, and build upon your work even for commercial purposes, as long as they credit you and license their new creations under the identical terms. The GNU Project recommend this license for art, entertainment and educational works, but also recommend that it is not used for software or documentation, since it is tricky as to how exactly this license is compatible with the GNU GPL. Creative Commons Attribution-Sharealike 2.1 Japan Modified from http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013; Modified from http://creativecommons.org/licenses/, accessed 12 June 2013. Allyson Lister CC BY-SA 2.1 JP CC BY-SA 3.0 is a copyleft free (free by the definition of the GNU Project) license which lets others remix, tweak, and build upon your work even for commercial purposes, as long as they credit you and license their new creations under the identical terms. The GNU Project recommend this license for art, entertainment and educational works, but also recommend that it is not used for software or documentation, since it is tricky as to how exactly this license is compatible with the GNU GPL. Creative Commons Attribution-Sharealike 3.0 Unported Modified from http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013; Modified from http://creativecommons.org/licenses/, accessed 12 June 2013. Allyson Lister CC BY-SA 3.0 CC BY-SA 3.0 US is a copyleft free (free by the definition of the GNU Project) license which lets others remix, tweak, and build upon your work even for commercial purposes, as long as they credit you and license their new creations under the identical terms. The GNU Project recommend this license for art, entertainment and educational works, but also recommend that it is not used for software or documentation, since it is tricky as to how exactly this license is compatible with the GNU GPL. Creative Commons Attribution-Sharealike 3.0 United States Modified from http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013; Modified from http://creativecommons.org/licenses/, accessed 12 June 2013. Allyson Lister CC BY-SA 3.0 US CC BY-SA 4.0 is a copyleft free (free by the definition of the GNU Project) license which lets others remix, tweak, and build upon your work even for commercial purposes, as long as they credit you and license their new creations under the identical terms. The GNU Project recommend this license for art, entertainment and educational works, but also recommend that it is not used for software or documentation, since it is tricky as to how exactly this license is compatible with the GNU GPL. Creative Commons Attribution-Sharealike 4.0 International Modified from http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013; Modified from http://creativecommons.org/licenses/, accessed 12 June 2013. Allyson Lister CC BY-SA 4.0 Open Data Commons The ODbL v1.0 allows a user of the databases to share, create and adapt the database. You must attribute any public use of the database, or works produced from the database. For redistribution of the database or derivative works, you must make the use of this license clear to others, and you must keep intact any notices on the original database. If you publicly use any adapted version of this database, or works produced from an adapted database, you must also offer that adapted database under the ODbL. If you redistribute the database, or an adapted version of it, then you may use technological measures that restrict the work (such as DRM) as long as you also redistribute a version without such measures. Open Database License (ODbL) v1.0 http://opendatacommons.org/licenses/odbl/summary/, accessed 5 July 2016. Allyson Lister ODbL v1.0 The DbCL v1.0 allows a user of the database contents to share, create and adapt the contents. You must attribute any public use of the contents, or works produced from them. For redistribution or derivative works, you must make the use of this license clear to others, and you must keep intact any notices on the original. If you publicly use any adapted version, or works produced from an adapted version, you must also offer it under the DbCL. If you redistribute the contents, or an adapted version of them, then you may use technological measures that restrict the work (such as DRM) as long as you also redistribute a version without such measures. Users of the DbCL must comply with the ODbL v1.0. ODC Database Contents License (DbCL) v1.0 http://opendatacommons.org/licenses/odbl/summary/, accessed 5 July 2016; http://opendatacommons.org/licenses/dbcl/1.0/, accessed 5 July 2016. Allyson Lister DbCL v1.0 The EMBLEM ELM Academic LIcense was developed as the license for the ELM (Eukaryotic Linear Motif) resource. Non-commerical use is allowed under this license, an additional commercial license is also available. This license makes the Licensed Software available free of charge for the licensee, which is a non-profit educational, academic and/or research institution. The software can only be used for academic research projects. This explicitly excludes projects which charge a fee, or projects that are done in collaboration with a third party that is funding the research in whole or in part in exchange for commercial rights on the results and/or possible delay in publication of any relevant results to the academic community. The user and any research assistants, co-workers or other workers who may use the Software agree to not grant licenses on any software that includes the Licensed Software, alone or integrated into other software, to third parties. Modification of the Licensed Software code is prohibited without the prior written consent of EMBLEM. ELM Software License Agreement http://elm.eu.org/media/Elm_academic_license.pdf, accessed 6 July 2017; http://elm.eu.org/infos/about.html accessed 6 July 2016. Allyson Lister EMBLEM ELM Academic License The FlowRepository Open Access Terms of Use license allows any individual to access the licensed product (originally the Flow Cytometry Data Repository) for any purpose. There are no restrictions on the use or redistribution of the data associated with this license, though it makes the statement that some data covered may also be included under more restrictive licensing. http://flowrepository.org/terms_of_service, accessed 6 July 2016. Allyson Lister FlowRepository Open Access Terms of Use The ODbL v1.0 allows a user of the databases to share, create and adapt the database. You must attribute any public use of the database, or works produced from the database. For redistribution of the database or derivative works, you must make the use of this license clear to others, and you must keep intact any notices on the original database. If you redistribute the database, or an adapted version of it, then you may use technological measures that restrict the work (such as DRM) as long as you also redistribute a version without such measures. Open Data Commons Attribution License (ODC-By) v1.0 http://opendatacommons.org/licenses/by/summary/, accessed 6 July 2016. Allyson Lister ODC-By v1.0 The ODC Public Domain Dedication and Licence is a document intended to allow you to freely share, modify, and use this work for any purpose and without any restrictions. This licence is intended for use on databases or their contents (“data”), either together or individually. The goal is to eliminate restrictions held by the original creator of the data and database on the use of it by others. Rightsholders will not be able to “dual license” their work by releasing the same work under different licences. This is because they have allowed anyone to use the work in whatever way they choose. Rightsholders therefore can’t re-license it under copyright or database rights on different terms because they have nothing left to license. ODC Public Domain Dedication and Licence http://opendatacommons.org/licenses/pddl/1.0/, accessed 7 July 2016. Allyson Lister PDDL v1.0 A vendor-specific license is a license which was, at least originally, created by a specific organization to be used just on the resources created within that organization. This is a hierarchy of convenience rather than of shared philosophy. Many of the licenses have since been taken up by other groups whose licensing requirements matched those of the originating organization. Allyson Lister Allyson Lister Vendor-specific License The NIDA NIH Data Access Policy specifies under what legal requirements NIDA NIH data may be accessed. Researchers may gain access to clinical data, genetic analysis data, and DNA by obtaining formal approval from the NIDA Genetic Data Access Request Committee. Allyson Lister Allyson Lister NIDA NIH Data Access Policy The Addgene Terms of Use specifies under what legal requirements Addgene data may be accessed. Data is available for use for non-commercial purposes, but users must get express written consent of Addgene to exploit the data for commercial purposes. All copyright, trademark and other proprietary notices must be retained on the data. As consent must be aquired for commercial use, this license only allows non-commercial use (a separate agreement must be entered into for commercial use). https://www.addgene.org/terms-of-use/, accessed 7 July 2016 Allyson Lister Addgene Terms of Use The CAS Information Use Policy specifies under what legal requirements CAS Information may be accessed. Attribution to ACS must be included whenever creating derivatives or redistributing data covered under this license.Each User is permitted to download and retain a maximum of 5,000 Records and a maximum of 5,000 Molfiles at any given time for personal use or to share within a Project team for the life of the Project. There are also limits on how long records may be stored with the licensee, and how records may be linked. http://www.cas.org/legal/infopolicy accessed 7 July 2016. Allyson Lister CAS Information Use Policy The created contents and works provided under this license by CellFinder are subject to the German copyright law. Third-party contributions are marked as such. Reproduction, adaptation, dissemination and any kind of exploitation outside the limits of the copyright require the written consent of the author or creator. Downloads and copies of these pages are only permitted for private, non-commercial use. The operators of these pages aim to observe the copyright of others or will refer to their own or license-free works. http://cellfinder.de/contact/disclaimer/, accessed 7 July 2016. Allyson Lister CellFinder Copyright The LINCS Data Policy is a license which allows redistribution and derivative works as long as the original data is attributed correctly. All investigators are encouraged, to publish results based on LINCS data. These results may include, but would not be limited to, integrating LINCS data with data from other sources. LINCS data are released with the sole restriction that they must be correctly cited so that others can establish provenance and access the original data; the correct citation will be released with each data set and will comprise either a PMID/PMCID reference or a unique LINCS identifier. http://www.lincsproject.org/data/data-release-policy/, accessed 7 July 2016. Allyson Lister LINCS Data Policy The GeneNetwork Conditions of Use describes the data licensing for the resource covered. Commercial and non-commercial use is allowed, though attribution is requested via either acknowledgement or co-authorship. Further restrictions on the bulk download of as-yet unpublished data is also described. (While mentioned in the document, software licensing is not the focus of this conditions of use and therefore is not modelled here.) http://www.genenetwork.org/conditionsofUse.html, accessed 7 July 2016. Allyson Lister GeneNetwork Conditions of Use The GMD Academic License is a vendor-specific license which allows the access and use of the licensed data for non-commercial purposes, as long as the appropriate attribution is used and copyright notices retained. A separate license agreement is required for commercial users and as such, they are not covered by this license. Without written consent by the GMD, no part of the GMD - in its original or in any way processed or reformatted form - may be re-distributed in any way. Golm Metabolome Database Academic License http://gmd.mpimp-golm.mpg.de/termsconditions.aspx, accessed 7 July 2016. GMD Academic License The GeneProf Academic License is a vendor-specific license which allows the access and use of the licensed resource for non-commercial purposes. http://www.geneprof.org/GeneProf/terms_and_conditions.jsp, accessed 7 July 2016. GeneProf Academic License The European Medicines Agency Copyright states that the Agency is the owner of copyright and other intellectual property rights for documents and other content published on their website. Information and documents made available on the Agency's webpages are public and may be reproduced and/or distributed, totally or in part, irrespective of the means and/or the formats used, for non-commercial and commercial purposes, provided that the Agency is always acknowledged as the source of the material. Such acknowledgement must be included in each copy of the material. Citations may be made from such material without prior permission, provided the source is always acknowledged. The above-mentioned permissions do not apply to content supplied by third parties. Therefore, for documents where the copyright vests in a third party, permission for reproduction must be obtained from this copyright holder. http://www.ema.europa.eu/ema/index.jsp?curl=pages/regulation/general/general_content_000178.jsp, accessed 12 July 2016. Allyson Lister European Medicines Agency Copyright miRTaBase Data License is a simple vendor license which allows academic users to make use of the data for free. http://mirtarbase.mbc.nctu.edu.tw/cache/download/LICENSE, accessed 12 July 2016 Allyson Lister miRTaBase Data License GBIF Data Sharing Agreement is a simple vendor license which allows all users to make use of the data for free, as long as the source of the data is properly attributed. http://www.gbif.org/terms/licences/data-sharing, accessed 12 July 2016 Allyson Lister GBIF Data Sharing Agreement IUPAC/InChI-Trust InChI Licence No. 1.0 is a vendor license which allows all users to make use of the resource, including the source code, for free, as long as its source is properly attributed. It is broadly compatible with the GNU GPL v3 and v2 in that it states in the license that you can change the license from this one to the GNU GPL if you wish. IUPAC/InChI-Trust Licence for the International Chemical Identifier (InChI) Software version 1.04 http://www.inchi-trust.org/wp/wp-content/uploads/2014/06/LICENCE.pdf, accessed 12 July 2016 Allyson Lister IUPAC/InChI-Trust InChI Licence No. 1.0 The Labome copyright makes the contents of their resource freely available for browsing. Any redistribution or reproduction of part or all of the contents in any form is prohibited other than the following: you may print or download to a local hard disk extracts for your use only, with a daily limit of 50 webpages; and you may copy the content to individual third parties for their use, but only if you acknowledge the website as the source of the material. You may not, except with our express written permission, distribute or commercially exploit the content. http://www.labome.com/about/copyright.html, accessed 12 July 2016. Allyson Lister Labome Copyright The CTD Legal Notice and Terms of Data Use specifies under what legal requirements the CTD data may be accessed. Data is available for use for non-commercial purposes as long as the data is properly attributed, but users must get express written consent of CTD to exploit the data for commercial purposes. As consent must be aquired for commercial use, this license only allows non-commercial use (a separate agreement must be entered into for commercial use). Additionally,You must notify CTD and describe your use of their data. For quality control purposes, you must provide CTD with periodic access to your publication of their data. Comparative Toxicogenomics Database Legal Notice and Terms of Use http://ctdbase.org/about/legal.jsp, accessed 12 July 2016 Allyson Lister CTD Legal Notice and Terms of Data Use LOINC RELMA Terms of Use is a vendor license which allows all users to make use of the data for free, as long as the source of the data is properly attributed. An unlimited number of copies of the licensed material may be used. https://loinc.org/terms-of-use/, accessed 12 July 2016 Allyson Lister LOINC RELMA Terms of Use MIACA Full Copyright is a vendor-specific license which allows the document it references to be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the MIACA Standards Initiative or other organizations, except as needed for the purpose of developing MIACA Standards Initiative Recommendations in which case the procedures for copyrights defined in the MIACA Document process must be followed, or as required to translate it into languages other than English. http://miaca.sourceforge.net/copyrightNotice.txt, accessed 12 July 2016 Allyson Lister MIACA Full Copyright The ORCID MIT-style license is identical to the MIT License, except for the addition of the following two clauses: 1. "The above license does not apply to the branding or the "look and feel" of the websites located at the orcid.org URL even if elements thereof are contained in the Software."; 2. "Except to provide the copyright notice required above or as allowed under ORCID Inc.'s Trademark Use Policy (available at http://orcid.org, under "Policies"), you may not use the name of ORCID, Inc., ORCID, its marks and logo, to advertise, promote or suggest any affiliation with or endorsement by ORCID, Inc. in connection with your use of the Software.". The MIT License is is a lax, permissive non-copyleft free software license, compatible with the GNU GPL. https://github.com/ORCID/ORCID-Source/blob/master/LICENSE.md, accessed 12 July 2016; https://www.gnu.org/licenses/license-list.html, accessed 28 June 2016. ORCID MIT-Style License (MIT) The NIH Genomic Data Sharing Policy specifies under what legal requirements NIH genomic data may be accessed. Access to human data is through a tiered model involving unrestricted- and controlled-data access mechanisms. Requests for controlled-access data are reviewed by NIH Data Access Committees (DACs). https://gds.nih.gov/PDF/NIH_GDS_Policy.pdf Allyson Lister NIH Genomic Data Sharing Policy The Facebase Data Access Policy specifies under what legal requirements Facebase data may be accessed. Non-sensitive data is available for use for all purposes and usages. As consent must be aquired for sensitive (or closed) data, this license only covers the use of the open data (a separate agreement must be entered into for restricted access data). https://www.facebase.org/methods/policies/, accessed 12 July 2016 Allyson Lister Facebase Data Access Policy The ORCID Terms of Use is a vendor-specific license for describing how the data in the ORCID resource may be used. ORCID data can be sublicensed, reproduced, stored, transmitted, distributed, publicly performed and publicly displayed for non-commercial and commercial uses. http://orcid.org/content/orcid-terms-use, accessed 12 July 2016 Allyson Lister ORCID Terms of Use The PPDB Academic Licens specifies under what legal requirements PPDB data may be accessed. Data is available for use for non-commercial purposes, but users must get express written consent of PPDB to exploit the data for commercial purposes. The resource will be used for teaching or not-for-profit research purposes only. The resource will not be further distributed to others. The recipient agrees to acknowledge the source of the material in any publication reporting its use. As consent must be aquired for commercial use, this license only allows non-commercial use (a separate agreement must be entered into for commercial use). Plant Promoter Database Academic License http://ppdb.agr.gifu-u.ac.jp/ppdb/cgi-bin/license.cgi, accessed 12 July 2016 Allyson Lister PPDB Academic License The SciCrunch Terms and Conditions specifies under what legal requirements SciCrunch data may be accessed. Broadly speaking, the site conforms, both for data and for the site documents themselves, to the CC BY 3.0 license. However, particular details for this resource (other than attribution requirements) are unclear. https://neuinfo.org/page/terms, accessed 12 July 2016. Allyson Lister SciCrunch Terms and Conditions The ProDom Commercial License is a vendor-specific license which allows the access and use of the licensed data for commercial purposes for a fee. Non-commercial use does not require licensing or a fee, and is covered by a separate license. http://prodom.prabi.fr/prodom/current/html/downcom.php, accessed 12 July 2016. ProDom Commercial License The SBGN Open License with Attribution is a very simple statement of openness for the SBGN standard and related resources available on its website. No one—not the principal investigators, nor the SBGN Editors, nor the members of the SBGN Scientific Committee, nor the funding agencies or anyone else—owns SBGN; it is a free and open community effort that extends beyond any single group, and they view themselves only as organizers and fellow developers. Systems Biology Graphical Notation Open License with Attribution http://www.sbgn.org/About, accessed 12July 2016. Allyson Lister SBGN Open License with Attribution The NLM Open License with Attribution is a vendor-specific license which is similar to public domain, but which requests attribution. Government information at NLM Web sites is in the public domain. Public domain information may be freely distributed and copied, but it is requested that in any subsequent use the National Library of Medicine (NLM) be given appropriate acknowledgement. When using NLM Web sites, you may encounter documents, illustrations, photographs, or other information resources contributed or licensed by private individuals, companies, or organizations that may be protected by U.S. and foreign copyright laws. Transmission or reproduction of protected items beyond that allowed by fair use as defined in the copyright laws requires the written permission of the copyright owners. Specific NLM Web sites containing protected information provide additional notification of conditions associated with its use. National Library of Medicine Open License with Attribution https://www.nlm.nih.gov/copyright.html, accessed 12 July 2016. Allyson Lister NLM Open License with Attribution The RegenBase Terms of Use is a vendor-specific license which requires attribution and which does not meet the requirements for open source code, as there is a statement saying that the user will NOT translate, reverse engineer, decompile or disassemble the SYSTEM, or disclose the SYSTEM or any underlying information or technology to any third party. http://regenbase.org/terms-of-use.html, accessed 12 July 2016 Allyson Lister RegenBase Terms of Use The SABIO-RK Non-Commercial Purpose License covers use of the Database for Non-Commercial Purpose only, and appropriate attribution must be given. Non-Commercial Purpose means the use of the Database solely for internal non-commercial research and academic purposes. As consent must be aquired for commercial use, a separate agreement must be entered into for commercial use and is not covered here. http://sabiork.h-its.org/layouts/content/termscondition.gsp, accessed 13 July 2016 Allyson Lister SABIO-RK Non-Commercial Purpose License The Terms of Use for EMBL-EBI Services reflect EMBL-EBI’s commitment to OpenScience through its mission to provide freely available online services, databases and software relating to data contributed from life science experiments to the largest possible community. They impose no additional constraints on the use of the contributed data than those provided by the data owner.
EMBL-EBI expects attribution (e.g. in publications, services or products) for any of its online services, databases or software in accordance with good scientific practice. The expected attribution will be indicated on the appropriate web page. http://www.ebi.ac.uk/about/terms-of-use, accessed 13 July 2016. Allyson Lister Terms of Use for EMBL-EBI Services The UCUM Terms of Use is a vendor-specific license which allows the resource it references to be used for commercial or non-commercial purposes without restriction of any kind, provided that appropriate attribution is given. However, the resource itself may not be modified in any way. Users may make and distribute an unlimited number of copies of the Licensed Materials. Each copy thereof must include the Copyright Notice and License. The Unified Code for Units of Measure Terms of Use http://unitsofmeasure.org/trac/wiki/TermsOfUse, accessed 13 July 2016 Allyson Lister UCUM Terms of Use The UMLS Metathesaurus License is a vendor-specific license which allows redistribution (as part of a larger computer application) as long as the original data is attributed correctly and a summary of data use provided each year. There is no cost to use the service, and may be used both commercially and non-commercially. Users must inform the resource if it is redistributed within a computer application. https://uts.nlm.nih.gov/license.html, accessed 13 July 2016. Allyson Lister UMLS Metathesaurus License The MHAS Data Policy is a vendor-specific license which requires that users attribute the data properly. The data is accessible free of charge to all commercial and non-commercial users. http://www.mhasweb.org/Data.aspx, accessed 13 July 2016. Allyson Lister MHAS Data Policy The ALFRED Copyright is a vendor-specific license which states that the resource is freely available to the scientific community for statistical analysis, the only condition being that attribution is required. The ALlele FREquency Database Copyright https://alfred.med.yale.edu/alfred/fullcopyrightpage.asp, accessed 13 July 2016. Allyson Lister ALFRED Copyright Commercial use only is a usage restricted clause which restricts the use of the licensed resource only to licensees who are commercial entites. Allyson Lister Allyson Lister Allyson Lister: Some licenses are expressly written for their commercial users. In such cases, a vendor will normally have multiple licenses, one for non-commercial use and one for commercial use. Commercial use only Fee-Based Commercial License is a license which, among its license clauses, states that commercial entities may use the resource for a fee. Allyson Lister Allyson Lister Allyson Lister: This is a convenience class which combines multiple license clauses to create a defined class, such that any license type which meets the requirements will be inferred to fall into this category. Fee-Based Commercial License The BRENDA License is a vendor-specific license which allows access to the official website and its data free of charge. Any inclusion of BRENDA components into other data bases, or redistribution of BRENDA requires a license. To obtain commercial in-house versions please contact our distributor Biobase GmbH ( http://www.biobase-international.com). In-house versions for academic users are available from Enzymeta GmbH (http://www.enzymeta.de). The copyright of the printed version is held by Springer publishers. Users of the website may retrieve a copy of the data but must not alter the BRENDA data or charge money for a copy of it, and must not distribute any BRENDA data without prior permission of the copyright holder. As there are separate licenses for in-house versions of BRENDA, please note that this license only describes the website-accessible version of BRENDA. http://www.brenda-enzymes.org/copy.php, accessed 13 July 2016. Allyson Lister BRENDA License The TCGA Data Use Certification is a vendor-specific license which specifies the certification which must be officially agreed to before data may be accessed. There are a number of requirements in this license including attribution, non-transferability, annual progress updates, and a number of security measures. The Cancer Genome Atlas Data Use Certification http://cancergenome.nih.gov/pdfs/Data_Use_Certv082014, accessed 13 July 2016 Allyson Lister TCGA Data Use Certification Non-Commercial No-Fee License is a license which, among its license clauses, states that non-commercial entities may use the resource without a purchase or usage cost. Allyson Lister Allyson Lister Allyson Lister: This is a convenience class which combines multiple license clauses to create a defined class, such that any license type which meets the requirements will be inferred to fall into this category. Non-Commercial No-Fee License DrugBank is offered to the public as a freely available resource. Use and re-distribution of the data, in whole or in part, for commercial purposes (including internal use) requires a license. We ask that users who download significant portions of the database cite the DrugBank paper in any resulting publications. As consent must be aquired for commercial use, this license only describes the non-commercial aspects of data usage (a separate agreement must be entered into for commercial use). http://www.drugbank.ca/about, accessed 13 July 2016 Allyson Lister DrugBank Academic License The UCSC Genome Browser Commercial Software License is a vendor-specific license which allows the access and use of the licensed data for commercial purposes under specific restrictions for a fee. The licensee shall not have the right to create Derivative Works of the Licensed Products, and the Licensee shall not have the right to sublicense, sell, transfer, or assign the Licensed Products. Non-commercial use does not require licensing or a fee, and is covered by a separate license. http://genome.cse.ucsc.edu/license/gblicense.pdf, accessed 13 July 2016. UCSC Genome Browser Commercial Software License Permission required for commercial use is a clause which restricts the use of the licensed resource only to licensees who are commercial entites which have received explicit permission in the manner stipulated by the resource. Allyson Lister Allyson Lister Allyson Lister: Some licenses are expressly written for their commercial users. In such cases, a vendor will normally have multiple licenses, one for non-commercial use and one for commercial use. Permission required for commercial use Permission required for derivative work is a clause which restricts the production of derivative work based on the licensed resource only to licensees who have received explicit permission in the manner stipulated by the resource. Allyson Lister Allyson Lister Permission required for derivative work Data are to be used only for purposes of research and education. Commercial use is prohibited without written permission from Xenbase. The contributor(s) of unpublished data should be explicitly acknowledged in any publication that incorporates, or is based in part or entirely on these data. Xenbase should be explicitly acknowledged when data used in any publication, has been in part or solely derived from analysis of data from this website. As consent must be aquired for commercial use, this license only describes the non-commercial aspects of data usage (a separate agreement must be entered into for commercial use). http://www.xenbase.org/other/static/aboutXenbase.jsp, accessed 13 July 2016 Allyson Lister Xenbase Academic Conditions of Use The RIKEN copyright is a vendor-specific license which states that all text, photographs, diagrams, and other materials on their website are copyrighted by RIKEN unless explicitly specified otherwise on the website. It is prohibited to use, reproduce, or modify any of the material without RIKEN's permission. http://www.riken.jp/en/terms/, accessed 14 July 2016 Allyson Lister RIKEN Copyright The Design Science License is a license intended to be a general "copyleft" that can be applied to any kind of work that has protection under copyright. This license states those certain conditions under which a work published under its terms may be copied, distributed, and modified. Unlike other open source licenses, the DSL was intended to be used on any type of copyrightable work, including documentation and source code. It was the first "generalized copyleft" license. This is a free and copyleft license meant for general data. THe GNU Project does not recommend it for software or documentation, since it is incompatible with the GNU GPL and with the GNU FDL; however, they consider it appropriate for other kinds of data. The DSL was written by Michael Stutz. The DSL came out in the 1990s, before the formation of the Creative Commons. According to Wikipedia, once the Creative Commons arrived, Stutz considered the DSL experiment "over" and no longer recommended its use. https://www.gnu.org/licenses/dsl.html, accessed 13 July 2016; https://www.gnu.org/licenses/license-list.html, accessed 13 July 2016; https://en.wikipedia.org/wiki/Design_science_license, accessed 13 July 2016. Allyson Lister Design Science License The University of Concordia Terms of Use is a vendor-specific license which states that no document appearing on this website or any other website owned, operated or controlled by Concordia may be copied, sold, reproduced, republished, downloaded, posted, transmitted or distributed by any means with the exception of downloading or printing the contents of the site for personal, non-commercial use. This use must bear in mind that Concordia reserves its copyright and its rights to exclusivity over the material. http://www.concordia.ca/web/terms.html, accessed 14 July 2016 Allyson Lister University of Concordia Terms of Use All OME formats and software are freely available, and all OMERO and Bio-Formats source code is available under GNU public "copyleft" licenses or through commercial license from Glencoe Software. FLIMfit is also now available under a GNU public "copyleft" license. For questions about the GNU license refer to the Frequently Asked Questions about the GNU Licenses page. Bio-Formats - under the terms of the GNU public "copyleft" license, any software package linking to Bio-Formats, either directly or indirectly, cannot be distributed unless its source code is also made available under the terms of the GPL. Some components which provide reader and writer implementations for open file formats, are released under a more permissive BSD-2 license which enables non-GPL third party software. For a complete list of which file formats are included in the BSD license, see the BSD column of the supported formats table. Developers of non-GPL software wishing to leverage Bio-Formats components not covered by the BSD license may purchase a commercial license from Glencoe Software; please contact them at bioformats@glencoesoftware.com to discuss your requirements. The core OME Model Schema files (.XSD) use the Creative Commons Attribution 4.0 International License, and as such you are free to share or adapt them as long as you attribute the OME consortium as follows; "This work is derived in part from the OME specification. Copyright (C) 2002-2016 Open Microscopy Environment". See further information about using OME-XML in your work. This website is also covered by the Creative Commons Attribution 4.0 International License - you are free to share or adapt content as long as you credit the Open Microscopy Environment. The exception to this is the screenshots and videos which can only be used for non-commercial purposes, see Attributions below. http://www.openmicroscopy.org/site/about/licensing-attribution/licensing, accessed on 23 June 2016. Allyson Lister OME Software Conditons of Use The ImmPort Conditions of Use is a vendor-specific license which allows the use of ImmPort data for any legal purpose except for those prohibited elsewhere in this agreement. There are very few prohibitions, and no requirement for attribution. https://aspera-immport.niaid.nih.gov:9443/displayAgreement, accessed 14 July 2016 Allyson Lister ImmPort Conditions of Use Distribution with notices is a distribution clause in which distribution is unrestricted, except that all distributions must retain certain licence information (e.g., copyright notices). Andy Brown Andy Brown Distribution with notices This is a lax, permissive non-copyleft free software license, compatible with the GNU GPL. It is sometimes ambiguously referred to as the MIT License. For substantial programs it is better to use the Apache 2.0 license since it blocks patent treachery. Expat License https://www.gnu.org/licenses/license-list.html, accessed 28 June 2016. MIT License The GNU Lesser General Public License (LGPL) is a free software license published by the Free Software Foundation (FSF). The license allows developers and companies to use and integrate LGPL software into their own (even proprietary) software without being required by the terms of a strong copyleft license to release the source code of their own software-parts. The license requires that only the LGPL software-parts be modifiable by end-users via source code availability. GNU Lesser General Public License http://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License, accessed 27 March 2015. Allyson Lister GNU LGPL The Artistic License v1.0 is not considered a free software license by the definition of the GNU Project because it is too vague; some passages are &quot;too clever for their own good&quot;, and their meaning is not clear. The GNU Project recommends that it is not used except as part of the disjunctive license of Perl. http://www.gnu.org/licenses/license-list.html, accessed 13 June 2013. Allyson Lister Andy Brown Artistic License 1.0 The Eclipse Public License is similar to the Common Public License. This is a free software license. Unfortunately, its weak copyleft and choice of law clause make it incompatible with the GNU GPL. The only change is that the EPL removes the broader patent retaliation language regarding patent infringement suits specifically against Contributors to the EPL'd program. Eclipse Public License Version 1.0 https://www.gnu.org/licenses/license-list.html, accessed 28 June 2016. EPL v1 The Modified BSD is a software license based on he original FreeBSD license, modified by removal of the advertising clause. It is a lax, permissive non-copyleft free software license, compatible with the GNU GPL. This license is sometimes referred to as the 3-clause BSD license. According to the GNU Project, the modified BSD license is not bad, as lax permissive licenses go, though the Apache 2.0 license is preferable. However, it is risky to recommend use of “the BSD license”, even for special cases such as small programs, because confusion could easily occur and lead to use of the flawed original BSD license. To avoid this risk, you can suggest the X11 license instead. The X11 license and the modified BSD license are more or less equivalent. According to the GNU project, the Apache 2.0 license is better for substantial programs, since it prevents patent treachery. 3 clause BSD License http://www.gnu.org/licenses/license-list.html, accessed June 12, 2013. Allyson Lister Andy Jones Modified BSD Latex Project Public License LPPL OPL v1.0 is not a free software license according to the definition of the GNU Project because it requires sending every published modified version to a specific initial developer. Open Public License Version 1.0 http://www.gnu.org/licenses/license-list.html, accessed 12 June 2013. OPL v1.0 Mozilla Public License MPL Development status is an information content entity which indicates the maturity of a software entity within the context of the software life cycle. Allyson Lister Andy Brown Development status Alpha is a development status which is applied to software by the developer/publisher during initial development and testing. Software designated alpha is commonly unstable and prone to crashing. It may or may not be released publicly. Modified from http://en.wikipedia.org/wiki/Software_release_life_cycle, accessed 11 June 2013. Allyson Lister alpha Beta is a development status which is generally applied to software by the developer/publisher once the majority of features have been implemented, but when the software may still contain bugs or cause crashes or data loss. Software designated beta is often released publicly, either on a general release or to a specific subset of users called beta testers. Modified from http://en.wikipedia.org/wiki/Software_release_life_cycle, accessed 11 June 2013. Allyson Lister beta A release candidate (RC) is a beta version with potential to be a final product, which is ready to release unless significant bugs emerge. http://en.wikipedia.org/wiki/Software_release_life_cycle#Release_candidate, accessed 22 October 2014. Release candidate Live is a development status which is applied to software that has been designated as suitable for production environments by the developer/publisher. If a non-free product, software at this stage is available for purchase Production Allyson Lister, Jon Ison, and Modified from http://en.wikipedia.org/wiki/Software_release_life_cycle, accessed 11 June 2013. Allyson Lister Live Sofware is no longer being supplied by the developers/publishers Obsolete An updated version of the software is available. Andy Brown Superseded The first release of a piece of software. A first release does not imply any particular levels of maturity other than is this is the first instance of this software to be considered released. James Malone First release The latest release of a piece of software. This does not imply any levels of maturity other than indicating this is the most recent release. James Malone Latest release Software has developers actively maintaining it (fixing bugs) Andy Brown Maintained matrix manipulation spreadsheet editing document outlining image compression ontology engineering word processing simulation and analysis of biochemical networks Manage Laboratory information such is commonly performed by LIMS software. laboratory information management the objective of performing the actions of an operation system such as managing the software running a computer and the interactions with the system resources and hardware. manage computer operations Text editing is the objective of editing plain text files. text editing Renders a file in such a way that its contents can be understood by users. file rendering annotation editing biological data processing molecular sequence analysis Andy Brown citation management Allyson Lister sequence alignment Allyson Lister multiple sequence alignment Allyson Lister pairwise sequence alignment An averaging objective is a data transformation objective where the aim is to perform mean calculations on the input of the data transformation. James Malone averaging A center calculation objective is a data transformation objective where the aim is to calculate the center of an input data set. James Malone center calculation A class discovery objective (sometimes called unsupervised classification) is a data transformation objective where the aim is to organize input data (typically vectors of attributes) into classes, where the number of classes and their specifications are not known a priori. Depending on usage, the class assignment can be definite or probabilistic. James Malone class discovery A class prediction objective (sometimes called supervised classification) is a data transformation objective where the aim is to create a predictor from training data through a machine learning technique. The training data consist of pairs of objects (typically vectors of attributes) and class labels for these objects. The resulting predictor can be used to attach class labels to any valid novel input object. Depending on usage, the prediction can be definite or probabilistic. A classification is learned from the training data and can then be tested on test data. PERSON: Elisabetta Manduchi PERSON: James Malone class prediction A correction is where the aim is to correct for error, noise or other impairments to the input of the data transformation or derived from the data transformation itself. PERSON: James Malone PERSON: Melanie Courtot correction A background correction is where the aim is to remove irrelevant contributions from the measured signal, e.g. those due to instrument noise or sample preparation. PERSON: Elisabetta Manduchi James Malone background correction An error correction is a data transformation objective where the aim is to remove (correct for) erroneous contributions arising from the input data, or the transformation itself. PERSON: James Malone James Malone error correction cross validation curve fitting is a data transformation in which the aim is to find a curve which matches a series of data points and possibly other constraints. PERSON: Elisabetta Manduchi Elisabetta Manduchi James Malone curve fitting A normalization is a data transformation objective where the aim is to remove systematic sources of variation to put the data on equal footing in order to create a common base for comparisons. PERSON: Elisabetta Manduchi PERSON: Helen Parkinson PERSON: James Malone James Malone data normalization A decision tree induction objective is a data transformation objective in which a tree-like graph of edges and nodes is created and from which the selection of each branch requires that some type of logical decision is made. PERSON: James Malone James Malone decision tree induction mean calculation A descriptive statistical calculation objective is a data transformation objective which concerns any calculation intended to describe a feature of a data set, for example, its center or its variability. James Malone PERSON: Elisabetta Manduchi PERSON: James Malone PERSON: Melanie Courtot PERSON: Monnie McGee descriptive statistical calculation differential expression analysis A feature extraction objective is a data transformation objective where the aim of the data transformation is to generate quantified values from a scanned image. feature extraction The process of publishing software. Typically this process involves a software publisher performing acts such as licensing, marketing, publicising and/or providing support for a product. Andy Brown software publishing process The process of developing software, typically involving the design, implementation and testing of software. Andy Brown AL 24.9.19: Merged the now-obsolete http://www.ebi.ac.uk/swo/objective/SWO_4000007 into this class as they were describing the same concept. See also https://github.com/allysonlister/swo/issues/2 software development oboInOwl:ObsoleteClass A data mining algorithm is an algorithm that has as its objective a data mining task and outputs as a result a generalization specified by a generalization specification. data mining algorithm Clustering algorithm is a data mining algorithm that solves a clustering task and as a result produces a clustering. clustering algorithm Estimating the (Joint) Probability Distribution. A set of data (of type T) is often assumed to be a sample taken from a population according to a probability distribution. A probability distribution/density function assigns a non-negative probability/density to each object of type T. Probably the most general data mining task (Hand et al. 2001) is the task of estimating the (joint) probability distribution D over type T from a set of data items or a sample drawn from that distribution. As mentioned above, in the most typical case we would have T = Tuple(T1, . . ., Tk), where each of T1, . . ., Tk is Boolean, Discrete(S) or Real. We talk about the joint probability distribution to emphasize the difference to the marginal distributions of each of the variables of type T1, . . ., Tk: the joint distribution captures the interactions among the variables. Representing multi-variate distributions is a non-trivial task. Two approaches are commonly used in data mining. In the density-based clustering paradigm, mixtures of multi-variate Gaussian distributions are typically considered (Hand et al. 2001). Probabilistic graphical models, most notably Bayesian networks, represent graphically the (in)dependencies between the variables: Learning their structure and parameters is an important approach to the problem of estimating the joint probability distribution. probability distribution estimation task the task of pattern discovery is to find all local patterns from a given pattern language that satisfy the required conditions. A prototypical instantiation of this task is the task of finding frequent itemsets (sets of items, such as {bread, butter}), which are often found together in a transaction (e.g., a market basket) (Aggrawal et al 1993). The condition that a pattern (itemset) has to satisfy in this case is to appear in (hold true for) a sufficiently high proportion (called support and denoted by s) of the transactions in the input dataset. With the increasing interest in mining complex data, mining frequent patterns is also considered for structured data. We can thus talk about mining frequent subsequences or mining frequent subgraphs in sequence or graph data. We can consider as frequency the multiple occurrences of a pattern in a single data structure (e.g., sequence or graph) or the single occurrences of a pattern in multiple data structures. pattern discovery task A data mining task is an objective specification that specifies the objective that a data mining algorithm needs to achieve when executed on a dataset to produce as output a generalization. data mining task Predictive modeling algorithm is a data mining algorithm that solves a predictive modeling task and as a result produces a predictive model. predictive modeling algorithm Pattern discovery algorithm is a data mining algorithm that solves a pattern discovery task and as a result produces a set of patterns. pattern discovery algorithm Learning a (Probabilistic) Predictive Model. In this task, we are given a dataset that consists of examples of the form (d, c), where each d is of type Td and each c is of type Tc. We will refer to d as the description and c as the class or target. To learn a predictive model means to find a mapping from the description to the target, m :: Td → Tc, that fits the data closely. This means that the observed target values and the target values predicted by the model, i.e., c and ˆc = m(d), have to match closely. predictive modeling task probability distribution estimation algorithm Clustering. Clustering in general is concerned with grouping objects into classes of similar objects (Kaufman and Rousseeuw 1990). Given a set of examples (object descriptions), the task of clustering is to partition these examples into subsets, called clusters. clustering task Ensemble algorithms are algorithms that generate an ensemble when executed on a dataset. The ensemble algorithms include a specification of single generalization algorithms which are executed in oreder to produce the single generalizations that compose the ensemble. Examples of ensemble algorithms include bagging, boosting, stacking, random forests, random subspaces,bagging of random subspaces etc. For example, bagging of decision trees algorithm includes the specification of a bagging algorithm and having a decision tree algorithm for generating the base models composing the ensemble. ensemble algorithm single generalization algorithms are data mining algorithms that given a dataset on input produce a generalization at the output. single generalization algorithm rdf:List owl:Thing skos:Collection Collection A meaningful collection of concepts. Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy. skos:Concept Concept An idea or notion; a unit of thought. skos:ConceptScheme Concept Scheme A set of concepts, optionally including statements about semantic relationships between those concepts. Thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', and other types of controlled vocabulary are all examples of concept schemes. Concept schemes are also embedded in glossaries and terminologies. A concept scheme may be defined to include concepts from different sources. skos:OrderedCollection Ordered Collection An ordered collection of concepts, where both the grouping and the ordering are meaningful. Ordered collections can be used where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'. Activity Activity starting-point entities-activities http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Activity http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Activity 0 ActivityInfluence ActivityInfluence provides additional descriptions of an Activity's binary influence upon any other kind of resource. Instances of ActivityInfluence use the prov:activity property to cite the influencing Activity. It is not recommended that the type ActivityInfluence be asserted without also asserting one of its more specific subclasses. ActivityInfluence qualified ActivitiyInfluence is the capacity of an activity to have an effect on the character, development, or behavior of another by means of generation, invalidation, communication, or other. Agent Agent starting-point agents-responsibility An agent is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Agent AgentInfluence AgentInfluence provides additional descriptions of an Agent's binary influence upon any other kind of resource. Instances of AgentInfluence use the prov:agent property to cite the influencing Agent. It is not recommended that the type AgentInfluence be asserted without also asserting one of its more specific subclasses. AgentInfluence qualified AgentInfluence is the capacity of an agent to have an effect on the character, development, or behavior of another by means of attribution, association, delegation, or other. Association An instance of prov:Association provides additional descriptions about the binary prov:wasAssociatedWith relation from an prov:Activity to some prov:Agent that had some responsiblity for it. For example, :baking prov:wasAssociatedWith :baker; prov:qualifiedAssociation [ a prov:Association; prov:agent :baker; :foo :bar ]. Association qualified agents-responsibility An activity association is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Association http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Association Attribution An instance of prov:Attribution provides additional descriptions about the binary prov:wasAttributedTo relation from an prov:Entity to some prov:Agent that had some responsible for it. For example, :cake prov:wasAttributedTo :baker; prov:qualifiedAttribution [ a prov:Attribution; prov:entity :baker; :foo :bar ]. Attribution qualified agents-responsibility http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig Attribution is the ascribing of an entity to an agent. When an entity e is attributed to agent ag, entity e was generated by some unspecified activity that in turn was associated to agent ag. Thus, this relation is useful when the activity is not known, or irrelevant. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribution http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-attribution Bundle Note that there are kinds of bundles (e.g. handwritten letters, audio recordings, etc.) that are not expressed in PROV-O, but can be still be described by PROV-O. Bundle expanded A bundle is a named set of provenance descriptions, and is itself an Entity, so allowing provenance of provenance to be expressed. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-bundle-entity http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-bundle-declaration Collection Collection expanded collections A collection is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the collections. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-collection Communication An instance of prov:Communication provides additional descriptions about the binary prov:wasInformedBy relation from an informed prov:Activity to the prov:Activity that informed it. For example, :you_jumping_off_bridge prov:wasInformedBy :everyone_else_jumping_off_bridge; prov:qualifiedCommunication [ a prov:Communication; prov:activity :everyone_else_jumping_off_bridge; :foo :bar ]. Communication qualified entities-activities http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig Communication is the exchange of an entity by two activities, one activity using the entity generated by the other. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Communication http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-wasInformedBy Delegation An instance of prov:Delegation provides additional descriptions about the binary prov:actedOnBehalfOf relation from a performing prov:Agent to some prov:Agent for whom it was performed. For example, :mixing prov:wasAssociatedWith :toddler . :toddler prov:actedOnBehalfOf :mother; prov:qualifiedDelegation [ a prov:Delegation; prov:entity :mother; :foo :bar ]. Delegation qualified agents-responsibility Delegation is the assignment of authority and responsibility to an agent (by itself or by another agent) to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work. For example, a student acted on behalf of his supervisor, who acted on behalf of the department chair, who acted on behalf of the university; all those agents are responsible in some way for the activity that took place but we do not say explicitly who bears responsibility and to what degree. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-delegation http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-delegation Derivation An instance of prov:Derivation provides additional descriptions about the binary prov:wasDerivedFrom relation from some derived prov:Entity to another prov:Entity from which it was derived. For example, :chewed_bubble_gum prov:wasDerivedFrom :unwrapped_bubble_gum; prov:qualifiedDerivation [ a prov:Derivation; prov:entity :unwrapped_bubble_gum; :foo :bar ]. The more specific forms of prov:Derivation (i.e., prov:Revision, prov:Quotation, prov:PrimarySource) should be asserted if they apply. Derivation qualified derivations http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig A derivation is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Derivation http://www.w3.org/TR/2013/REC-prov-n-20130430/#Derivation-Relation End An instance of prov:End provides additional descriptions about the binary prov:wasEndedBy relation from some ended prov:Activity to an prov:Entity that ended it. For example, :ball_game prov:wasEndedBy :buzzer; prov:qualifiedEnd [ a prov:End; prov:entity :buzzer; :foo :bar; prov:atTime '2012-03-09T08:05:08-05:00'^^xsd:dateTime ]. End qualified entities-activities http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig End is when an activity is deemed to have been ended by an entity, known as trigger. The activity no longer exists after its end. Any usage, generation, or invalidation involving an activity precedes the activity's end. An end may refer to a trigger entity that terminated the activity, or to an activity, known as ender that generated the trigger. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-End http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-End Entity Entity starting-point entities-activities http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig An entity is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-entity http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Entity EntityInfluence EntityInfluence provides additional descriptions of an Entity's binary influence upon any other kind of resource. Instances of EntityInfluence use the prov:entity property to cite the influencing Entity. It is not recommended that the type EntityInfluence be asserted without also asserting one of its more specific subclasses. EntityInfluence qualified EntityInfluence is the capacity of an entity to have an effect on the character, development, or behavior of another by means of usage, start, end, derivation, or other. Generation An instance of prov:Generation provides additional descriptions about the binary prov:wasGeneratedBy relation from a generated prov:Entity to the prov:Activity that generated it. For example, :cake prov:wasGeneratedBy :baking; prov:qualifiedGeneration [ a prov:Generation; prov:activity :baking; :foo :bar ]. Generation qualified entities-activities http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig Generation is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Generation http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Generation Influence An instance of prov:Influence provides additional descriptions about the binary prov:wasInfluencedBy relation from some influenced Activity, Entity, or Agent to the influencing Activity, Entity, or Agent. For example, :stomach_ache prov:wasInfluencedBy :spoon; prov:qualifiedInfluence [ a prov:Influence; prov:entity :spoon; :foo :bar ] . Because prov:Influence is a broad relation, the more specific relations (Communication, Delegation, End, etc.) should be used when applicable. Because prov:Influence is a broad relation, its most specific subclasses (e.g. prov:Communication, prov:Delegation, prov:End, prov:Revision, etc.) should be used when applicable. Influence qualified derivations Influence is the capacity of an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-influence http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-influence InstantaneousEvent An instantaneous event, or event for short, happens in the world and marks a change in the world, in its activities and in its entities. The term 'event' is commonly used in process algebra with a similar meaning. Events represent communications or interactions; they are assumed to be atomic and instantaneous. InstantaneousEvent qualified entities-activities http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#dfn-event The PROV data model is implicitly based on a notion of instantaneous events (or just events), that mark transitions in the world. Events include generation, usage, or invalidation of entities, as well as starting or ending of activities. This notion of event is not first-class in the data model, but it is useful for explaining its other concepts and its semantics. Invalidation An instance of prov:Invalidation provides additional descriptions about the binary prov:wasInvalidatedBy relation from an invalidated prov:Entity to the prov:Activity that invalidated it. For example, :uncracked_egg prov:wasInvalidatedBy :baking; prov:qualifiedInvalidation [ a prov:Invalidation; prov:activity :baking; :foo :bar ]. Invalidation qualified entities-activities http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig Invalidation is the start of the destruction, cessation, or expiry of an existing entity by an activity. The entity is no longer available for use (or further invalidation) after invalidation. Any generation or usage of an entity precedes its invalidation. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Invalidation http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Invalidation Location Location expanded A location can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. As such, there are numerous ways in which location can be expressed, such as by a coordinate, address, landmark, and so forth. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-location http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-attribute Organization prov:Organization Organization expanded agents-responsibility An organization is a social or legal institution such as a company, society, etc. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-types Person prov:Person Person expanded agents-responsibility Person agents are people. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-types Plan There exist no prescriptive requirement on the nature of plans, their representation, the actions or steps they consist of, or their intended goals. Since plans may evolve over time, it may become necessary to track their provenance, so plans themselves are entities. Representing the plan explicitly in the provenance can be useful for various tasks: for example, to validate the execution as represented in the provenance record, to manage expectation failures, or to provide explanations. Plan expanded qualified agents-responsibility A plan is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Association http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Association PrimarySource An instance of prov:PrimarySource provides additional descriptions about the binary prov:hadPrimarySource relation from some secondary prov:Entity to an earlier, primary prov:Entity. For example, :blog prov:hadPrimarySource :newsArticle; prov:qualifiedPrimarySource [ a prov:PrimarySource; prov:entity :newsArticle; :foo :bar ] . PrimarySource qualified derivations A primary source for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight. Because of the directness of primary sources, they 'speak for themselves' in ways that cannot be captured through the filter of secondary sources. As such, it is important for secondary sources to reference those primary sources from which they were derived, so that their reliability can be investigated. A primary source relation is a particular case of derivation of secondary materials from their primary sources. It is recognized that the determination of primary sources can be up to interpretation, and should be done according to conventions accepted within the application's domain. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-primary-source http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-original-source Quotation An instance of prov:Quotation provides additional descriptions about the binary prov:wasQuotedFrom relation from some taken prov:Entity from an earlier, larger prov:Entity. For example, :here_is_looking_at_you_kid prov:wasQuotedFrom :casablanca_script; prov:qualifiedQuotation [ a prov:Quotation; prov:entity :casablanca_script; :foo :bar ]. Quotation qualified derivations A quotation is the repeat of (some or all of) an entity, such as text or image, by someone who may or may not be its original author. Quotation is a particular case of derivation. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-quotation http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-quotation Revision An instance of prov:Revision provides additional descriptions about the binary prov:wasRevisionOf relation from some newer prov:Entity to an earlier prov:Entity. For example, :draft_2 prov:wasRevisionOf :draft_1; prov:qualifiedRevision [ a prov:Revision; prov:entity :draft_1; :foo :bar ]. Revision qualified derivations A revision is a derivation for which the resulting entity is a revised version of some original. The implication here is that the resulting entity contains substantial content from the original. Revision is a particular case of derivation. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-revision http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Revision Role Role qualified agents-responsibility A role is the function of an entity or agent with respect to an activity, in the context of a usage, generation, invalidation, association, start, and end. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-attribute-role http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-attribute SoftwareAgent SoftwareAgent expanded agents-responsibility A software agent is running software. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-agent http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-types Start An instance of prov:Start provides additional descriptions about the binary prov:wasStartedBy relation from some started prov:Activity to an prov:Entity that started it. For example, :foot_race prov:wasStartedBy :bang; prov:qualifiedStart [ a prov:Start; prov:entity :bang; :foo :bar; prov:atTime '2012-03-09T08:05:08-05:00'^^xsd:dateTime ] . Start qualified entities-activities http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig Start is when an activity is deemed to have been started by an entity, known as trigger. The activity did not exist before its start. Any usage, generation, or invalidation involving an activity follows the activity's start. A start may refer to a trigger entity that set off the activity, or to an activity, known as starter, that generated the trigger. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Start http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Start Usage An instance of prov:Usage provides additional descriptions about the binary prov:used relation from some prov:Activity to an prov:Entity that it used. For example, :keynote prov:used :podium; prov:qualifiedUsage [ a prov:Usage; prov:entity :podium; :foo :bar ]. Usage qualified entities-activities http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig Usage is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-Usage http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-Usage foaf:Agent example to be eventually removed example to be eventually removed failed exploratory term The term was used in an attempt to structure part of the ontology but in retrospect failed to do a good job Person:Alan Ruttenberg failed exploratory term metadata complete Class has all its metadata, but is either not guaranteed to be in its final location in the asserted IS_A hierarchy or refers to another class that is not complete. metadata complete organizational term Term created to ease viewing/sort terms for development purpose, and will not be included in a release organizational term ready for release Class has undergone final review, is ready for use, and will be included in the next release. Any class lacking "ready_for_release" should be considered likely to change place in hierarchy, have its definition refined, or be obsoleted in the next release. Those classes deemed "ready_for_release" will also derived from a chain of ancestor classes that are also "ready_for_release." ready for release metadata incomplete Class is being worked on; however, the metadata (including definition) are not complete or sufficiently clear to the branch editors. metadata incomplete uncurated Nothing done yet beyond assigning a unique class ID and proposing a preferred term. uncurated pending final vetting All definitions, placement in the asserted IS_A hierarchy and required minimal metadata are complete. The class is awaiting a final review by someone other than the term editor. pending final vetting Core is an instance of a grouping of terms from an ontology or ontologies. It is used by the ontology to identify main classes. PERSON: Alan Ruttenberg PERSON: Melanie Courtot obsolete_core true placeholder removed placeholder removed terms merged An editor note should explain what were the merged terms and the reason for the merge. terms merged term imported This is to be used when the original term has been replaced by a term imported from an other ontology. An editor note should indicate what is the URI of the new term to use. term imported term split This is to be used when a term has been split in two or more new terms. An editor note should indicate the reason for the split and indicate the URIs of the new terms created. term split This is to be used if none of the existing instances cover the reason for obsolescence. An editor note should indicate this new reason. We expect to be able to mine these new reasons and add instances as required. obsolete_other true universal Hard to give a definition for. Intuitively a "natural kind" rather than a collection of any old things, which a class is able to be, formally. At the meta level, universals are defined as positives, are disjoint with their siblings, have single asserted parents. Alan Ruttenberg A Formal Theory of Substances, Qualities, and Universals, http://ontology.buffalo.edu/bfo/SQU.pdf universal defined class A defined class is a class that is defined by a set of logically necessary and sufficient conditions but is not a universal "definitions", in some readings, always are given by necessary and sufficient conditions. So one must be careful (and this is difficult sometimes) to distinguish between defined classes and universal. Alan Ruttenberg defined class named class expression A named class expression is a logical expression that is given a name. The name can be used in place of the expression. named class expressions are used in order to have more concise logical definition but their extensions may not be interesting classes on their own. In languages such as OWL, with no provisions for macros, these show up as actuall classes. Tools may with to not show them as such, and to replace uses of the macros with their expansions Alan Ruttenberg named class expression to be replaced with external ontology term Terms with this status should eventually replaced with a term from another ontology. Alan Ruttenberg group:OBI to be replaced with external ontology term requires discussion A term that is metadata complete, has been reviewed, and problems have been identified that require discussion before release. Such a term requires editor note(s) to identify the outstanding issues. Alan Ruttenberg group:OBI requires discussion The term was added to the ontology on the assumption it was in scope, but it turned out later that it was not. This obsolesence reason should be used conservatively. Typical valid examples are: un-necessary grouping classes in disease ontologies, a phenotype term added on the assumption it was a disease. https://github.com/information-artifact-ontology/ontology-metadata/issues/77 https://orcid.org/0000-0001-5208-3432 out of scope This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page). If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome. W3C PROVenance Interchange Ontology (PROV-O) Recommendation version 2013-04-30 2023-03-07 has part my body has part my brain (continuant parthood, two material entities) my stomach has part my stomach cavity (continuant parthood, material entity has part immaterial entity) this year has part this day (occurrent parthood) a core relation that holds between a whole and its part Everything has itself as a part. Any part of any part of a thing is itself part of that thing. Two distinct things cannot have each other as a part. Occurrents are not subject to change and so parthood between occurrents holds for all the times that the part exists. Many continuants are subject to change, so parthood between continuants will only hold at certain times, but this is difficult to specify in OWL. See http://purl.obolibrary.org/obo/ro/docs/temporal-semantics/ Parthood requires the part and the whole to have compatible classes: only an occurrent have an occurrent as part; only a process can have a process as part; only a continuant can have a continuant as part; only an independent continuant can have an independent continuant as part; only a specifically dependent continuant can have a specifically dependent continuant as part; only a generically dependent continuant can have a generically dependent continuant as part. (This list is not exhaustive.) A continuant cannot have an occurrent as part: use 'participates in'. An occurrent cannot have a continuant as part: use 'has participant'. An immaterial entity cannot have a material entity as part: use 'location of'. An independent continuant cannot have a specifically dependent continuant as part: use 'bearer of'. A specifically dependent continuant cannot have an independent continuant as part: use 'inheres in'. has_part has part has measurement unit label This document is about information artifacts and their representations A (currently) primitive relation that relates an information artifact to an entity. 7/6/2009 Alan Ruttenberg. Following discussion with Jonathan Rees, and introduction of "mentions" relation. Weaken the is_about relationship to be primitive. We will try to build it back up by elaborating the various subproperties that are more precisely defined. Some currently missing phenomena that should be considered "about" are predications - "The only person who knows the answer is sitting beside me" , Allegory, Satire, and other literary forms that can be topical without explicitly mentioning the topic. person:Alan Ruttenberg Smith, Ceusters, Ruttenberg, 2000 years of philosophy is about A person's name denotes the person. A variable name in a computer program denotes some piece of memory. Lexically equivalent strings can denote different things, for instance "Alan" can denote different people. In each case of use, there is a case of the denotation relation obtaining, between "Alan" and the person that is being named. A primitive, instance-level, relation obtaining between an information content entity and some portion of reality. Denotation is what happens when someone creates an information content entity E in order to specifically refer to something. The only relation between E and the thing is that E can be used to 'pick out' the thing. This relation connects those two together. Freedictionary.com sense 3: To signify directly; refer to specifically 2009-11-10 Alan Ruttenberg. Old definition said the following to emphasize the generic nature of this relation. We no longer have 'specifically denotes', which would have been primitive, so make this relation primitive. g denotes r =def r is a portion of reality there is some c that is a concretization of g every c that is a concretization of g specifically denotes r person:Alan Ruttenberg Conversations with Barry Smith, Werner Ceusters, Bjoern Peters, Michel Dumontier, Melanie Courtot, James Malone, Bill Hogan denotes m is a quality measurement of q at t. When q is a quality, there is a measurement process p that has specified output m, a measurement datum, that is about q 8/6/2009 Alan Ruttenberg: The strategy is to be rather specific with this relationship. There are other kinds of measurements that are not of qualities, such as those that measure time. We will add these as separate properties for the moment and see about generalizing later From the second IAO workshop [Alan Ruttenberg 8/6/2009: not completely current, though bringing in comparison is probably important] This one is the one we are struggling with at the moment. The issue is what a measurement measures. On the one hand saying that it measures the quality would include it "measuring" the bearer = referring to the bearer in the measurement. However this makes comparisons of two different things not possible. On the other hand not having it inhere in the bearer, on the face of it, breaks the audit trail. Werner suggests a solution based on "Magnitudes" a proposal for which we are awaiting details. -- From the second IAO workshop, various comments, [commented on by Alan Ruttenberg 8/6/2009] unit of measure is a quality, e.g. the length of a ruler. [We decided to hedge on what units of measure are, instead talking about measurement unit labels, which are the information content entities that are about whatever measurement units are. For IAO we need that information entity in any case. See the term measurement unit label] [Some struggling with the various subflavors of is_about. We subsequently removed the relation represents, and describes until and only when we have a better theory] a represents b means either a denotes b or a describes describe: a describes b means a is about b and a allows an inference of at least one quality of b We have had a long discussion about denotes versus describes. From the second IAO workshop: An attempt at tieing the quality to the measurement datum more carefully. a is a magnitude means a is a determinate quality particular inhering in some bearer b existing at a time t that can be represented/denoted by an information content entity e that has parts denoting a unit of measure, a number, and b. The unit of measure is an instance of the determinable quality. From the second meeting on IAO: An attempt at defining assay using Barry's "reliability" wording assay: process and has_input some material entity and has_output some information content entity and which is such that instances of this process type reliably generate outputs that describes the input. This one is the one we are struggling with at the moment. The issue is what a measurement measures. On the one hand saying that it measures the quality would include it "measuring" the bearer = referring to the bearer in the measurement. However this makes comparisons of two different things not possible. On the other hand not having it inhere in the bearer, on the face of it, breaks the audit trail. Werner suggests a solution based on "Magnitudes" a proposal for which we are awaiting details. Alan Ruttenberg is quality measurement of has_specified_input has_specified_input see is_input_of example_of_usage The inverse property of is_specified_input_of 8/17/09: specified inputs of one process are not necessarily specified inputs of a larger process that it is part of. This is in contrast to how 'has participant' works. PERSON: Alan Ruttenberg PERSON: Bjoern Peters PERSON: Larry Hunter PERSON: Melanie Coutot has_specified_input has_specified_output has_specified_output The inverse property of is_specified_output_of PERSON: Alan Ruttenberg PERSON: Bjoern Peters PERSON: Larry Hunter PERSON: Melanie Courtot has_specified_output is_specified_output_of is_specified_output_of A relation between a planned process and a continuant participating in that process. The presence of the continuant at the end of the process is explicitly specified in the objective specification which the process realizes the concretization of. Alan Ruttenberg PERSON:Bjoern Peters is_specified_output_of has participant The relation obtains, for example, when this particular process of oxygen exchange across this particular alveolar membrane has_participant this particular sample of hemoglobin at this particular time. this blood coagulation has participant this blood clot this investigation has participant this investigator this process has participant this input material (or this output material) Has_participant is a primitive instance-level relation between a process, a continuant, and a time at which the continuant participates in some way in the process. a relation between a process and a continuant, in which the continuant is somehow involved in the process Has_participant is a primitive instance-level relation between a process, a continuant, and a time at which the continuant participates in some way in the process. The relation obtains, for example, when this particular process of oxygen exchange across this particular alveolar membrane has_participant this particular sample of hemoglobin at this particular time. has_participant http://obo-relations.googlecode.com/svn/trunk/src/ontology/core.owl Andy Brown http://www.obofoundry.org/ro/#OBO_REL:has_participant has participant has participant en Adam Goldstein Alan Ruttenberg Albert Goldfain Barry Smith Bjoern Peters Carlo Torniai Chris Mungall Chris Stoeckert Christian A. Boelling Clint Dowland Darren Natale David Osumi-Sutherland Gwen Frishkoff Holger Stenzhorn James A. Overton James Malone Jennifer Fostel Jie Zheng Jonathan Rees Larisa Soldatova Lawrence Hunter Mathias Brochhausen Matt Brush Melanie Courtot Michel Dumontier Paolo Ciccarese Pat Hayes Philippe Rocca-Serra Randy Dipert Ron Rudnicki Satya Sahoo Sivaram Arabandi Werner Ceusters William Duncan William Hogan Yongqun (Oliver) He The Information Artifact Ontology (IAO) is an ontology of information entities, originally driven by work by the OBI digital entity and realizable information entity branch. Information Artifact Ontology (IAO) An information artifact is, loosely, a dependent continuant or its bearer that is created as the result of one or more intentional processes. Examples: uniprot, the english language, the contents of this document or a printout of it, the temperature measurements from a weather balloon. For more information, see the project home page at https://github.com/information-artifact-ontology/IAO IDs allocated to related efforts: PNO: IAO_0020000-IAO_0020999, D_ACTS: IAO_0021000-IAO_0021999 IDs allocated to subdomains of IAO. pno.owl: IAO_0020000-IAO_0020999, d-acts.owl: IAO_0021000-IAO_0021999 2022-11-07 Degui Zhi Kirk Roberts Licong Cui Xiaqian Jiang Tuan Amith and Cui Tao An ontology representing the model card structure https://creativecommons.org/licenses/by/3.0/ Model Card Ontology 2023-03-07 Allyson Lister Andy Brown Duncan Hull Helen Parkinson James Malone Jon Ison Nandini Badarinarayan Robert Stevens SWO (The Software Ontology) The Software Ontology (SWO) is a resource for describing software tools, their types, tasks, versions, licences, provenance and associated data. Date of release: 21.10.2019 The Software Ontology (SWO) is a resource for describing software tools, their types, tasks, versions, licensing, provenance and associated data. It contains SWO-specific classes and axioms as well as imports from: 1. BFO 2. IAO 3. OBI 4. EDAM 1.7 Dave Beckett Nikki Rogers Participants in W3C's Semantic Web Deployment Working Group. Alistair Miles Sean Bechhofer An RDF vocabulary for describing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', other types of controlled vocabulary, and also concept schemes embedded in glossaries and terminologies. SKOS Vocabulary EmptyCollection EmptyCollection expanded collections An empty collection is a collection without members. specializationOf expanded alternate http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#prov-dm-constraints-fig An entity that is a specialization of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. Examples of aspects include a time period, an abstraction, and a context associated with the entity. http://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-specialization generalizationOf http://www.w3.org/TR/2013/REC-prov-n-20130430/#expression-specialization A revision is a derivation that revises an entity into a revised version. wasRevisionOf expanded derivations hadRevision