Open Geospatial Consortium
Document OGC 08-020
CR-Form-v3
CHANGE REQUEST
SWE Common 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 Impl Stand X Best Practices Paper Other
Title: Improve documentation in various sections of the specification
Source: Alexandre Robin, Ingo Simonis, Johannes Echterhoff, Michael E. Botts
Work item code: Date: 2008-02-25
Category: F (Add needed information)
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: Several aspects of the SWE Common Encodings are not very well documented (or not at all) leading to confusions/misunderstanding by
implementers. This is in particular true of the binary encodings, variable array size, local and reference frames and semantics concepts.
Summary of change: Add clear examples and more explanations for these features.
Consequences if
not approved:
Implementers may not fully understand all SWE Common features and could misuse them leading to incompatible implementations.
Clauses affected: 8, 9 (currently in SensorML 1.0 Specification)
OGC 08-020
Other specs Other core specifications
Affected: Abstract specifications
Best Practices Papers
Supporting Doc.
Other comments:
Status NEW
Disposition
OGC 08-020
Change Request Description
1. Document use of ASCII, XML and binary encodings and the mappings existing between the structure description, the component encoding options and the actual data stream structure. Diagrams should be added to clearly illustrate these concepts.
2. More precise documentation should be added to explain the concept of local frame, reference frame and the relation to axisCode that can be assigned to scalar
components. More examples of Vectors are needed.
3. Document the concept of variable size array and how it can be defined either implicitly by not specifying an elementCount value OR referencing another component (necessarily a Count) holding the array size.
4. Add constraints in schema (xs:key) to enforce unicity of DataRecord fields and add statement in the documentation to explain why fields should have unique names.
