Open Geospatial Consortium
Document OGC 09-201r1
CR-Form-v3
CHANGE REQUEST
OWS Common
CR ?
rev-
Current version:1.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 Other
Title: OWS Common change request - Clarify "not empty"
Source: Arliss Whiteside, Keith Pomakis, Steven Keens
Work item code: Date: 2008-12-0409
Category: D
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: NOTE 2 following Table 3 is not as clear as it should be about the meaning of “Character String Type, not empty”.
Summary of change: Edit NOTE 2 following Table 3 to be clearer about the meaning of “Character String Type, not empty”.
Consequences if
not approved:
Continued possible misinterpretation of OGC standards.
Clauses affected: 7.2.1
Other specs Other core specifications
OGC 09-201r1
Affected: Abstract specifications
Best Practices Papers
Supporting Doc.
Other comments: This change request is based on the OGC 06-121r3 version of OWS Common.
Status
Disposition
Edit NOTE 2 at the end of Clause 7.2.1 as follows:
NOTE 2 The data type of many parameters is specified as “Character String type, not empty”. In the
XML Schemas specified herein, these parameters are encoded with the xsd:string type, which allows an empty stringdoes NOTrequire that these strings not be empty. Nevertheless, “not empty” is a normative requirement on the values of the associated parameter, since all contents of these tables are normative.
