OWS Common change request: add schemalocation for XML namespace

OGC Doc 07-141

Open Geospatial Consortium

CR-Form-v3

CHANGE REQUEST
WSC 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

Title:

 OWS Common change request: add schemalocation for XML namespace

Source:


 Peter Schut, WPS RWG

Work item code: 
Category:

Other

Date:  2007-10-22

 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 current OWS Common ExceptionReport.xsd schema references an
obsolete version of the XML schema, and therefore does not validate properly if
an XML validator actually attempts to import the XML schema at this obsolete
location. As a consequence other OGC schemas cannot import the exception
report schema.
This validation problem exists in the XML validators that the OGC has
standardized on to schemas (xerces-j and xsv). It does not occur in the latest
(v2008) XMLSpy, although it occurs in the 2006 version.

Summary of change:  In
ows/1.1.0/owsExceptionReport.xsd
replace


with




Consequences if
not approved:

 XML schema validation with xerces-j and xsv will fail for WPS and other OGC
standards which attempt to use the Exception Report portion of OWS Common.
Potential for OGC standards to look poor.

Clauses affected:

 None. Just the schema.

The OGC Technical Committee Policies & Procedures 05-020r3
Other specs
Affected:
Supporting Doc.

Other comments:
Status
Disposition


Other core specifications

Abstract specifications
Best Practices Document
 Attempting to import W3C namespace at
="http://www.w3.org/XML/1998/namespace" returns an XML document which
indicates where the XML schema is located, as indicated in the correction
specified above.






Last Revision Date: 2 December 2017

Page2