SensorML CR - improve interface specification
OGC Doc 08-146
Open Geospatial Consortium
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
Title:
SensorML CR – Improve Interface Specification
Source:
University of Alabama in Huntsville
Work item code:
Category:
Other
Date: 2008-09-10
C
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:
In order to possibly support plug-n-play of sensor systems, improvements to the
“interface” property for sml:System and sml:Component are anticipated. The
current SensorML version supports the OSI stack, with additional support for
data encodings.
Summary of change: Test and examine the interface specification for possible improvements. Improve
the linking of data component and encoding descriptions with the interface.
Consequences if
not approved:
The current version of SensorML is more clumsy than necessary when one wishes
Clauses affected:
Other specs
Affected:
Supporting Doc.
Other comments:
Status
to connect particular interface components and encoding with the data components
specified in “outputs”. Improving these connections and making them more robust
would encourage the use of SensorML descriptions for supporting plug-n-play of
sensors and components, as well as allow one to be able to immediately be able to
interpret data streaming from the sensor, as well as understand the required data
sytructure for tasking and configuring the sensor.
Other core specifications
Abstract specifications
Best Practices Document
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)
The OGC Technical Committee Policies & Procedures 05-020r3
Disposition
Last Revision Date: 2 December 2017
Page2
Open Geospatial Consortium
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
Title:
SensorML CR – Improve Interface Specification
Source:
University of Alabama in Huntsville
Work item code:
Category:
Other
Date: 2008-09-10
C
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:
In order to possibly support plug-n-play of sensor systems, improvements to the
“interface” property for sml:System and sml:Component are anticipated. The
current SensorML version supports the OSI stack, with additional support for
data encodings.
Summary of change: Test and examine the interface specification for possible improvements. Improve
the linking of data component and encoding descriptions with the interface.
Consequences if
not approved:
The current version of SensorML is more clumsy than necessary when one wishes
Clauses affected:
Other specs
Affected:
Supporting Doc.
Other comments:
Status
to connect particular interface components and encoding with the data components
specified in “outputs”. Improving these connections and making them more robust
would encourage the use of SensorML descriptions for supporting plug-n-play of
sensors and components, as well as allow one to be able to immediately be able to
interpret data streaming from the sensor, as well as understand the required data
sytructure for tasking and configuring the sensor.
Other core specifications
Abstract specifications
Best Practices Document
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)
The OGC Technical Committee Policies & Procedures 05-020r3
Disposition
Last Revision Date: 2 December 2017
Page2