part of
type: ObjectProperty
equivalent property:
  inverse of: has part
inverse of: has part
type: TransitiveProperty
IAO_0000111: is part of
IAO_0000112: my brain is part of my body (continuant parthood, two material entities)
IAO_0000112: my stomach cavity is part of my stomach (continuant parthood, immaterial entity is part of material entity)
IAO_0000112: this day is part of this year (occurrent parthood)
IAO_0000115: a core relation that holds between a part and its whole
IAO_0000116: 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.
IAO_0000116: 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 https://code.google.com/p/obo-relations/wiki/ROAndTime
IAO_0000116: 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'.
IAO_0000118: part_of
IAO_0000412: obi.owl
RO_0001900: RO_0001901

has part
type: ObjectProperty
type: TransitiveProperty
IAO_0000111: has part
IAO_0000112: my body has part my brain (continuant parthood, two material entities)
IAO_0000112: my stomach has part my stomach cavity (continuant parthood, material entity has part immaterial entity)
IAO_0000112: this year has part this day (occurrent parthood)
IAO_0000115: a core relation that holds between a whole and its part
IAO_0000116: 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.
IAO_0000116: 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 https://code.google.com/p/obo-relations/wiki/ROAndTime
IAO_0000116: 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'.
IAO_0000118: has_part
IAO_0000412: obi.owl
RO_0001900: RO_0001901

realized in
type: ObjectProperty
equivalent property:
  inverse of: realizes
inverse of: realizes
range: process
IAO_0000111: realized in
IAO_0000112: this disease is realized in this disease course
IAO_0000112: this fragility is realized in this shattering
IAO_0000112: this investigator role is realized in this investigation
IAO_0000118: is realized by
IAO_0000118: realized_in
IAO_0000412: obi.owl
IAO_0000600: [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])
comment: 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

realizes
type: ObjectProperty
domain: process
IAO_0000111: realizes
IAO_0000112: this disease course realizes this disease
IAO_0000112: this investigation realizes this investigator role
IAO_0000112: this shattering realizes this fragility
IAO_0000412: obi.owl
IAO_0000600: 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])
comment: 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

has measurement unit label
type: ObjectProperty
sub property of: has part
type: FunctionalProperty
IAO_0000412: obi.owl

is about
type: ObjectProperty
IAO_0000112: This document is about information artifacts and their representations
IAO_0000114: pending final vetting
IAO_0000115: is_about is a (currently) primitive relation that relates an information artifact to an entity.
IAO_0000116: 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.
IAO_0000117: person:Alan Ruttenberg
IAO_0000119: Smith, Ceusters, Ruttenberg, 2000 years of philosophy
IAO_0000412: obi.owl

denotes
type: ObjectProperty
sub property of: is about
inverse of: is denoted by
IAO_0000112: 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.
IAO_0000115: denotes is 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
IAO_0000116: 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
IAO_0000117: person:Alan Ruttenberg
IAO_0000119: Conversations with Barry Smith, Werner Ceusters, Bjoern Peters, Michel Dumontier, Melanie Courtot, James Malone, Bill Hogan
IAO_0000412: obi.owl

is_supported_by_data
type: ObjectProperty
IAO_0000111: is_supported_by_data
IAO_0000112: The relation between the conclusion "Gene tpbA is involved in EPS production" and the data items produced using two sets of organisms, one being a tpbA knockout, the other being tpbA wildtype tested in polysacharide production assays and analyzed using an ANOVA.
IAO_0000114: ready for release
IAO_0000115: The relation between a data item and a conclusion where the conclusion is the output of a data interpreting process and the data item is used as an input to that process
IAO_0000117: OBI
IAO_0000119: OBI
IAO_0000119: Philly 2011 workshop
IAO_0000412: obi.owl

has_specified_input
type: ObjectProperty
equivalent property:
  inverse of: is_specified_input_of
sub property of: has participant
inverse of: is_specified_input_of
domain: planned process
IAO_0000111: has_specified_input
IAO_0000112: see is_input_of example_of_usage
IAO_0000114: ready for release
IAO_0000115: A relation between a planned process and a continuant participating in that process that is not created during the process. The presence of the continuant during the process is explicitly specified in the plan specification which the process realizes the concretization of.
IAO_0000116: 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.
IAO_0000117: PERSON: Alan Ruttenberg
IAO_0000117: PERSON: Bjoern Peters
IAO_0000117: PERSON: Larry Hunter
IAO_0000117: PERSON: Melanie Coutot
IAO_0000412: obi.owl

is_specified_input_of
type: ObjectProperty
sub property of: participates in
range: planned process
IAO_0000111: is_specified_input_of
IAO_0000112: some Autologous EBV(Epstein-Barr virus)-transformed B-LCL (B lymphocyte cell line) is_input_for instance of Chromum Release Assay described at https://wiki.cbil.upenn.edu/obiwiki/index.php/Chromium_Release_assay
IAO_0000114: ready for release
IAO_0000115: A relation between a continuant participating in that process that is not created during the process. The presence of the continuant during the process is explicitly specified in the plan specification which the process realizes the concretization of.
IAO_0000117: Alan Ruttenberg
IAO_0000117: PERSON:Bjoern Peters
IAO_0000412: obi.owl

has_specified_output
type: ObjectProperty
equivalent property:
  inverse of: is_specified_output_of
sub property of: has participant
inverse of: is_specified_output_of
domain: planned process
IAO_0000111: has_specified_output
IAO_0000114: ready for release
IAO_0000115: 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.
IAO_0000117: PERSON: Alan Ruttenberg
IAO_0000117: PERSON: Bjoern Peters
IAO_0000117: PERSON: Larry Hunter
IAO_0000117: PERSON: Melanie Courtot
IAO_0000412: obi.owl

is_specified_output_of
type: ObjectProperty
sub property of: participates in
range: planned process
IAO_0000111: is_specified_output_of
IAO_0000114: ready for release
IAO_0000115: A relation between a continuant participating in a planned 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.
IAO_0000117: Alan Ruttenberg
IAO_0000117: PERSON:Bjoern Peters
IAO_0000412: obi.owl

has value specification
type: ObjectProperty
sub property of: has part
IAO_0000111: has value specification
IAO_0000114: metadata complete
IAO_0000115: A relation between an information content entity and a value specification that specifies its value.
IAO_0000117: PERSON: James A. Overton
IAO_0000119: OBI
IAO_0000412: obi.owl

participates in
type: ObjectProperty
equivalent property:
  inverse of: has participant
inverse of: has participant
IAO_0000111: participates in
IAO_0000112: this blood clot participates in this blood coagulation
IAO_0000112: this input material (or this output material) participates in this process
IAO_0000112: this investigator participates in this investigation
IAO_0000115: a relation between a continuant and a process, in which the continuant is somehow involved in the process
IAO_0000118: participates_in
IAO_0000412: obi.owl

has participant
type: ObjectProperty
property chain axiom: has part
IAO_0000111: has participant
IAO_0000112: this blood coagulation has participant this blood clot
IAO_0000112: this investigation has participant this investigator
IAO_0000112: this process has participant this input material (or this output material)
IAO_0000115: a relation between a process and a continuant, in which the continuant is somehow involved in the process
IAO_0000116: 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.
IAO_0000118: has_participant
IAO_0000412: obi.owl
source: http://www.obofoundry.org/ro/#OBO_REL:has_participant

is concretized as
type: ObjectProperty
equivalent property:
  inverse of: concretizes
inverse of: concretizes
IAO_0000112: 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).
IAO_0000112: 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).
IAO_0000115: 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.
IAO_0000412: obi.owl

concretizes
type: ObjectProperty
IAO_0000112: 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).
IAO_0000112: 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).
IAO_0000115: 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.
IAO_0000412: obi.owl

declares
type: ObjectProperty
sub property of: is about
inverse of: is declared by
IAO_0000115: property to indicate that a design declares a variable; the inverse property is 'is declared by'
IAO_0000117: Alejandra Gonzalez-Beltran
IAO_0000117: Orlaith Burke
IAO_0000117: Philippe Rocca-Serra

is declared by
type: ObjectProperty
IAO_0000115: property to indicate the variables declared by a design; the inverse property is 'declares'
IAO_0000117: Alejandra Gonzalez-Beltran
IAO_0000117: Orlaith Burke
IAO_0000117: Philippe Rocca-Serra

executes
type: ObjectProperty
property chain axiom: realizes
property chain axiom: concretizes
IAO_0000115: relationship between a planned process and the plan specification that it carries out; it is defined as equivalent to the composed relationship (realizes o concretizes)
IAO_0000117: Alejandra Gonzalez-Beltran
IAO_0000117: Orlaith Burke
IAO_0000117: Philippe Rocca-Serra
IAO_0000119: AGB

is member of
type: ObjectProperty
inverse of: has member
IAO_0000115: relationship between an element and a set it belongs to
IAO_0000117: Alejandra Gonzalez-Beltran
IAO_0000117: Orlaith Burke
IAO_0000117: Philippe Rocca-Serra
IAO_0000119: AGB

has member
type: ObjectProperty
IAO_0000115: relationship between a set and one of its elements
IAO_0000117: Alejandra Gonzalez-Beltran
IAO_0000117: Orlaith Burke
IAO_0000117: Philippe Rocca-Serra
IAO_0000119: AGB

is denoted by
type: ObjectProperty
IAO_0000115: Inverse relation of 'denotes', where denotation is what happens when someone creates an information content entity E in order to specifically refer to something (from 'denotes' definition).
IAO_0000117: Alejandra Gonzalez-Beltran
IAO_0000117: Orlaith Burke
IAO_0000117: Philippe Rocca-Serra

has measurement value
type: DatatypeProperty
type: FunctionalProperty
range: double
IAO_0000412: obi.owl

has specified numeric value
type: DatatypeProperty
sub property of: has specified value
range: real
IAO_0000111: has specified numeric value
IAO_0000114: metadata complete
IAO_0000115: A relation between a value specification and a number that quantifies it.
IAO_0000116: A range of 'real' might be better than 'float'. For now we follow 'has measurement value' until we can consider technical issues with SPARQL queries and reasoning.
IAO_0000117: PERSON: James A. Overton
IAO_0000119: OBI
IAO_0000412: obi.owl

has specified value
type: DatatypeProperty
IAO_0000111: has specified value
IAO_0000114: metadata incomplete
IAO_0000115: A relation between a value specification and a literal.
IAO_0000116: This is not an RDF/OWL object property. It is intended to link a value found in e.g. a database column of 'M' (the literal) to an instance of a value specification class, which can then be linked to indicate that this is about the biological gender of a human subject.
IAO_0000119: OBI
IAO_0000412: obi.owl

process
type: Class
BFO_0000179: process
BFO_0000180: Process
IAO_0000112: a process of cell-division, \ a beating of the heart
IAO_0000112: a process of meiosis
IAO_0000112: a process of sleeping
IAO_0000112: the course of a disease
IAO_0000112: the flight of a bird
IAO_0000112: the life of an organism
IAO_0000112: your process of aging.
IAO_0000115: An occurrent that has temporal proper parts and for some time t, p s-depends_on some material entity at t.
IAO_0000116: 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)
IAO_0000116: 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])
IAO_0000412: obi.owl
IAO_0000602: (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]

objective specification
type: Class
subclass of: directive information entity
IAO_0000111: objective specification
IAO_0000112: In the protocol of a ChIP assay the objective specification says to identify protein and DNA interaction.
IAO_0000114: ready for release
IAO_0000115: 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.
IAO_0000116: 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."
IAO_0000116: 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.
IAO_0000116: Answers the question, why did you do this experiment?
IAO_0000117: PERSON: Alan Ruttenberg
IAO_0000117: PERSON: Barry Smith
IAO_0000117: PERSON: Bjoern Peters
IAO_0000117: PERSON: Jennifer Fostel
IAO_0000118: goal specification
IAO_0000119: OBI Plan and Planned Process/Roles Branch
IAO_0000119: OBI_0000217
IAO_0000412: obi.owl

action specification
type: Class
subclass of: directive information entity
IAO_0000112: Pour the contents of flask 1 into flask 2
IAO_0000114: ready for release
IAO_0000115: a directive information entity that describes an action the bearer will take
IAO_0000117: Alan Ruttenberg
IAO_0000119: OBI Plan and Planned Process branch
IAO_0000412: obi.owl

directive information entity
type: Class
IAO_0000114: ready for release
IAO_0000115: An information content entity whose concretizations indicate to their bearer how to realize them in a process.
IAO_0000116: 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.
IAO_0000116: 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.
IAO_0000116: 8/6/2009 Alan Ruttenberg: Changed label from "information entity about a realizable" after discussions at ICBO
IAO_0000116: 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
IAO_0000117: PERSON: Alan Ruttenberg
IAO_0000117: PERSON: Bjoern Peters
IAO_0000412: obi.owl

plan specification
type: Class
subclass of: directive information entity
subclass of: Restriction
  on property: has part
  some values from: objective specification
subclass of: Restriction
  on property: has part
  some values from: action specification
IAO_0000111: plan specification
IAO_0000112: PMID: 18323827.Nat Med. 2008 Mar;14(3):226.New plan proposed to help resolve conflicting medical advice.
IAO_0000114: ready for release
IAO_0000115: 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.
IAO_0000116: 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.
IAO_0000116: 2014-03-31: A plan specification can have other parts, such as conditional specifications.
IAO_0000116: Alternative previous definition: a plan is a set of instructions that specify how an objective should be achieved
IAO_0000117: Alan Ruttenberg
IAO_0000119: OBI Plan and Planned Process branch
IAO_0000119: OBI_0000344
IAO_0000412: obi.owl
comment: 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

planned process
type: Class
equivalent class: Restriction
  on property: realizes
  some values from: Restriction
    on property: concretizes
    some values from: plan specification
subclass of: process
IAO_0000111: planned process
IAO_0000112: Injecting mice with a vaccine in order to test its efficacy
IAO_0000114: ready for release
IAO_0000115: A processual entity that realizes a plan which is the concretization of a plan specification.
IAO_0000116: '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.)
IAO_0000116: 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.
IAO_0000117: Bjoern Peters
IAO_0000119: branch derived
IAO_0000232: 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)
IAO_0000232: 6/11/9: Edited at workshop. Used to include: is initiated by an agent
IAO_0000412: obi.owl

example to be eventually removed

metadata complete
IAO_0000115: 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.

organizational term
IAO_0000115: term created to ease viewing/sort terms for development purpose, and will not be included in a release
IAO_0000117: PERSON:Alan Ruttenberg

ready for release
IAO_0000115: 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."

metadata incomplete
IAO_0000115: Class is being worked on; however, the metadata (including definition) are not complete or sufficiently clear to the branch editors.

uncurated
IAO_0000115: Nothing done yet beyond assigning a unique class ID and proposing a preferred term.

pending final vetting
IAO_0000115: 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.

to be replaced with external ontology term
IAO_0000115: Terms with this status should eventually replaced with a term from another ontology.
IAO_0000117: Alan Ruttenberg
IAO_0000119: group:OBI

requires discussion
IAO_0000115: 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.
IAO_0000117: Alan Ruttenberg
IAO_0000119: group:OBI