WFS 1.1.0 (wfs.xsd) Change Request - Correct namespace errors
OGC Doc 05-073r1
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
WFS 1.1.0 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
Recom. Paper
Title:
Correct two namespace errors
Source:
William Kammersell, BBN Technologies
Work item code:
Category:
Other
Date: 2005-08-31
F
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:
The schema wfs.xsd (found at http://schemas.opengis.net/wfs/1.1.0/wfs.xsd) has
two critical errors. On line 32, type is “wfs:ServiceType”. However, no such type
exists in the wfs namespace. Also, on lines 334 and 344 there is a base with
value “NMTOKEN”. This value needs a namespace, however.
Summary of change: Change the type on line 32 from “wfs:ServiceType” to “ows:ServiceType”. This
matches the type on line 155 and resolves to a valid element. Lines 334 and
344 should also be changed to have a valid namespace for “NMTOKEN”. I am
unsure what that namespace should be, but another solution is to add a
NMTOKEN to wfs.xsd and change lines 334 and 344 to
“wfs:NMTOKEN”.According to the WFS Implementation Specification (04-094,
p.82) the namespace should be xsd. So, change lines 334 and 344 from
“NMTOKEN” to “xsd:NMTOKEN”.
Consequences if
not approved:
The wfs.xsd schema is invalid because there are references to wfs:ServiceType
and NMTOKEN, which currently do not exist. Fixing these namespaces will
resolve the targets for these references.
Clauses affected:
wfs.xsd
Other specs
Affected:
X Other core specifications
Abstract specifications
Recommendation Papers
Other comments:
1. This change request is part of a series of critical, yet simple, change
requests that I am submitting for the WFS schema implementation.
Drafts for WFS 1.1.1
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
WFS 1.1.0 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
Recom. Paper
Title:
Correct two namespace errors
Source:
William Kammersell, BBN Technologies
Work item code:
Category:
Other
Date: 2005-08-31
F
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:
The schema wfs.xsd (found at http://schemas.opengis.net/wfs/1.1.0/wfs.xsd) has
two critical errors. On line 32, type is “wfs:ServiceType”. However, no such type
exists in the wfs namespace. Also, on lines 334 and 344 there is a base with
value “NMTOKEN”. This value needs a namespace, however.
Summary of change: Change the type on line 32 from “wfs:ServiceType” to “ows:ServiceType”. This
matches the type on line 155 and resolves to a valid element. Lines 334 and
344 should also be changed to have a valid namespace for “NMTOKEN”. I am
unsure what that namespace should be, but another solution is to add a
NMTOKEN to wfs.xsd and change lines 334 and 344 to
“wfs:NMTOKEN”.According to the WFS Implementation Specification (04-094,
p.82) the namespace should be xsd. So, change lines 334 and 344 from
“NMTOKEN” to “xsd:NMTOKEN”.
Consequences if
not approved:
The wfs.xsd schema is invalid because there are references to wfs:ServiceType
and NMTOKEN, which currently do not exist. Fixing these namespaces will
resolve the targets for these references.
Clauses affected:
wfs.xsd
Other specs
Affected:
X Other core specifications
Abstract specifications
Recommendation Papers
Other comments:
1. This change request is part of a series of critical, yet simple, change
requests that I am submitting for the WFS schema implementation.
Drafts for WFS 1.1.1