SensorML 2.0 change request - Use more ISO terms
Open Geospatial Consortium
Document OGC 07-101
CR-Form-v3
CHANGE REQUEST
SensorML CR ?
-
rev
Current version:
1.0
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 change request - Use more ISO terms
Source:
Arliss Whiteside
Work item code:
Category:
Other
Date: 2007-10-16
C
(Changes functional names)
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)
Reason for change:
OGC Implementation Specifications should use all relevant terms
already specified in the OGC Abstract Specification, which includes ISO
19111, 19115, 19119, and 19123.
Summary of change: Change some terms in the SensorML specification to be consistent with
terms with the same meanings already specified in the OGC Abstract
Specification, including change “Process” to “Operation” throughout
specification
Consequences if
not approved:
Continued lack of using all relevant terms already specified in the OGC
Abstract Specification and used in other Implementation Specifications,
producing reader confusion
Clauses affected:
Most
Other specs
Affected:
Supporting Doc.
Other comments:
Status
Disposition
Other core specifications
Abstract specifications
Best Practices Document
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
1
OGC 07-101
Change #1: Change “Process” to “Operation”
Specific change: Change the word “Process” to “Operation” throughout the SensorML
specification, including in compound names such as ProcessModel and ProcessChain, and
edit the surrounding text as needed for consistency
Background: The term “Process” is not used in the OGC Abstract Specification with a
meaning similar to its use in SensorML. The term “Operation” is used in ISO 19119 and
19111 (in compound names including CoordinateOperation, SingleOperation,
ConcatenatedOperation, etc.) with essentially the same meaning as “Process” in
SensorML.
Explain change: Add following paragraph to Subclause 9.1 (after renumbering suggested
in OGC 07-132) in the specification:
“Some of the communities expected to use SensorML would more easily understand the
term “Process” instead of “Operation”, so “Process” was used in previous versions of the
SensorML specification (in OGC 07-000 and its predecessors). However, the term
“Process” is not used in the OGC Abstract Specification with a meaning similar to its use
in SensorML. The term “Operation” is used in OGC Abstract Specification topics 12 and
2 (in ISO 19119 and 19111, in compound names including CoordinateOperation) with
essentially the same meaning as “Process” in SensorML. Since SensorML is an OGC
document (which may be submitted to ISO/TC 211), the term “Process” has thus been
changed to “Operation” throughout the SensorML specification, including in compound
names such as OperationModel and OperationChain.”
2
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
Document OGC 07-101
CR-Form-v3
CHANGE REQUEST
SensorML CR ?
-
rev
Current version:
1.0
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 change request - Use more ISO terms
Source:
Arliss Whiteside
Work item code:
Category:
Other
Date: 2007-10-16
C
(Changes functional names)
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)
Reason for change:
OGC Implementation Specifications should use all relevant terms
already specified in the OGC Abstract Specification, which includes ISO
19111, 19115, 19119, and 19123.
Summary of change: Change some terms in the SensorML specification to be consistent with
terms with the same meanings already specified in the OGC Abstract
Specification, including change “Process” to “Operation” throughout
specification
Consequences if
not approved:
Continued lack of using all relevant terms already specified in the OGC
Abstract Specification and used in other Implementation Specifications,
producing reader confusion
Clauses affected:
Most
Other specs
Affected:
Supporting Doc.
Other comments:
Status
Disposition
Other core specifications
Abstract specifications
Best Practices Document
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
1
OGC 07-101
Change #1: Change “Process” to “Operation”
Specific change: Change the word “Process” to “Operation” throughout the SensorML
specification, including in compound names such as ProcessModel and ProcessChain, and
edit the surrounding text as needed for consistency
Background: The term “Process” is not used in the OGC Abstract Specification with a
meaning similar to its use in SensorML. The term “Operation” is used in ISO 19119 and
19111 (in compound names including CoordinateOperation, SingleOperation,
ConcatenatedOperation, etc.) with essentially the same meaning as “Process” in
SensorML.
Explain change: Add following paragraph to Subclause 9.1 (after renumbering suggested
in OGC 07-132) in the specification:
“Some of the communities expected to use SensorML would more easily understand the
term “Process” instead of “Operation”, so “Process” was used in previous versions of the
SensorML specification (in OGC 07-000 and its predecessors). However, the term
“Process” is not used in the OGC Abstract Specification with a meaning similar to its use
in SensorML. The term “Operation” is used in OGC Abstract Specification topics 12 and
2 (in ISO 19119 and 19111, in compound names including CoordinateOperation) with
essentially the same meaning as “Process” in SensorML. Since SensorML is an OGC
document (which may be submitted to ISO/TC 211), the term “Process” has thus been
changed to “Operation” throughout the SensorML specification, including in compound
names such as OperationModel and OperationChain.”
2
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.