• Tidak ada hasil yang ditemukan

OWS Common change request: add schemalocation for XML namespace

N/A
N/A
Protected

Academic year: 2017

Membagikan "OWS Common change request: add schemalocation for XML namespace"

Copied!
2
0
0

Teks penuh

(1)

Open Geospatial Consortium

OGC Doc 07-141

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 Other

Title:  OWS Common change request: add schemalocation for XML namespace

Source:  Peter Schut, WPS RWG

Work item code:Date:  2007-10-22

Category: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

<import namespace="http://www.w3.org/XML/1998/namespace"/> with

<import namespace=" http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/>

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.

(2)

The OGC Technical Committee Policies & Procedures 05-020r3

Other specs  Other core specifications  Affected: Abstract specifications

Best Practices Document

Supporting Doc.  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.

Other comments:Status

Disposition

Referensi

Dokumen terkait

An XML Schema that implements a minor revision of a standard SHALL incorporate all prior revisions of the same major version by importing the all-components schema document for

An example of the intended usage for the nilValue element in the context of a Coverage range parameter encoding is provided in the following instance

endpoints of its operation requests in order to give browser-based client software the ability to make many requests to the server at once (bypassing the browser's

Summary of change:  Provide guidance to specification editors that all elements and attributes in XML schemas must be fully documented, and the specification document should not

In the event that an OWS server encounters an error servicing an operation request, it shall return an exception report message as specified in Clause 8. The allowed exception

Reason for change:  The schema wfs.xsd (found at http://schemas.opengis.net/wfs/1.1.0/wfs.xsd ) references an element “ows:Capabilities” on line 164. However, no such

1) An XML schema for a link element based on RFC 5988.. end up looking very similar to the link element used in ATOM.!. 2) A JSON schema to encoding links based on

In addition, it describes an XML- Schema based implementation of the UML information models defined in OWS-8 engineering report “Information Model for Moving Target Indicators