- From: Roger L. Costello <costello@mitre.org>
- Date: Sun, 06 Jul 2003 11:12:03 -0400
- To: www-rdf-interest@w3.org
- CC: "Thomas B. Passin" <tpassin@comcast.net>, "Costello,Roger L." <costello@mitre.org>, b.fallenstein@gmx.de, jon@spin.ie
Hi Folks,
I have incorporated Benja's and Tom's comments, and added a few of my
own. Comments? /Roger
-----------------------------------------------------------------
Conceptual Model:
TangibleObject
physicalProperty
PhysicalProperty
measurement
Measurement
measurementValue
MeasurementValue
numericalValue
unitSpecification
precision
source
... (any other measurement metadata)
-----------------------------------------------------------------
Conceptual Model Applied to a TangibleObject which has a length:
TangibleObject
length
Length
measurement
LengthMeasurement
value
LengthValue
number
units
precision
source
... (any other measurement metadata)
-----------------------------------------------------------------
Conceptual Model Property Hierarchies:
physicalProperty
|
---------------------------------
| |
lengthProperty areaProperty
| |
------------------------- -------------
| | | | | |
length width height thickness area size
and:
numericalValue unitSpecification
| |
number units
-----------------------------------------------------------------
Conceptual Model Class Hierarchies:
PhysicalProperty Measurement Value
| | |
---------------- LengthMeasurement MeasurementValue
| | |
Length Area LengthValue
-----------------------------------------------------------------
Concrete Example that Conforms to the Conceptual Model:
<River rdf:ID="Yangtze">
<length>
<Length>
<measurement>
<Measurement>
<value>
<Value>
<number>6300</number>
<units rdf:resource="#LengthInKilometers"/>
</Value>
</value>
<precision>(+/-)10km</precision>
<source>OGC</source>
</Measurement>
</measurement>
</Length>
</length>
</River>
-----------------------------------------------------------------
Conceptual Model Statements:
M1) A TangibleObject may have zero or more physicalProperties.
M2) A physicalProperty is a kind of Property.
M3) The type of the value of a physicalProperty is a PhysicalProperty.
M4) A lengthProperty is a kind of physicalProperty.
M4a) A areaProperty is a kind of physicalProperty.
M5) A length is a kind of lengthProperty.
M5a) A width is a kind of lengthProperty.
M5b) A height is a kind of lengthProperty.
M5c) A thickness is a kind of lengthProperty.
M5d) A area is a kind of areaProperty.
M5e) A size is a kind of areaProperty.
M6) A PhysicalProperty may be characterized by zero or more measurement
properties.
M7) A Length is a kind of PhysicalProperty.
M7a) A Area is a kind of PhysicalProperty.
M8) The type of the value of a length is a Length.
M8a) The type of the value of a width is a Length.
M8b) The type of the value of a height is a Length.
M8c) The type of the value of a thickness is a Length.
M8d) The type of the value of a area is a Area.
M8e) The type of the value of a size is a Area.
M9) The type of the value of a measurement is a Measurement.
M10) A LengthMeasurement is a kind of Measurement.
M10a) The type of the value of a measurement property of a Length is a
LengthMeasurement.
M11) A LengthMeasurement is characterized by one or more equivalent
(numerical value, units specification) pairs.
Note - This refers to the values in different units, not to the
results of different measurements taken at different times or by
different methods.
M12) A (numerical value, units specification) pair is a kind of
MeasurementValue.
M13) A MeasurementValue may be associated with metadata that include -
a) Accuracy
b) Precision
c) Data set
d) Calculations
e) Algorithms used for the calculation.
f) Relevant publications
g) Source
h) Reported precision (i.e., number of decimal places in the
stated value, which may be different from the precision of
the measurement)
M14) There is at least one method for establishing the equivalence
between each (numerical value, unit specification) pair of interest.
Received on Sunday, 6 July 2003 11:14:11 UTC