iao.owl
type: Ontology
default language: en
version info: $Revision$
comment: 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.
imports: protege-dc.owl
imports: ontology-metadata.owl
imports: http://www.ifomis.org/bfo/1.1
imports: ro.owl

has measurement unit label
type: ObjectProperty
type: FunctionalProperty
range: measurement unit label
sub property of: has part

specifically denotes
type: ObjectProperty
IAO_0000114: IAO_0000125
IAO_0000115: 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.
IAO_0000119: Smith, Ceusters, Ruttenberg, 2000 years of philosophy
IAO_0000117: Alan Ruttenberg
IAO_0000112: 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
sub property of: is about

is about
type: ObjectProperty
IAO_0000114: IAO_0000125
IAO_0000117: person:Alan Ruttenberg
IAO_0000112: This document is about information artifacts and their representations
IAO_0000115: a representation is_about anything exactly when some part of the information_artifact denotes the entity
IAO_0000119: Smith, Ceusters, Ruttenberg, 2000 years of philosophy

generically denotes
type: ObjectProperty
IAO_0000119: Smith, Ceusters, Ruttenberg, 2000 years of philosophy
IAO_0000112: The word Boston on a traffic signn in Massachusetts generically denotes the city of Boston
IAO_0000115: g generically 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
sub property of: is about

materially denotes
type: ObjectProperty
sub property of: is about

is quality measurement of
type: ObjectProperty
IAO_0000115: m is a quality measurement of q at t when q is a determinable quality there is a measurement process p that has_output m m has a value part that together with the units of the value of q at t. p is a assay 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. 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. unit of measure is a quality, e.g. the length of a ruler. 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 Example: q = height of barry p is the process using a tape measure extend across the longer part of barry and reading off the number at the far end. v is that number # dimension is height unit of measure is inches We have had a long discussion about denotes versus describes.
IAO_0000116: 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.
sub property of: is about

describes
type: ObjectProperty
sub property of: is about

represents
type: ObjectProperty
sub property of: is about

part of
type: ObjectProperty
IAO_0000116: There is controversy about this relation intended to represent the relation between some arbitrary physical thing that is used as a represention/proxy/pointer to something else

has measurement value
type: DatatypeProperty
type: FunctionalProperty

conditional specification
type: Class
subclass of: information entity about a realizable
IAO_0000114: IAO_0000124
IAO_0000119: OBI branch derived
IAO_0000119: OBI_0000349
IAO_0000117: PlanAndPlannedProcess Branch
IAO_0000111: instruction trigger
IAO_0000115: is information about a realizable that specifies that what should happen if the trigger condition is fulfilled

measurement unit label
type: Class
subclass of: label
IAO_0000114: IAO_0000124
IAO_0000116: remove? See unit of measure.
IAO_0000119: OBI_0000176
IAO_0000115: A measurement unit label is an label that is part of a measurement datum and denotes a unit of measure.
IAO_0000112: Examples of measurement unit labels are liters, inches, weight per volume.
IAO_0000111: measurement unit label
IAO_0000117: person:Alan Ruttenberg

objective specification
type: Class
subclass of: information entity about a realizable
IAO_0000114: IAO_0000124
IAO_0000117: Barry Smith
IAO_0000119: OBI_0000217
IAO_0000117: Alan Ruttenberg
IAO_0000115: An objective specification is an information entity about a realizable entity that describes a 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: Answers the question, why did you do this experiment?
IAO_0000117: Jennifer Fostel
IAO_0000119: OBI Plan and Planned Process/Roles Branch
IAO_0000111: objective specification
IAO_0000112: purpose of a study; support of hypothesis, discovery of new information

narrative object
type: Class
subclass of: IAO_0000030
IAO_0000114: IAO_0000124
IAO_0000119: OBI_0000013
IAO_0000115: A narrative object is an information content entity that is a set of propositions.
IAO_0000112: Examples of narrative objects are reports, journal articles, and patents submission.
IAO_0000116: 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
IAO_0000119: group:OBI
IAO_0000111: narrative object
IAO_0000117: person:Chris Stoeckert

action specification
type: Class
subclass of: information entity about a realizable
IAO_0000117: Alan Ruttenberg
IAO_0000115: An action specification is information about a realizable that describes an action the bearer will take
IAO_0000119: OBI Plan and Planned Process branch
IAO_0000112: Pour the contents of flask 1 into flask 2

artifact
type: Class
subclass of: IndependentContinuant
IAO_0000114: IAO_0000124
IAO_0000115: An artifact is an independent continuant that is the intended output of an objective driven process
IAO_0000116: There is not yet consensus this term

label
type: Class
subclass of: data item
IAO_0000116: http://www.golovchenko.org/cgi-bin/wnsearch#4n
IAO_0000115: 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

software
type: Class
subclass of: plan specification
IAO_0000114: IAO_0000120
IAO_0000119: GROUP: OBI
IAO_0000117: PERSON: Alan Ruttenberg
IAO_0000117: PERSON: Bjoern Peters
IAO_0000117: PERSON: Chris Stoeckert
IAO_0000117: PERSON: Melanie Courtot
IAO_0000115: Series of encoded instructions that can be directly executed by a CPU, or transformed in to a form that can be. For programming texts that are syntactically correct and which are in a language that can be executed by an interpreter this would correspond to the tokenized version of the text stripped of comments.
IAO_0000116: see sourceforge tracker discussion at http://sourceforge.net/tracker/index.php?func=detail&aid=1958818&group_id=177891&atid=886178
IAO_0000111: software

digital entity
type: Class
subclass of: digital quality
IAO_0000114: IAO_0000124
IAO_0000115: 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.
IAO_0000119: OBI_0000261
IAO_0000111: digital entity
IAO_0000119: group:OBI
IAO_0000117: person:Chris Stoeckert

journal article content
type: Class
subclass of: report of results
IAO_0000114: IAO_0000002
IAO_0000115: Journal article content is a narrative object that is the information content encoded in a article published in a serious, scholarly publication, most often peer-reviewed.
IAO_0000119: OBI_0000159
IAO_0000112: Examples of encodings of journal article content 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.
IAO_0000119: group:OBI
IAO_0000111: journal article content
IAO_0000117: person:Alan Ruttenberg
IAO_0000117: person:Chris Stoeckert

information carrier
type: Class
subclass of: Quality
IAO_0000114: IAO_0000125
IAO_0000117: Alan Ruttenberg
IAO_0000115: an information carrier is that quality of an information bearer that imparts the information content
IAO_0000112: The pattern in ink on a page of a paperback novel.
IAO_0000119: Smith, Ceusters, Ruttenberg, 2000 years of philosophy

binary digital entity
type: Class
subclass of: digital entity
IAO_0000114: IAO_0000124
IAO_0000119: OBI_0000244
IAO_0000115: 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.
IAO_0000112: MS Word document, ZIP file, DICOM file, JPEG file
IAO_0000111: binary digital entity
IAO_0000116: digital_entity
IAO_0000119: group:OBI
IAO_0000117: person:Chris Stoeckert

unit of measure
type: Class
subclass of: Quality
IAO_0000114: IAO_0000125
IAO_0000117: Alan Ruttenberg
IAO_0000112: The length of a ruler.
IAO_0000115: a unit of measure is the quality of some material entity compared to which another quality is some multiple of.
IAO_0000119: Smith, Ceusters, Ruttenberg, 2000 years of philosophy

programming language
type: Class
subclass of: plan specification
IAO_0000114: IAO_0000124
IAO_0000119: OBI_0000058
IAO_0000115: 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.
IAO_0000112: R, Perl, Java
IAO_0000119: group:OBI
IAO_0000117: person:Alan Ruttenberg
IAO_0000117: person:Chris Stoeckert
IAO_0000111: programming language

data item
type: Class
subclass of: IAO_0000030
IAO_0000116: 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
IAO_0000115: 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.
IAO_0000117: Jonathan Rees
IAO_0000118: data
IAO_0000118: datum

symbol
type: Class
subclass of: data item
IAO_0000117: Jonathan Rees
IAO_0000116: a smallish, word-like datum...

numeral
type: Class
subclass of: symbol
IAO_0000117: Jonathan Rees
IAO_0000116: a symbol that denotes a number

IAO_0000030
type: Class
subclass of: GenericallyDependentContinuant
subclass of: Restriction
  on property: is about
  some values from: Entity
IAO_0000114: IAO_0000124
IAO_0000112: Examples of information content entites include journal articles, data, graphical layouts, and graphs.
IAO_0000119: OBI_0000142
IAO_0000115: an information content entity is an entity that is generically dependent on some artifact and stands in relation of aboutness to some entity
IAO_0000111: information content entity
IAO_0000116: 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.

integer numeral
type: Class
subclass of: numeral
IAO_0000117: Jonathan Rees
IAO_0000115: a numeral that denotes an integer

scalar measurement datum
type: Class
subclass of: measurement datum
subclass of: Restriction
  on property: has measurement unit label
  min cardinality: 1
subclass of: Restriction
  on property: has measurement value
  min cardinality: 1
IAO_0000116: 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.
IAO_0000115: a scalar measurement datum is a measurement datum that is composed of two parts, a single numeral and a unit label.
IAO_0000112: 10 feet. 3 ml.
IAO_0000117: Alan Ruttenberg

information entity about a realizable
type: Class
subclass of: IAO_0000030
subclass of: Restriction
  on property: is about
  some values from: RealizableEntity
IAO_0000114: IAO_0000124
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_0000115: An information entity about a realizable is an information content entity about a realizable.
IAO_0000117: Alan Ruttenberg

time trigger
type: Class
subclass of: conditional specification
IAO_0000114: IAO_0000124
IAO_0000119: OBI branch derived
IAO_0000119: OBI_0000331
IAO_0000117: PlanAndPlannedProcess Branch
IAO_0000115: revisit?
IAO_0000111: time trigger

conclusion
type: Class
subclass of: narrative object
IAO_0000114: IAO_0000124
IAO_0000119: OBI_0000005
IAO_0000115: A conclusion is a narrative object which can be published in a paper summerizing and interpreting a protocol application.
IAO_0000117: Jennifer Fostel
IAO_0000111: conclusion

dot plot
type: Class
subclass of: report graph
IAO_0000114: IAO_0000002
IAO_0000119: OBI_0000123
IAO_0000115: 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.
IAO_0000112: Dot plot of SSC-H and FSC-H.
IAO_0000111: dot plot
IAO_0000119: group:OBI
IAO_0000117: person:Allyson
IAO_0000117: person:Chris Stoeckert

report graph
type: Class
subclass of: report figure
IAO_0000114: IAO_0000124
IAO_0000119: OBI_0000240
IAO_0000119: group:OBI
IAO_0000115: A report graph is a report figure that presents one or more tuples of information my mapping those tuples in to a two dimensional space in a non arbitrary way.
IAO_0000117: person:Alan Ruttenberg
IAO_0000117: person:Allyson Lister
IAO_0000111: report graph

text based digital entity
type: Class
subclass of: digital document
IAO_0000114: IAO_0000124
IAO_0000115: A text based digital entity is a digital entity that is encoded so that it only contains text characters.
IAO_0000119: OBI_0000132
IAO_0000112: XML file, C++ source code file
IAO_0000116: digital_entity
IAO_0000119: group:OBI
IAO_0000117: person:Chris Stoeckert
IAO_0000111: text based digital entity

rule
type: Class
subclass of: conditional specification
IAO_0000114: IAO_0000124
IAO_0000119: OBI_0500021
IAO_0000116: MSI
IAO_0000119: PRS
IAO_0000117: PRS
IAO_0000115: a rule is an executable which guides, defines, restricts actions
IAO_0000112: example to be added
IAO_0000111: rule

contour plot
type: Class
subclass of: report graph
IAO_0000114: IAO_0000002
IAO_0000119: OBI_0000246
IAO_0000112: Contour plot of SSC-H, FSC-H, and FL1-H.
IAO_0000111: contour plot
IAO_0000116: generically_dependent_continuants
IAO_0000119: group:Flow Cytometry community
IAO_0000117: person:Allyson
IAO_0000117: person:Chris Stoeckert

report figure
type: Class
subclass of: report display element
IAO_0000114: IAO_0000124
IAO_0000115: 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
IAO_0000116: 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
IAO_0000119: OBI_0000027
IAO_0000119: group:OBI
IAO_0000117: person:Alan Ruttenberg
IAO_0000117: person:Allyson Lister
IAO_0000111: report figure

algorithm
type: Class
subclass of: plan specification
IAO_0000114: IAO_0000124
IAO_0000119: OBI_0000270
IAO_0000112: PMID: 18378114.Genomics. 2008 Mar 28. LINKGEN: A new algorithm to process data in genetic linkage studies.
IAO_0000117: Philippe Rocca-Serra
IAO_0000117: PlanAndPlannedProcess Branch
IAO_0000119: adapted from discussion on OBI list (Matthew Pocock, Christian Cocos, Alan Ruttenberg)
IAO_0000111: algorithm
IAO_0000115: an algorithm is a plan 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.

software interpreter
type: Class
subclass of: algorithm
IAO_0000114: IAO_0000124
IAO_0000119: OBI_0000199
IAO_0000115: A software interpreter is a generically dependent realizable entity that takes, as input, some digital entity, and takes action driven by the information content of that digital entity
IAO_0000116: 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
IAO_0000112: R program, Perl interpreter, Java virtual machine
IAO_0000119: group:OBI
IAO_0000117: person:Alan Ruttenberg
IAO_0000117: person:Chris Stoeckert
IAO_0000111: software interpreter

density plot
type: Class
subclass of: report graph
IAO_0000114: IAO_0000002
IAO_0000119: OBI_0000179
IAO_0000115: 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.
IAO_0000112: Density plot of SSC-H and FSC-H.
IAO_0000111: density plot
IAO_0000119: group:Flow Cytometry community
IAO_0000117: person:Allyson
IAO_0000117: person:Chris Stoeckert

report of results
type: Class
subclass of: narrative object
IAO_0000114: IAO_0000002
IAO_0000112: Examples of reports are gene lists and investigation reports. These are not published (journal) articles but may be included in a journal article.
IAO_0000119: OBI_0000099
IAO_0000115: 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.
IAO_0000116: 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
IAO_0000119: group:OBI
IAO_0000117: person:Chris Stoeckert
IAO_0000111: report of results

report display element
type: Class
subclass of: narrative object
IAO_0000114: IAO_0000124
IAO_0000115: 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.
IAO_0000119: OBI_0000001
IAO_0000116: 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
IAO_0000119: group:OBI
IAO_0000117: person:Alan Ruttenberg
IAO_0000117: person:Allyson Lister
IAO_0000111: report display element

binary executable
type: Class
subclass of: digital entity
IAO_0000114: IAO_0000124
IAO_0000115: 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)
IAO_0000119: OBI_0000222
IAO_0000111: binary executable
IAO_0000119: group:OBI
IAO_0000117: person:Jennifer Fostel

source code module
type: Class
subclass of: IAO_0000030
IAO_0000114: IAO_0000124
IAO_0000119: OBI_0000039
IAO_0000115: A source code module is an information content entity that specifies, using a programming language, some algorithm.
IAO_0000112: 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.
IAO_0000119: group:OBI
IAO_0000117: person:Alan Ruttenberg
IAO_0000117: person:Chris Stoeckert
IAO_0000111: source code module

report table
type: Class
subclass of: report display element
IAO_0000114: IAO_0000002
IAO_0000115: 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
IAO_0000119: OBI_0000265
IAO_0000119: group:OBI
IAO_0000117: person:Alan Ruttenberg
IAO_0000117: person:Allyson Lister
IAO_0000111: report table

data format specification
type: Class
subclass of: information entity about a realizable
IAO_0000114: IAO_0000124
IAO_0000119: OBI_0000187
IAO_0000115: A data format specification is the information content borne by the document published defining the specification. blah: for organizing information artifacts. Example: The ISO document specifying what encompasses an XML document; The instructions in a XSD file
IAO_0000119: OBI branch derived
IAO_0000117: PlanAndPlannedProcess Branch
IAO_0000111: data format specification

data set
type: Class
subclass of: IAO_0000030
IAO_0000114: IAO_0000124
IAO_0000119: OBI_0000042
IAO_0000115: A data set is an information content entity that is an aggregate of other information_content_entities that have something in common and are considered to form a unit.
IAO_0000111: data set
IAO_0000119: group:OBI
IAO_0000117: person:Allyson
IAO_0000117: person:Chris Stoeckert

image
type: Class
subclass of: IAO_0000030
IAO_0000114: IAO_0000124
IAO_0000119: OBI_0000030
IAO_0000115: An image is an information content entity which provides a visual representation of for the result of a measurement.
IAO_0000119: group:OBI
IAO_0000111: image
IAO_0000117: person:Allyson
IAO_0000117: person:Chris Stoeckert

plan specification
type: Class
subclass of: information entity about a realizable
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_0000114: IAO_0000124
IAO_0000119: OBI_0000344
IAO_0000115: A plan specification is an information entity about a realizable entity. The specification includes parts such as objective specification, action specifications and conditional specifications. When concretized it is realized in a process in which the bearer tries to achieve the objectives, in part by taking the actions specified.
IAO_0000117: Alan Ruttenberg
IAO_0000116: Alternative previous definition: a plan is a set of instructions that specify how an objective should be achieved
IAO_0000119: OBI Plan and Planned Process branch
IAO_0000112: PMID: 18323827.Nat Med. 2008 Mar;14(3):226.New plan proposed to help resolve conflicting medical advice.
IAO_0000111: plan specification

digital document
type: Class
subclass of: digital entity
IAO_0000114: IAO_0000124
IAO_0000115: 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.
IAO_0000119: OBI_0000195
IAO_0000111: digital document
IAO_0000119: group:OBI
IAO_0000117: person:Jennifer Fostel

measurement datum
type: Class
subclass of: data item
IAO_0000114: IAO_0000124
IAO_0000115: A measurement datum is an information content entity that is a recording of the output of a measurement such as produced by an instrument.
IAO_0000119: OBI_0000305
IAO_0000112: 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,}.
IAO_0000119: group:OBI
IAO_0000111: measurement datum
IAO_0000117: person:Chris Stoeckert

_identifier
type: Class
subclass of: GenericallyDependentContinuant
IAO_0000114: IAO_0000121
IAO_0000116: _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.

version number
type: Class
subclass of: _identifier
IAO_0000114: IAO_0000124
IAO_0000115: 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.
IAO_0000116: 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

serial number
type: Class
subclass of: _identifier
IAO_0000114: IAO_0000124
IAO_0000115: 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.
IAO_0000116: 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 :-)

lot number
type: Class
subclass of: _identifier
IAO_0000114: IAO_0000124
IAO_0000118: batch number
IAO_0000115: 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.

setting datum
type: Class
subclass of: data item
IAO_0000114: IAO_0000124
IAO_0000116: Alan grouped these in placeholder for the moment. Name by analogy to measurement datum.
IAO_0000115: A settings datum is a datum that denotes some configuration of an instrument.

digital quality
type: Class
subclass of: GenericallyDependentContinuant
IAO_0000114: IAO_0000121
IAO_0000116: Need to rework digital entity. Digital quality was suggested by Barry.

material information bearer
type: Class
subclass of: MaterialEntity
IAO_0000115: An information bearer is an artifact, such as a hard drive, upon which an information content entity generically depends.

histogram
type: Class
subclass of: report graph
IAO_0000114: IAO_0000122
IAO_0000115: A histogram is a report graph which is a statistical description of a distribution in terms of occurrence frequencies of different event classes.
IAO_0000119: GROUP:OBI
IAO_0000117: PERSON:Chris Stoeckert
IAO_0000117: PERSON:James Malone
IAO_0000117: PERSON:Melanie Courtot
IAO_0000111: histogram

heatmap
type: Class
subclass of: report graph
IAO_0000114: IAO_0000122
IAO_0000115: 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.
IAO_0000119: GROUP:OBI
IAO_0000117: PERSON:Chris Stoeckert
IAO_0000117: PERSON:James Malone
IAO_0000117: PERSON:Melanie Courtot
IAO_0000111: heatmap

Venn diagram
type: Class
subclass of: report graph
IAO_0000114: IAO_0000122
IAO_0000115: A Venn diagram is a report graph showing all hypothetically possible logical relations between a finite collection of sets.
IAO_0000117: PERSON:Chris Stoeckert
IAO_0000117: PERSON:James Malone
IAO_0000117: PERSON:Melanie Courtot
IAO_0000111: Venn diagram
IAO_0000119: WEB: http://en.wikipedia.org/wiki/Venn_diagram

survival curve
type: Class
subclass of: report graph
IAO_0000114: IAO_0000122
IAO_0000115: 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.
IAO_0000117: PERSON:Chris Stoeckert
IAO_0000117: PERSON:James Malone
IAO_0000117: PERSON:Melanie Courtot
IAO_0000119: WEB: http://www.graphpad.com/www/book/survive.htm
IAO_0000111: survival curve

dendrogram
type: Class
subclass of: report graph
IAO_0000114: IAO_0000122
IAO_0000115: 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.
IAO_0000112: Dendrograms are often used in computational biology to illustrate the clustering of genes.
IAO_0000117: PERSON:Chris Stoeckert
IAO_0000117: PERSON:James Malone
IAO_0000117: PERSON:Melanie Courtot
IAO_0000119: WEB: http://en.wikipedia.org/wiki/Dendrogram
IAO_0000111: dendrogram

scatterplot
type: Class
subclass of: report graph
IAO_0000114: IAO_0000122
IAO_0000115: A scatterplot is a report 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.
IAO_0000117: PERSON:Chris Stoeckert
IAO_0000117: PERSON:James Malone
IAO_0000117: PERSON:Melanie Courtot
IAO_0000119: WEB: http://en.wikipedia.org/wiki/Scatterplot
IAO_0000118: scattergraph
IAO_0000111: scatterplot