2005-12-20 om: Observations and Measurements OGC Document; In the comments the following "namespaces" were used to indicate author or source of the comment: fp: Florian Probst; ag: Andrew Gordon; mw: Merian-Webster Online (http://www.m-w.com); aw: Answer.com (http://answer.com); wp: Wikipedia (http://www.wikipedia.org); seegrid:(https://www.seegrid.csiro.au/twiki/bin/view/Xmml/ObservationsAndMeasurements); ISO 19###: International Organization for Standardizationt; om: (Section 6.4) ResultMeasure is a variation of the standard Measure, which is a number with a scale [ISO 19103, ISO 19136]. fp: Renamed vom Observation to SimpleObservation. This allows to rename AbstractObservation to Observation. --> The notion "abstract" is useful in UML to denote classes with no instances. Classes with no instances are not usefull in ontologies om: (Section 6.6.2) A CommonObservation is an alternative to ComplexObservation, using the “Data” components from SensorML for its result type and resultDefinition. om: (Listing 33 - note) CommonObservation is a specialized observation type in which the value of the result property is a DataValue from the SWE Common components. seegrid: Generic concrete observation type in which the result is a tuple or record, and the record schema is provided in a adjacent result definition property. 1 0 om: (Listing 23) A definition of how to unpack an array and assign atomic values to components of map vectors. The array must correspond with an N-dimensional grid. Each map describes the values of the independent variable for one axis of the grid. The order of maps defines the iteration sequence within the grid, i.e. the rule for assigning the control variables to the items in an ordered list corresponding with a grid. fp: changed super class from SimpleProcedure to Object -> if an instrument is seen as procedure, it is ontologically problematic to assign a reference number to it. (--> datatype property "hasSerialNumber) om: (Section 6.5.3) Instrument adds a serialNumber denoting the instrument instance. 1 fp: renamed from ProcedurePackeage om: (Section 6.5.3) A ProcedurePackage is a single procedure composed of elements each responsible for a different observed property. A ProcedurePackage generates a complex observation representing a compound phenomenon. om: (Section 6.6.3) An array not tied to a conceptual object. om: (Section 6.5.3) SurveyProcedure carries a set of properties related to geodesy om: (Section 6.5.2) A CompoundPhenomenon has several components, whose count is indicated by the dimension. CompoundPhenomenon is an abstract class. Two concrete specializations are provided. fp: in this ontology, there are no sub classes of stereotype, but five individuals. fp: (?) A stereotype represents a variation of an existing model element with the same form (such as attributes and relationships) but with different intent. Generally a stereotype represents a usage distinction. A stereotyped element may have additional constraints, beyond those of the base element, as well as a distinct visual image. ISO19107: (Page 17) Most entities in a UML model can be described by a "stereotype" which is included near the name of the object and enclosed in guillemets "«" and "»". The stereotype allows the model to extend UML to include descriptions of elements of the model. fp: Changed Measurement to SimpleMeasurement in order to shift the class Measurement as intermediate class between Observation and all other XMeasurement classes. om: (Section 4.17) An observation whose result is a measure, a single number with a scale (ResultMeasure) om: (Section 6.2) While the term “observation” is used here for the general concept, Measurement is reserved for cases where the result is a numeric quantity. om: (Section 6.5.3) CalculationProcedure uses the inherited description, remarks and method properties to give details. fp: class Location was renamed to LocationDestription. The sub classes are EX_GeographicDescription and GN_Object. Both can be understood as descriptions / representations and not as real word entites. om: (Section 6.3) A location value is a spatial object described using coordinates (GM_Object) or a named place (EX_GeographicDescription). The location will normally refer to the location of the instrument or observer at the time of the observation. fp: Is a collection a sub class of event? A collection is a social object -->non-physical object --> non-physical endurant om: (Page_12) ObservationCollection is specialized from Event, being a collection of member observations. There are no constraints on the relationships between member observations. om: (Section 6.6.2) The most general way to combine observations where the result is split between component observations. Each component of the result is modelled as a separate observation. om: (Section 6.4) ObservationCollection is specialized from Event, being a collection of member observations. There are no constraints on the relationships between member observations. 1 om: (Section 6.3) A named place. om: (Listing 33) DataValue is the value of the result property. om: (Section 6.6.1) ScopedName is the result of a CategoryObservation, it is a term scoped by a vocabulary or authority. wp: In computer programming in general, a scope is an enclosing context. Scopes have contents which are associated with them. om: (Section 6.6.2) A CompositeObservation is a specialization of ObservationCollection, with the constraint that at least one of featureOfInterest, time or phenomenon is constant across all members. om: (Listing 32) Functionally equivalent to ComplexObservation. om: (Section 6.6.2) An ordered list of atomic values. om: (Section 6.6.2) The result of a ComplexMeasurement is a NumericRecord, which is an ordered set of numbers each with a scale. ISO 19103: (Page 18) Arrays used in programming languages are sequences that can be directly indexed by an offset from the beginning of the sequence. A Sequence is a Bag-like structure that orders the element instances. fp: Renamed the class Phenomenon with ObservedProperty --> in an DOLCE alignment the super class will be Quality. ag: "the observed property is usually a phenomenon" the word usually is not very precise. Are there any examples of observed properties that are not phenomena? om: (Section 6.3) The value that identifies or describes the Phenomenon for which the observation result provides an estimate of its value that is the primary result of observation. om: (Section 6.5.2) The observed property is usually a phenomenon, the estimate of whose value is the primary result of the observation. om: (Section 6.5.2) The basic Phenomenon class is a definition with an identifier. The description property may be used to hold a textual definition, or to carry a pointer to a more authoritative source. fp: introduced class Measurements and SimpleMeasurements in oder to extent the taxonomic structure and thus increase distinction between kinds of measurement and kinds of observations. 2 om: (Section 6.6.1) A RangeMeasurement is a variant measurement with two results describing an interval or range. Both results are RelativeMeasureType. om: (Section 6.3) Temporal Object that includes both temporal primitives and aggregates. om: (Section 6.3) A spatial object described using coordinates. 1 1 1 0 1 fp: changed from AbstractObservation to Observation see comment for the class Feature. om: (Listing 31) Basic type for observations. Concrete observations must extend this type with a "result" of the appropriate type. 1 om: (Section 6.6.3) Describes a single item in a record and it is characterized by property (indicated by an association with a Phenomenon), representation (how the item is encoded) and optional quality and procedure properties allow item-specific metadata to be provided. om: (Listing 23) Description of a scalar property with its representation and scale and (optional) quality indicators. om:(Section 6.61) An observation with a result that a ScopedName, which is a term scoped by a vocabulary or authority. ISO 19136 p356: UML classes with stereotype <<FeatureType>> derive directly or indirectly from gml:AbstractFeatureType. If the class is a class without supertype, it extends directly gml:AbstractFeatureType; otherwise it extends its supertype which shall be derived from gml:AbstractFeatureType (again, directly or indirectly). fp: This class was renamed from Abstract Feature to Feature. In software engineering it is a useful modeling construct to have "abstract" classes, which have no instances. In DL-based ontology engineering it is not possible to have "abstract" classes without instances which in turn have "concrete" sub classes which do have instances. The only explicit sub class relation in the O&M UML diagrams is to the class Station. For all other Feature (Types) this relation is implicitly assumes (?). ISO 19136: (Page 336) An abstract feature provides a set of common properties, including id, metaDataProperty, name and description inherited from AbstractGMLType, plus boundedBy. A concrete feature type must derive from this type and specify additional properties in an application schema. A feature must possess an identifying attribute ('id' - 'fid' has been deprecated). ISO 19136: (Page 32) The content model for gml:AbstractFeatureType adds two specific properties suitable for geographic features to the content model defined in gml:AbstractGMLType. The value of the gml:boundedBy property describes an envelope that encloses the entire feature instance, and is primarily useful for supporting rapid searching for features that occur in a particular location. om: (Section 8.1) A feature type is defined in terms of its set of properties, including attributes, association roles, and behaviors, as well as generalization and fp: this class was renamed from abstract feature to feature. In software engineering the notion of "abstract" provides a useful modelling construct. In ontology engineering ist is rather problematic to use the notion "abstract". Especially if the abstract class (no instances) has concrete sub classes (with instances). specialization relationships, and constraints (ISO 19109). ISO19101: (Page_3) Abstraction of real world phenomena. ISO19101: (Page_3) A feature may occur as a type or an instance. Feature type or feature instance shall be used when only one is meant. ISO19107: (Page_143) A feature may occur as a type or an instance. Feature type or feature instance should be used when only one is meant. ISO19110: (Page_2) Abstraction of real world phenomena with common properties. ISO 119103: (Page 18) Arrays used in programming languages are sequences that can be directly indexed by an offset from the beginning of the sequence. fp: renamed from Procedure Sequence om: (Section 6.5.3) A ProcedureSequence is a single procedure composed of an ordered set of processingSteps, the value of each being a Procedure. A ProcedureSequence generates a single observation. 1 om: (Section 6.6.3) RecordDefinition describes a record of the specified recordLength, in terms of an explicit set of ordered components. 1 om: (Section 6.3) A procedure is used to generate the observation. om: (Section 6.5.3) The value of the procedure property is the description of a procedure. This may be quite elaborate, and may involve the description of multiple processing steps, with various inputs, calibrations, and predecessor observations used in particular stages. om: (Section 6.5.3) A “procedure” is generally an abstraction, for which the description or catalogue entry provides the canonical object. Hence, the abstract superclass Procedure is stereotyped <<ObjectType>>, and in the model shown here is derived from the GML Definition class. 0 om: (Section 6.6.2) Its result is a Record, which is an ordered list of atomic values. A record instance should provide a means of obtaining a description of its structure, but in the context of the ComplexObservation feature type a resultDefinition property provides a slot where the RecordSchema may be given explicitly. The RecordSchema must provide the meaning (name) of elements in the record, their order, and scale (for numbers) or scope (for terms). TODO: this class seems to have many possible super classes. TODO: get defintion GML 3.1. p.530 “F.2.3.3 GML Object Types Every GML object type shall be mapped to a UML class. If the object type directly or indirectly derives from gml:AbstractFeatureType, the stereotype of the class shall be <<FeatureType>>, otherwise the stereotype shall be <<ObjectType>>. The name of the class shall be the same as the name of the global element of the GML object type. The class shall be abstract, if and only if the GML object type is abstract. If the GML object type is derived from another GML object type, then the class inherits from the corresponding superclass. If the base type is defined in the GML application schema or another imported GML application schema, then the superclass is the class corresponding to this GML object type. If the base type is defined in the GML namespace, then the superclass is determined by Table 21. ISO 19103: (Page 6) Object is a entity with a well-defined boundary and identity that encapsulates state and behaviour. State is represented by attributes and relationships, behaviour is represented by operations, methods, and state machines. An object is an instance of a class. See: class, instance. 1 om: (Section 7.3.1) "...an observation station, which is a simple point-located feature used for observations" om: (Listing 30) A "Station" is an identified position (0-D geospatial feature). It may be revisited for various purposes, in particular to retrieve multiple specimens or make repeated or complementary observations. The position property of the station provides the value of the position property of observations an specimens associated with the station. The procedureHosted property allows the user to point to one or more sensors or other procedures that are relevant to this station. By using the Station feature, this position information and any metadata associated with it may be encoded in one place, i.e. normalised, and then re-used _by reference_ on other feature instances associated with it. om: (Section 6.6.2) An ordered set of numbers each with a scale. om: (Section 6.3) A number of persons or organisations that may be identified as responsible for the Event. om: (Listing 23) Abstract element used as head of a substitution group for axis and record definitions. ag: Temporaray superclass of all result types (basically a container until the hierarchy of result types is determined) om: (Section 6.3) The type of the result is variable and distinguish observation types according to the result type. In order to avoid some practical difficulaties associated with derivation by restriction, the result attribute does not appear directly on the abstract superclass AbstractObservation, but all concrete observation classes derived from AbstractObservation MUST add an attribute called result, having an appropriate type. mw: Etymology: Middle English, from Medieval Latin resultare, from Latin, to rebound, from re- + saltare to leap; to proceed or arise as a consequence, effect, or conclusion; to have an issue or result. aw: To come about as a consequence; in mathematics is the quantity or expression obtained by calculation. om: (Section 6.5.3) A SimpleProcedure is characterized by a method, and the resultQuality associated systematically with the results of observation made using this procedure. The “method” will typically be a code from some catalogue. 0 0 om: (Section 6.3) Feature type characterized by a time whose value is a temporal object (TM_Object), a location whose value is either a spatial object described using coordinates (GM_Object) or a named place (EX_GeographicDesription). 0 om: (Section 6.6.3) Each member of an ObjectArray is (a pointer to) an object described elsewhere, such as elements of a station array, or elements of a temporal aggregate. 1 om: (Section 6.5.2) A ConstrainedPhenomenon modifies a base phenomenon by adding singleConstraints, each specifying a value on some secondary axis. fp: this indicates an understanding of Phenomenon in terms of a quality space! If this is intended, then the definitions in the O&M text are much too broad. fp: the class PhenomenonSeries was renamed to MulitPhenomenon. --> there is not kind-of relationship between series and phenomenon! om: (Section 6.5.2) A PhenomenonSeries applies one or more constraintLists to the base phenomenon, each providing a set of values for a single secondary axis. 1 om: (Section 6.5.2) A CompositePhenomenon is composed of a set of component phenomena. The components may not be related to each other, though useful compound phenomena would usually have some semantic coherence. The optional base phenomenon allows for the CompositePhenomenon to be generated by adding components to a base. 1 1 0 om: (Section 1) Observation is an event with a result which has a value describing some phenomenon. An observation uses a procedure to determine the value, which may involve a sensor or observer, analytical procedure, simulation or other numerical process. The observation pattern and feature is primarily useful for capturing metadata associated with data capture. om: (Section 6.4) Observation is a generic concrete class for observations where the result type is shown as anyType. mw: Etymology: Middle French, from Latin observation-, observatio, from observare. An act or instance of observing a custom, rule, or law: an act of recognizing and noting a fact or occurrence often involving measurement with instruments; a record or description so obtained. A judgment on or inference from what one has observed; broadly. aw: An inference or a judgment that is acquired from or based on observing. wp: Observation basically means watching something and taking note of anything it does. om:(Section 6.6.3) ItemSeriesDefinition describes a record of the specified recordLength, in which all items share the same representation, quality and procedure. om:(Listing 23) Description of a series of scalar properties with a common representation and scale and (optional) quality indicators. Controls the number of procedures used in a procedure package. Contorls the number of CI_ResponsiblesParties that are responsible for an Event. Controls the number of AbstractObservations that are part of an ObservationCollection Controls the type of result a specific observation may have. Determines the number of events taking place after a given event (as determined by the Event's time property.) Determines the position of a Station Determines the Abstarct Feature that is the target of an Abstract Observation Controls the number of Arrays mapped to a GridDefinition. Controls the number of AbstarctObservations generated by a Procedure. Determines the Location of an event. Determines which procedure is used to generate an observation. Contaols the number and order of Procedures that compose a ProcedureSequence Controls the number of phenomena that compose a specialized phenomenon An indication of an observations event-specific quality (optional.) fp: new O&M version: rename quality --> resultQaulity Determines what coordinate system is used to locate an event. Controls the number of phenomena that may compose a composite phenomenon Controls the number of procedures hsoted by a Station. original O&M name: procedureHosted Determines the Phenomenon observed by an AbstractObservation. Determines the number of events taking place after a given event (as determined by the Event's time property.) Controls which property of a phenomenon is described by an ItemDefinition.