Change Requests | OGC

(1)

Open Geospatial Consortium

OGC Doc 08-145

CR-Form-v3

CHANGE REQUEST



_{SensorML CR ?}

 rev

_-

 Current version: 1.0.1 

For

HELP

on using this form, see bottom of this page or look at the pop-up text over the symbols.

Proposed change affects:  AS Imp Spec X Best Practices Paper Other

Title:  SensorML CR – Improve Inheritance

Source:  University of Alabama in Huntsville

Work item code:  Date:  2008-09-10

Category:  B

Use one of the following categories:

F (Critical correction)

A (corresponds to a correction in an earlier release)

B (Addition of feature),

C (Functional modification of feature)

D (Editorial modification)

Detailed explanations of the above categories can be found in the TC Policies and Procedures.

Reason for change:  It is important that one can describe a sensor component type and allow another SensorML document to specify that it is of that type, thereby inheriting all properties of that document while adding additional properties. This will for instance allow one to create a SensorML instance describing a particular model of a sensor, and allow another SensorML instance to specify that is of that sensor type, and thus inherit all properties of that sensor model. Additional properties such as serial number, location, or owner can then be added without having to duplicate all information in the sensor model type.

Summary of change:  Add a property element named “typeOf” which can take any SensorML ProcessType or a reference (through xlink:href) to a ProcessType. It is anticipated that SensorML instances will typically use a reference to the type description resulting in reuse of descriptions and more compact XML. The typeOf property should be interpreted to mean that all properties of the typeOf Object also apply to the current instance.

Consequences if 

not approved: The current version of SensorML somewhat supports inheritance by wrapping_{components up in a system. This is not only philosophically incorrect, but clumsy}

and excessively verbose.

Clauses affected: 

Other specs  Other core specifications 

Affected: Abstract specifications Best Practices Document

(2)

The OGC Technical Committee Policies & Procedures 05-020r3

Other comments:  This is a minor change which does not affect backwards compatibility, while providing significant benefits. It is suggested that it be released quickly as a slight version change to 1.0.1 (e.g. 1.0.2)

Status 

Disposition 