Open Geospatial Consortium
OGC Doc 08-115
CR-Form-v3
CHANGE REQUEST
WFS CR 08-115
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: Support of License Information in WFS response
Source: Simon Cox, CSIRO – Exploration & Mining
Work item code: Date: 2008-07-17
Category: C
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: To optionally allow license information to be associated with a WFS response delivered from a non-SOAP WFS service.
Summary of change: Modify the content model for wfs:FeatureCollectionType
<xsd:sequence> <xsd:annotation>
<xsd:documentation>Additional elements after those inherited from
gml:AbstractFeatureCollectionType</xsd:documentation> </xsd:annotation>
<xsd:element name="license" minOccurs="0"> <xsd:annotation>
<xsd:documentation>Optional slot to hold license information applicable to the WFS
response</xsd:documentation> </xsd:annotation>
<xsd:complexType mixed="true"> <xsd:annotation>
<xsd:documentation>Content model is mixed to allow either a plain text or XML encoded license to be
supplied</xsd:documentation> </xsd:annotation>
<xsd:sequence minOccurs="0"> <xsd:annotation>
The OGC Technical Committee Policies & Procedures 05-020r3
</xsd:annotation> <xsd:any>
<xsd:annotation>
<xsd:documentation>Wildcard to allow any XML encoded license to be included</xsd:documentation>
</xsd:annotation> </xsd:any>
</xsd:sequence> </xsd:complexType> </xsd:element>
</xsd:sequence>
Consequences if
not approved: Will restrict use of wfs to applications where no response-specific licensing is required.
Clauses affected: 9.3
Other specs Other core specifications Affected: Abstract specifications
Best Practices Document
Supporting Doc. License Manager Specification - Australian Bureau of Statistics (see attach)
Other comments: 1. Other OWS services which carry an XML response (e.g. CS/W, SOS) may have a similar requirements. A standard model for embedding license information in responses from "REST-based" OWS services should be developed.
2. "License" might be considered a type of "metadata" for the WFS response. A standard extensibility point for associating general metadata with a WFS response might be useful.
Status
Disposition
How to create CRs using this form: Comprehensive
information and tips about how to create CRs can be found at:
Fill out the above form. The symbols above marked
contain pop-up help information about the field that they are closest to.
Obtain the latest version for the release of the specification to which the change is proposed. Use the MS Word "revision marks" feature (also known as "track
The OGC Technical Committee Policies & Procedures 05-020r3
changes") when making the changes. All Open GIS specifications can be downloaded from the OGC server under
http://www.opengeospa tial.org/specs/
If a Word version of the document is not available, please contact the TCC or his designee.
With "track changes" disabled, paste the entire CR form (use CTRL-A to select it) into the specification just in front of the clause containing the first piece of changed text. Delete those parts of the specification that are not relevant to the change request.