This HTML5 document contains 34 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Subject Item

n4:IAO_0000221

rdf:type

owl:ObjectProperty

rdfs:subPropertyOf

n4:IAO_0000136

owl:inverseOf

n4:IAO_0000417

rdfs:label

is quality measurement of

rdfs:domain

n4:IAO_0000109

rdfs:range

n4:BFO_0000019

foaf:topic

n4:IAO_0000417 n4:IAO_0000136 n4:BFO_0000019 n4:IAO_0000109 n11:rdf_load_html_response n4:IAO_0000116 n4:IAO_0000115 n11:this n11:DataCreation n4:IAO_0000117 _:vb664775799

wdrs:describedby

n6:owl n7:owl n13:owl

n4:IAO_0000117

Alan Ruttenberg

n4:IAO_0000115

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

n4:IAO_0000412

n12:owl

n4:IAO_0000111

is quality measurement of

n4:IAO_0000116

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. 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. 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 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 [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.

Subject Item

_:vb664775799

rdf:type

n9:DataAccess

wdrs:describedby

n3:IAO_0000221

n9:performedAt

2024-09-06T09:44:37.627372

n9:performedBy

n11:spongerInstance

n9:accessedService

n4:IAO_0000221