Change Requests by Date

Change Requests are submitted by anyone for any existing or proposed OpenGIS® Standard. The process for public submission of Change Request is rather simple:

Visit the On-line Change Request Form.
Follow the Instructions on the form
- Submitter Contact Information
- Confirmation of Submitter Information
- Input of Change Request
The Change Request will be reviewed (by OGC Staff/SWG)
Change Request will be posted to the page below

Document Title (click to download)	Version	Document #	Editor	Date
KML 2.3 - Addition of Google extensions to the KML Standard	1	11-176	Sean Askay	2011-12-14
Addition of new KML features supported in Google Earth to the KML Standard.
O&M - No OGC Name for SWE*Observations	1	11-167	Arne Broering	2011-12-14
Mappings of SWE*Observation types to OGC names and result types are missing in Table 6.
Implemenation of required valueOf() function will reduce query/filter efficiency.	1	11-177	Panagiotis (Peter) A. Vretanos	2011-12-14
Deprecate valueOf() - i.e., it would still be in the standard in versions 2.x, but client developers would be advised not to use it - and adds a new conformance class based on the old 03-106 proposal.
KML 2.3 Enhancements to KML’s Extension Mechanism	1	11-175	Sean Askay	2011-12-14
Improve schema extension mechanisms to allow greater flexibility for third-party extensions.
Ambiguity in GetRecords TypeNames parameter for ISO Metadata AP 1.0	1	11-174	Enrico Boldrini	2011-12-14
Change is necessary in order to clarify the specification, affecting content of capabilities document and GetRecords requests correcteness, in regard to the correct name for the parameter typeNames ("typeNames" or "typeName"?).
Ambiguity in GetRecords TypeNames parameter for CAT 2.0.2	1	11-173	Enrico Boldrini	2011-12-14
Change is necessary in order to clarify the specification, affecting content of capabilities document and GetRecords requests correcteness, in regard to the correct value for the parameter typeNames ("typeNames" or "typeName"?).
Temporal Constraints for State and Transition UML class in the data model	1	11-149	JeaJun Yoo	2011-10-19
When modeling indoor spaces for some indoor services such as indoor-navigation, we need to consider some temporal constraints when can affect the indoor space model. For an example and more detailed comments, please refer the uploaded file at supporting document field below.
Direction Information for the Transition UML class in the data model	1	11-151	JeaJun Yoo	2011-10-19
When we model indoor spaces for location-based services such as indoor-navigation, we need to consider direction of navigable path (that is, whether a path is one way or not). For example, let¡ ̄s think about security check doors or arrival doors at the airports. A customer can go forward through those doors but cannot go back. Therefore, we need to describe the direction of a path or a transition when modeling indoor space. However, it is understood that there is no way to describe such directions of a path (or a transition) in the suggested data model. In the suggested data model, all transitions are bi-directional. Therefore, we need some modifications to the suggested model to resolve this problem.
WMTS 1.0 Change Request - Conform to OGC 08-131r3 ModSpec	1	11-155	Paul Daisey	2011-10-19
1. Inconsistent specification of operations, parameters, and conformance clauses for KVP/GET, KVP/POST, XML/POST, SOAP/POST and RESTful bindings. 2. Various errata. 2. Abstract Test Suite (ATS) too general to support development of unambiguous Executable Test Suite (ETS)
Incorrect reference in ows19115subset.xsd	1	11-156	David Valentine	2011-10-19
http://schemas.opengis.net/ows/1.1.0/ows19115subset.xsd Error Failed to load the schema [http://www.w3.org/2001/xml.xsd], included from schema [http://schemas.opengis.net/ows/1.1.0/ows19115subset.xsd] Failed to read the file at [http://www.w3.org/2001/xml.xsd] Failed to load the url [http://www.w3.org/2001/xml.xsd] The underlying connection was closed: The connection was closed unexpectedly.
Default value for the count parameter is not clear.	1	11-153	Panagiotis (Peter) A. Vretanos	2011-10-19
There is a disagreement concerning the default value of the count parameter between Table 5 and clause 7.6.3.5. Table 5 says the default value is 1. Clause 7.6.3.5 says there is no default value.
Adopt documented best practices for CRS definitions (URN CRS per 07-092r3) in WMS 1.3	1	11-142	Luis Bermudez	2011-10-19
Different OGC specifications for WMS, WFS, WCS, CAT, GML, OWS_Common, and different versions of those specifications require different forms of CRS specification. It is a significant hindrance to interoperability long recognized in the OGC community to have to use different CRS specifications for different OGC Specifications.
Consistent handling of operators in Filter capabilities document	1	11-141	Panagiotis (Peter) A. Vretanos	2011-10-19
Within a Filter capabilities document support for the logical operators is accomplished by including the empty element fes:LogicalOperators. This however is different from the other operators which are explicitly listed.
Allow use of http URIs to identify CRS	1	11-152	Simon Cox	2011-10-19
The WFS 2.0 spec requires that coordinate reference systems referred to in WFS interactions be identified by OGC URNs. Current OGC policy is to _allow_ URNs, but to _recommend_ http URIs (URLs).
DropStoredQuery KVP Encoding	1	11-140	Debbie Wilson	2011-10-13
DropStoredQuery KVP Encoding described in Table 23 defines the KVP encoding for DescribeStoredQueries not DropStoredQuery
Symbolizer for styling of nested child objects	1	11-148	Jeroen Dries	2011-10-13
omplex data models like AIXM 5 have feature types that are a composition of nested objects. The current SE 1.1 only allows limited styling of these child objects, such as using the same style for all objects. This change request defines a new type of symbolizer that makes this possible.
Add service id field to service identification section.	1	11-117	Panagiotis (Peter) A. Vretanos	2011-09-15
The only way catalogues have to distinguish one OGC service instance from another is by using the service's URL (e.g its base URL or GetCapabilities URL) which is not a reliable method. So, there needs to be some other, more robust, way for a catalogue to distinguish one OGC from another when it harvests them.
LOD0 footprints for all CityGML classes	2	11-102	Linda van den Brink	2011-09-15
The guidelines (or rules) for extending CityGML should be described more fully and clearly so that a working extension of CityGML (i.e. working in CityGML software) can be created by relying on these rules and/or guidelines.
Clarify returnFeatureType semantics for the GetFeatureId stored procedure	1	11-100	Panagiotis (Peter) A. Vretanos	2011-09-15
The current semantics of the returnFeatureType parameter used in describing stored queries do not work for the mandatory GetFeatureById stored query because this stored query can returns a feature of any type.
LOD0 footprints for all CityGML classes	1	11-102	Linda van den Brink	2011-09-15
The guidelines (or rules) for extending CityGML should be described more fully and clearly so that a working extension of CityGML (i.e. working in CityGML software) can be created by relying on these rules and/or guidelines.
Conformance test A.2.17 is not clear with regard to local resolve.	1	11-098	Panagiotis (Peter) A. Vretanos	2011-09-15
According to clause 7.6.4.1, all WFS implementations must support local resolve. However, conformance test A.2.17 seems to imply the opposite ... that local resolve is not mandatory for all conformance classes.
Add land cover information	1	11-103	Linda van den Brink	2011-09-15
Enriching LandUse class with land cover information would improve the semantics for this class significantly. This would also be in line with harmonization with Inspire themes (CR10-062).
Clearer guidelines for extending CityGML	1	11-101	Linda van den Brink	2011-09-15
The guidelines (or rules) for extending CityGML should be described more fully and clearly so that a working extension of CityGML (i.e. working in CityGML software) can be created by relying on these rules and/or guidelines.
Consider revising clause 7.6.4.1 to not make "local resolve" mandatory for all confromance classes.	1	11-099	Panagiotis (Peter) A. Vretanos	2011-09-15
Clause 7.6.4.1. says that all implementation of WFS must support "local resolve". However, this seems rather advanced functionality for the "Simple WFS" and perhaps the "Basic WFS" conformance classes.
The description of the abstract test suite is not clear in some cases.	1	11-128	Panagiotis (Peter) A. Vretanos	2011-09-15
Having a look at Annex A.1.2 of the WFS 2.0 specification (Basic WFS), I still wonder if "Verify the following list of conformance tests: [...] ,A.2.11.2, [...], A.2.20.1, A.2.20.2, [...]" really implies that the respective functionality must be available (even if not announced by the server). A.2.11.2: Version navigation A.A.2.20.1, A.2.20.2: Response paging IMHO, this would imply that every Basic WFS has to implement "Response" as well as "Feature versions" conformance classes!? Or can an implementation still be Basic WFS compliant even if it does not offer Version navigation/response paging (and sets the respective conformance classes in the capabilities to FALSE)?
Additional class for constructions other than buildings	1	11-104	Linda van den Brink	2011-09-15
CityGML currently lacks (a) class(es) for constructions that are human-built objects, but that are not ‘buildings’ in the normal meaning: e.g. they have no roof, doors, windows etc, may not be able to be closed off, etc. The INPIRE Building domain model also has a class OtherConstruction. Harmonization with Inspire constitutes a second reason for change.
Local resolve should not be required for the Simple WFS conformance class.	1	11-130	Panagiotis (Peter) A. Vretanos	2011-09-15
equiring local resolve to be supported for the SimpleWFS conformance class seems to set the implementation bar rather high.
Fix the use of the NAMESPACE parameter in the examples and clarify its use	1	11-127	Panagiotis (Peter) A. Vretanos	2011-09-15
A number of KVP examples in the WFS specificaton use qualified names without binding the prefix used to a namespace.
WFS Abstract test suite seems to imply that a	1	11-129	Panagiotis (Peter) A. Vretanos	2011-09-15
In the list of tests for Simple Conformance Classes it says 'A.2.17'Which would seem to imply A.2.17.1, A.2.17.2, A.2.17.3.1, A.2.17.3.2, A.2.17.3.3. Seems reasonable to require A.2.17.1 - basically reporting 'none'. But everything else seems like a really high bar to reach a simple, let alone a basic, wfs conformance class.
GmlBase/Dictionary in 3.2.1 need to import DepreciatedTypes	1	11-132	David Valentine	2011-09-15
Does not validate because StringOrRefType, indirectEntry, and metaDataProperty are in depecriatedTypes. Discovered using Liquid XML (MS Xml)
Temporal Constraints for State and Transition UML class in the data model	1	11-118	JaeJun Yoo	2011-09-15
When modeling indoor spaces for some indoor services such as indoor-navigation, we need to consider some temporal constraints when can affect the indoor space model. However, in my understanding, the currently suggest data model cannot support such temporal constraints. For an example and more detailed comments, please refer the uploaded file at supporting document field below.
Composite Rule with support for 'Else If' and nested objects	1	11-131	Jeroen Dries	2011-09-15
1. Complex data models like AIXM 5 have feature types that are a composition of nested objects. The current SE 1.1 only allows limited styling of these child objects, such as using the same style for all objects. 2. Another CR defines a CompositeChildSymbolizer to apply a symbolizer to child objects, this is not always sufficient because there are examples where we need to apply rules to nested objects to select the right symbolizer. 3. Currently the concept of 'else if' as defined by many programming languages is not supported by SE. This makes rules hard to write and inefficient, as every rule also needs a condition that is the inverse of the conditions of the other rules to achieve the same effect.
ATC 11 assertion is invalid if LatLonBox bounds cross anti-meridian	1	11-081	Jason Mathews	2011-07-25
ATC 11: LatLonBox states following constraints: * kml:north > kml:south * kml:east > kml:west However, the kml:east > kml:west constraint doesn't hold if GroundOverlay LatLonBox bounds cross anti-meridian (i.e., west >= 0 && east < 0) in which case this rule needs clarification. For example, let west = [Korea] +125 lon, east = [California,US] -115 lon east > west constraint valid only if bounds don't cross anti-merdian (i.e., west < 0 \|\| east >= 0) ATC 11 assertion is invalid if bounds GroundOverlay LatLonBox bounds cross anti-meridian as in above example. There is a related bug in Google Earth: http://code.google.com/p/earth-issues/issues/detail?id=1145
Describe the use of RSS auto discovery for advertising which OGC services are available at a site.	1	11-079	Panagiotis (Peter) A. Vretanos	2011-07-25
RSS auto discovery is a well established protocol on the web that allows, for example, browsers to find RSS feeds at a site. This capability would be leveraged to make OGC services discoverable in the same way aiding other services like catalogues. Presumable a catalogue could use the RSS auto discovery protocol to find all the services available at a site and harvest them ... without having to have a priori knowledge of the URL for each capabilities document.
Inconsistent default value for startIndex parameter	1	11-082	Panagiotis (Peter) A. Vretanos	2011-07-25
The default value for the startIndex parameter is not consistent within the body of the specification. In some places it is zero, in other places it is 1.
Definition of NativeType does not seem to be correct	1	11-084	Panagiotis (Peter) A. Vretanos	2011-07-25
Both the text of the specification and the schema, wfs.xsd, do not seem to correctly define the Native element. The current definition does not allow content within the native element which is a problem.
Declaration of element is incorrect.	1	11-078	Panagiotis (Peter) A. Vretanos	2011-07-25
The declaration of the Native element appears to be incorrect in both the document and the online schema repository.
Incorrect element referenced in clause 7.6.2.6	1	11-083	Panagiotis (Peter) A. Vretanos	2011-07-25
Clause 7,6.2.6 incorrectly reference the element ows:ExceptionText as containing the locator attribute when in fact it is the ows:Exception element upon which the locator attribute is defined.
Symbolizer and Rule for styling of nested child objects	1	11-076	Jeroen Dries	2011-07-25
Complex data models like AIXM 5 have feature types that are a composition of nested objects. The current SE 1.1 only allows limited styling of these child objects, such as using the same style for all objects. This change request defines a new type of rule and symbolizer that makes this possible.
fig 18 colours for inter-space connections	1	11-067	Luc Van Linden	2011-07-25
colours used seems not consistent, but seem to suggest some commonality, representing the same space-space inter-space connection
Typos and other minor clarifications	1	11-077	Panagiotis (Peter) A. Vretanos	2011-07-25
On page 61, Example C.4 about schema-element() It reads: "In this case, the WFS shall consider the property streetName of all subtypes of Address, ie. USAdress, EUAddress, AUAdress". I suggest adding "and Address itself" (6.3.3.1.5 makes it clear) There are also a couple of typos in the example in C.2.
Attribute and element with same name cause JAXB compilation error	1	11-069	Patrick Goalwin	2011-07-25
An error was encountered when attempting to compile GML 3.2.1 using JAXB. The specific locations are: gml\3.2.1\geometryPrimitives.xsd"(648,13): gml\3.2.1\geometryPrimitives.xsd"(680,16):
Change title of AnyInteracts temporal operator to TIntersects	1	11-068	Debbie Wilson	2011-07-25
The title name of the AnyInteracts temporal operator is not immediately intuitive to users. By changing the title to TIntersects reflects terminology used in use cases and scenarios. For example: “...and the scheduled reservation activity time interval intersects with the subscription time interval.”
page 24 line 9 "be" between "can" and "used" is missing	1	11-075	Luc Van Linden	2011-07-25
page 24 line 9 "be" between "can" and "used" needs to be added
elaborate on \	1	11-066	Luc Van Linden	2011-07-25
\"now contains this information\". It seems to me that this information is not contained by the dual graph itself, but represented by the dual graph. This means that \"this information\" (the single step in the middle of the floor) can be derived/interpreted explicitly from the combination of the dual graph and the topographic space. In other words, the dual graph contains the information on what cell(s) is(are) connected to others and it is only when the Inter-space connections are taken into account that \"this information\" can be derived.
A REST binding for WFS 2.0	1	11-080	Panagiotis (Peter) A. Vretanos	2011-07-15
The WFS specification already defines an OGC XML-POST binding, an OGC KVP-GET binding and a SOAP binding. The other popular service binding, which the WFS does not currently support, is REST. This change proposal attempts to address this omission.
CITE test doesn't comply with section 14.3.3 of the spec	1	11-047	Hoang Dam	2011-05-12
Implement section 14.3.3 of the spec results in failing the CITE. Here is the assertion... \"A KVP parameter value that denotes a bounding box shall conform to the general syntax specified in subclause 10.2.3. If no CRS reference is provided, a service-defined default value must be assumed.\" However, section 14.3.3 of the spec gives an impression that EPSG:4326 (WGS84) must be used for BBOX 2-D coordinate system. Follows are the excerpt of section 14.3.3 \"14.3.3 Bounding box The bounding box parameter, BBOX, is included in this specification for convenience as a shorthand representation of the very common a bounding box filter which would be expressed in much longer form using XML and the filter encoding described in[3]. A BBOX applies to all feature types listed in the request. The KVP encoding for a bounding box is defined in subclause 10.2.3 of normative reference [15]. The general form of the parameter is: BBOX=lcc1,lcc2,...,lccN,ucc1,ucc2,...uccN[,crsuri] where lcc means Lower Corner Coordinate, ucc means Upper Corner Coordinate and crsuri means the URI reference to allows N coordinates optional crsuri. If coordinates shall be described in [15].\" the coordinate system being used. This encoding for each corner listed in the order of the the crsuri is not specified then the 2-D specified using decimal degrees and WGS84 as
Required support for TINs (for interchange or interface)	1	11-046	Emmanuel Devys	2011-05-12
- TINs are not included in present version of the specification and corresponding schema GML Coverage AS 1.0 (and WCS 2.0). It is reminded that 09-146r1 mentions in its chapter 3 – Normative References the conformance classes for both TIN coverage interface and interchange. - TINs are used in ESM Abstract model, based on Topic 6 or ISO 19123 (Coverage) Grid, TIN and point coverages. - DGIWG works intend to use GML Coverage Application Schema for the ESM Application schema for the 2 following key reasons: - the GML Coverage Application Schema appears to be the only standardized Application Schema for Coverages (interchange or data access) - it is foreseen that this will favour the use of WCS2.0 service to ESM data (or make their access available).
Improve control over BalloonStyle layout	1	11-042	Clemens Portele	2011-05-12
If one wishes to use JavaScript scripts in a KML Balloon it is currently required to provide the complete HTML document. This is usually undesirable, so it would be useful, if KML would support child elements to a BalloonStyle? to specify, for example, styles and scripts.
Allow default value for a complex data input type	1	11-041	Aleksei Valikov	2011-05-12
WPS 1.0.0 allows specifying default value for a literal input type. At the same time, there is no such option for complex data input type. It is impossible to "default" complex inputs. This feature is very useful in many scenarios. For instance, some "reasonable default value" is known for the input (ex. "most used value" or "recent value" or "user settings" may be used as default value). This may improve usability of WPS process on the clint site (end-user interaction).
The numberReturned parameter should be able to have the value	1	11-040	Panagiotis (Peter) A. Vretanos	2011-04-22
From the SAA pilot: numberMatched can be 'unknown', so in case if the actual number of matched features is smaller than the 'count' parameter, or the count parameter is not set, what should the value of 'numberReturned' be? Shouldn't it be possible to set this attribute to 'unknown'?
Correction of XML Schema GetCapabilitiesResponse.xsd	1	11-037	Herve Caumont	2011-04-22
Considering both « OGC 07-057r7 » and « wmtsGetCapabilities_response.xsd » we have discrepancies in the types (integer/positiveInteger) for the following elements of TileMatrixLimits : - MinTileRow - MaxTileRow - MinTileCol - MaxTileCol
Harmonization with SQL/MM	1	11-026	John Herring	2011-03-01
Harmonization with SQL/MM, which has changed significantly since the original harmonization with version 1.1 Simple Features
Service metadata WMS 1.3.0 and ISO 19119 differs: alignment is needed in future versions of OWS common 2.0 with (newest version of) ISO 19115	1	11-028	Marcel Reuvers	2011-03-01
Differences between service metadata of: • • • ISO 19119 and ISO 19128 of ISO/TC 211 WMS 1.3.0 and ISO 19119 of OGC and ISO/TC 211 ISO/CD 19115 - ISO 19119 and OWS common of OGC and ISO/TC 211 The service metadata will become part of the newest version of ISO 19115. In the current version of ISO/CD 19115 section 6.6.13 the service metadata of ISO 19119 is included. The differences between these standards makes implementation 1 of 4 difficult and confuses implementers. In the Inspire view service Technical Guidance (version 2.20) these differences have become visible in the extended capabilities. The extended capabilities are extra elements needed to make WMS 1.3.0 in alignment with ISO 19119 and ISO 19115.
Alignment multilingualism Inspire view service with OGC and ISO/TC 211 standards (at least OWS Common 2.0) (All INSPIRE network services are subject to languages support not only view)	1	11-027	Marcel Reuvers	2011-03-01
Inspire requirements for language can’t be fulfilled with OWS common 2.0
Cartogram Symbolizer	1	11-024	Emanuel Rita	2011-03-01
The actual SE language does not allow the creation of cartogram maps. This extension introduces a new element that will to deform polygon features of a given layer creating this way cartogram maps.
Add date type to list of SimpleField types	1	11-002	Jason Mathews	2011-03-01
Date values in ExtendedData/Schema/SimpleFields should be added with an explicit \"date\" type as opposed to using the string type.
decimal fraction separator specification	1	11-003	JW Lokin	2011-03-01
Ongoing complaints about problems in locales where the decimal fraction separator is a comma, which interferes with the separator specified for .
Add resolution parameters to GetFeatureRequest to support visualization clients	1	11-004	Panagiotis (Peter) A. Vretanos	2011-03-01
Visuallization clients are having a very hard time interacting with WFS's because of the volume of data that can be generated when you are zoomed out too far. Also, geometries may be simplified to remove detail as you zoom out further reducing the size of the output generated. This is a problem even if the WFS output stream is compressed ... which it should always be.
Symbology Encoding Improvements	1	11-023	Chris Holmes	2011-03-01
We've made lots of extensions to SLD in order to achieve high quality rendering. If SLD seeks to be comprehensive enough to be able to render a high quality base map then these changes are essential, imho. If SLD is just about overlaying stuff roughly on top of other base maps then these aren't essential, but would be nice improvements for people.
KML - Extended metadata needed for KML ExtendedData Schema elements	1	11-001	Jason Mathews	2011-01-18
ExtendedData needs standard convention to define metadata such as units of measure (UOM). Without such definition there is no common way to define such metadata.
Axis order of input services to WPS	1	10-197	Raj Singh	2010-11-30
Is there anything we should/could look at adding to WPS to check/correct axis order of input services before trying to execute a process?
KML - Inconsistent use of Snippet vs snippet in KML documents	1	10-193	Jason Mathews	2010-11-30
There is inconsistent use of Snippet vs snippet in spec and Best practice document (OGC 07-113r1).
Extend basic package to describe actual OGC artifacts.	1	10-187	Panagiotis (Peter) Vretanos	2010-11-30
The basic package currently describe a very small subset of OGC artifacts and is missing what I believe most people would consider basic object types. For example there are no object type identifiers to distinguish between a wms layer and a wfs featute type. This makes the csw fairly useless without additional extension packages. I believe that an ogc catalogue should be able to harvest ogc artifacts right out of the box without additional packages.
WPS Add a new input Type StructuredData and a new output type StructuredOutput in the wps DescribeProcess Schema	1	10-186	Alain Kabamba	2010-11-30
In order to improve interoperability and also to facilitate automatic GUI generation by WPS clients , we recommend to introduce the notion of structured type in the list of WPS input and output of the WPS (Structured types will be more precisely specified then the ComplexData type).
Conversion Functions	1	10-199	Andreas Matheus	2010-11-30
It is not mandatory for the conformance class I (BASIC) that the following functions are included: urn:ogc:def:function:geoxacml:1.0:convert-to-metre urn:ogc:def:function:geoxacml:1.0:convert-to-square-metre
Clarify the semantics for testing NULL geometries	1	10-203	Panagiotis (Peter) A. Vretanos	2010-11-30
There should be a clear statement in the specification concerning how NULL geometries should be handled. Since the convention seems to be that a NULL geometry is disjoint from other geometries, the FES should declare that. A tatement like "If a spatial operator in a filter expression is testing a pair of geometries and one is null, the results should be FALSE (i.e. the two geometries are disjoint)."
Clarify the semantics for testing NULL geometries	1	10-202	Panagiotis (Peter) A. Vretanos	2010-11-30
The FES 1.1 specification is not clear about how NULL geometries should be treated by spatial operators and this needs to be clarified.
Add the attribute maxoccurs="unbounded" for the se:Graphic reference in GraphicStroke and PointSymbolizerType	1	10-201	Steve Hruda	2010-11-30
The attribute maxOccurs with the value unbounded must be added in the se:Graphic reference in GraphicStroke and PointSymbolizerType. (See page 28 Symboogy Encoding Implementation Specification 05-077r4)
Typo in specfication and schema ogc4sos.xsd	1	10-200	Eric Boisvert	2010-11-30
Sos4ogc.xsd (http://schemas.opengis.net/sos/1.0.0/ogc4sos.xsd) which provides the filter validation has a misspelled "TM_Overalps" (should be TM_Overlaps). This prevents validating queries from the published schemas (unless the misspelled element is used). This typo is also present in the 06-009r6 document A.13, page 66
Add extension point to UserStyle element	1	10-181	Tobias Moberg	2010-09-21
Extend the schema definition of the UserStyle element to include an abstract element called _ExtendedUserStyle. Include an example of how to use this element together with the XML Schema 'substitutionGroup' functionality in section 11.4 of the specification.
CSW-ebRIM Add a new GetRepositoryItems and GetRepositoryItemById operation to the CSW-ebRIM service	1	10-175	Frederic Houbie	2010-09-08
CSW-ebRIM Add a new GetRepositoryItems and GetRepositoryItemById operation to the CSW-ebRIM service
Clarify KVP BBOX parameter interpretation	1	10-174	Andreas Schmitz	2010-09-08

Define a "where" slot.	1	10-162	Panagiotis (Peter) A. Vretanos	2010-08-05
At the moment there is no standard target for spatial predicates (similar to georss:where for ATOM) and there is no way for a CSW-ebRIM client to get a list of available slots/slotTypes making it very difficult to formulate spatial predicates with operators other than BBOX.
Missing ebXML Slot Types Definition	1	10-154	Lorenzo Bigagli	2010-08-02
According to 06-131r6_EO_Products_Extension_Package_for_ebRIM_(v0.2.5), slot types range definitions are missing from CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW [OGC 07-110r4]. They should be defined in order to map EP concepts to the ebRIM structure, i.e. to define the range of slot types used in the EP
Redefinition of GetCapabilities response document element	1	10-153	Lorenzo Bigagli	2010-08-02
Allow for a mechanism of selecting between the baseline and the ebRIM AP response type. Overloading the mandatory "service" parameter is assumed in the EO EP, as follows (the following paragraph should be added to §8.2 of 07-110r4). The value of the mandatory "service" parameter may be 'CSW' or 'CSW-ebRIM'. In the former case, the server should respond as defined in the baseline CSW specification. In the latter case, the server should respond as defined in the following section.
Simplify WPS for Synchronous KVP	1	10-152	Peter Schut	2010-08-02
Provide a simple version of WPS to meet the needs of the mass market.
Add hatching to se:Fill	1	10-145	Reinhard Erstling	2010-06-25
Cross hatching is a method of area filling which is used so often and has so simple parameters that it should be established as another Fill variety.
Add a way to select se:ExternalGraphics using data content	1	10-146	Reinhard Erstling	2010-06-25
Use cases require different ExternalGraphics to be placed in points, where the selection of the particular Graphic is controlled by data content.
Use XML encoding of GetMap from next WMS version	1	10-144	Reinhard Erstling	2010-06-25
The next version of the WMS specification (version 2.0) will contain XML formats of its operations. There is no longer a need for the SLD Profile of WMS to define its own XML encoding of GetMap.
Reformulate specification on scale selection in Rules	1	10-143	Reinhard Erstling	2010-06-25
The specification regarding scale selection in Rules is lengthy and hard to understand. Moreover, part of the text is at least misleading. A certain amount of rewording is also necessary because the next verion of WMS will introduce a PIXELSIZE parameter.
Misspelled attribute	1	10-141	Reinhard Erstling	2010-06-25
The attribute named 'threshholdsBelongTo' belonging to the definition of the element Categorize should correctly spell 'thresholdBelongsTo'. The same applies for its type 'ThreshholdBelongsToType'.
Treatment of properties with a cardinality greater than 1	1	10-142	Reinhard Erstling	2010-06-25
The SLD/SE spec does not give any information on how to deal with properties which carry a cardinality greater than 1. We should think about this, because (a) properties with cardinality > 1 are quite common in data models and (b) FE and WFS 2.0 will address this problem explicitly (at least in some contexts).
Rapport in repeated linear patterns generated by se:Stroke	1	10-139	Reinhard Erstling	2010-06-23
There is no way to request rapport in a full cycle of a Stroke pattern at the end point of a geometry. If the specification is taken literally, rapport calculation is not even permitted on an implementation specific basis.
GML 3.2.1 change request - Add ReferenceableGridByTransformation	1	10-138	Arliss Whiteside, Max Martinez	2010-06-23
Abstract Specification Topic 6 (ISO 19123) specifies CV_ReferenceableGrid, but this class was not previously encoded in GML. GML Change Request 07-112r3 adds an abstract implementation of CV_ReferenceableGrid, plus two concrete subtypes that are designed for irregularly spaced grid points. However, another implementation of CV_ReferenceableGrid is required and will be very frequently used. That implementation uses a CC_Transformation or CC_ConcatenatedOperation (instead of grid points) to specify the relationship between grid coverage positions and positions in another CRS, as suggested in Clause 8.10.1.1 of Topic 6. Although that Transformation could use grid points, it will usually be an analytical Transformation using sensor models such as defined in ISO 19130. Analytical Transformations are normally used for these sensor models, to reduce the required data volume and to simplify least-squares adjustment.
Define a cross-service implementation of the subscribe/notify paradigm	1	10-133	Alexandre Robin	2010-06-22
Many OGC service specifications define their own way of handling subscriptions and notifications as well as asynchronous mechanisms. There needs to be a standard OGC approach to solve this need in a common manner in all service standards.
Repository Item validation	1	10-120	Leif Stainsby	2010-05-20
Add mechanism to improve integrity of registry content. Current specification does not address this capability. This issue was raised in the Registry SWG charter (OGC 07-119r1) that identified several critical deficiencies in the current CSW-RIM 1.0.1 specification.
Revise definition of VersionInfo/@versionName property	1	10-119	Leif Stainsby	2010-05-20
The CSW-ebRIM 1.0.1 spec does not address support for versioning of RegistryObjects. There is an ebRIM property, VersionInfo/@versionName, which is intended to track version numbering in a "versioning" registry. Clause 15.2.1 "General behaviour" (for Transactions) states that: "This profile does not specify any form of versioning. The value of the versionName attribute of the rim:VersionInfo element shall be an empty string for all unversioned registry objects." This renders a potentially useful property useless. The intent of this CR is to redefine this property in order to facilitate the development of additional registry capabilities based on change detection. For example, in HTTP, the Entity Tag (E-Tag) header used in conjunction with the If-None-Match request header can enable a registry service to optimize responses (i.e. avoid resending content that has NOT changed) in a standardized manner.
Define Extensible Life-Cycle model	1	10-121	Leif Stainsby	2010-05-20
Life-cycle management is lacking in current CSW-ebRIM specification. Life-cycle management capability is key enabler for registry applications, especially those requiring workflow processing. Addition of an extensible Life-Cycle model would allow better support for registry applications requiring workflow.
Define Life-cycle Update transaction method	1	10-122	Leif Stainsby	2010-05-20
Absence of the means to modify a RegistryObject's life-cycle status has been identified as a deficiency in the CSW-ebRIM specification. Changing the status of an object (in a controlled manner) allows it to participate in an application defined life-cycle. Life-cycle management is a key feature in workflow scenarios. Support for workflow processing requires this capability to be standardized.
Define a Registry Extension Package model	1	10-118	Leif Stainsby	2010-05-20
An Extension Package is a concept introduced during the writing of the CSW-ebRIM specification. While the Basic Package (OGC 07-144) offers a limited example, there exists no official definition for: a) how to define an Extension Package b) what elements should be present in an Extension Package (mandatory or otherwise) c) how a registry must handle an Extension Package once it is loaded into the registry. If there are constraints in an Ext. Pkg. how are they manifested, when are they enforced. Consider special cases such as: * an Access Control policy extension gets loaded in an Ext. Pkg. * new Life-cycle models are loaded. However, several communities have already defined Extension Packages (i.e. HMA-T, CIM, CRS etc.). Experience shows that these packages, while useful to their communities, have differences in implementation and in some cases lack components that would improve their overall utility.
Align with Catalogue/CSW 3.0	1	10-123	Leif Stainsby	2010-05-20
CSW-ebRIM AP 1.0.1 is based, in large part, on the Catalogue/CSW specification. As the Catalogue/CSW spec is now being updated, it is an excellent time to revise the CSW-ebRIM spec in concert with it.
LockFeature description does not correlate with schema fragments.	1	10-113	Panagiotis (Peter) A. Vretanos	2010-05-20
In section 11.2.1, the XML Schema fragment for defining the LockFeature request includes the attribute definition: Two paragraphs below that, the text states: \"This specification does not constrain how long a lock should be held if the expiry attribute is not specified.\" 1 of 2 What does the default value of the expiry attribute do, then, if not \"constrain how long a lock should be held if the expiry attribute is not specified\"? Furthermore, in the examples in section 11.5, the sample responses are shown to have a root element name of \"WFS_LockFeatureResponse\"; in reality, at least talking to a GeoServer (which I understand is the reference implementation of this spec), the name is actually \"wfs:LockFeatureResponse\".
Refine Granularity of Timestamps	1	10-112	Thomas Lane	2010-05-20
The work I am doing with KML would benefit from the ability to timestamp content in increments of less than a second, since the information I wish to represent on the model changes more than once per second. Since I would benefit greatly from this change, other people and groups probably would, too. There are numerous potential uses of KML content that would be inconvenienced by the inability to differentiate events that occurred during the same second, but not at the same time.
Version number in Normative References to OGC documents	1	10-114	Steven Keens	2010-05-20
The new policy regarding versioning of OGC standard is not clear on how to deal with version number in references to other OGC documents. For example, should a normative reference include the bug version number or just the major and minor version numbers? What version level should be added to the abbreviated references? Normative reference example: OGC 07-036, Geography Markup Language (GML) Encoding Standard, version 3.2.1 or OGC 07-036, Geography Markup Language (GML) Encoding Standard, version 3.2 Abbreviated reference example OGC-GML 3.2.1 or OGC-GML 3.2
Make clear the distinction between a Process Description, a WPS Application Profile, a profile of the WPS Specification	1	10-115	Edward Nash	2010-05-20
Currently the distinction between a WPS Process Description, a WPS Application Profile and a profile of the WPS spec. is not made sufficiently clear: section 6.4 "WPS Profiles" starts by talking about "standardized profiles" and then moves into "Application Profiles".
Define a packaging format for CSW-ebRIM Extension Packages	1	10-117	Leif Stainsby	2010-05-20
The CSW-ebRIM 1.0.1 specification includes an Extension Package (the Basic Package) and partially describes what they contain, but, stops short of defining a transport format for them. Having a transport format, one which could be used for ingest (via Harvest for example), export and archival purposes would be extremely useful and facilitate the adoption of the Extension Package concept as well as the creation of new domain specific packages.
Add support for multiple file input such as shp files	1	10-116	Bastian Schäffer	2010-05-20
WPS spec is lacking support for associating multiple files to one input such as shp files
Catalogue (CSW) 2.0.2 CR: introducing a new attribute to enrich the semantics of numberOfRecordsMatched	1	10-110	Yuqi Bai	2010-05-19
When implementing OGC CAT 2.0.2 on top of massive metadata sets, it may not be practical or even feasible to know the total number of matched records, due to the long time of processing or other possible reasons. Therefore, by introducing a new dedicated attribute in the response, whether "numberOfRecordsMatched" standards for the total number of matched records, or at least having that number of matched records could be differentiated, and the clients may act accordingly and elegantly.
Semantics of requirements class extension	1	10-066	Lorenzo Bigagli	2010-05-19
The current conceptual framework cannot capture restrictive requirements, that are very common, e.g. in Application Schemas (see OWS Commons, §11.6.6), Profiles, etc. The intended rationale to prevent limitations to possible future standard extensions results in inconsistency, with the current wording of Req 25.
Make get Domain more general	1	10-109	Panagiotis (Peter) A. Vretanos	2010-05-17
The current get domain operation is not flexible enough to support the create of robust CSW clients. For example, Table 64 is missing a lot of request parameters for which a client might want to know the run-time domain.
KML Change Request: Correct latitude & longitude bounds & defaults	1	10-108	Tyler Erickson	2010-05-16
Some of the coordinate bounds and defaults in the KML specification document are illogical. For example, the specification defines longitude between -90 and +90 (rather than -180 and +180. Also, some of the coordinate bounds described in the main document do not match the KML Schemas listed in Annex A.
KVP parameter ordering and unrecognized KVP parameters	1	10-107r1	Keith Pomakis	2010-05-16
In the course of helping define the WMTS specification, I discovered something surprising about the OWS Common specification (all versions). Nowhere does it mention that unknown/unrecognized parameters in KVP requests must be ignored. This has been standard practice in all OGC Web Service implementation specifications, and is a very important trait for all OGC Web Services to have because it allows for the non-intrusive use of vendor-specific and/or experimental parameters. Furthermore, it makes no mention that KVP parameters must be accepted in any order. This, too, has been standard practice in all OGC Web Service implementation specifications, and is typical CGI behaviour. Are these dictates intentionally absent from the OWS Common specification, or is their absence an oversight?
BNF for WKT syntax does not specify whitespace between coordinates	1	10-106	Kevin Martin	2010-05-16
The BNF in 7.2 does not account for the white space required to delimit the coordinates for productions like . Thus the text 'POINT(12)' is valid WKT for a 2-d point, and 'POINT(123)' is also valid but cannot be parsed unambiguously. On the other hand, 'POINT(1 2)' which appears to be the intended valid syntax is disallowed by the BNF.
Create new feature type capability for WFS	1	10-105	Panagiotis (Peter) Vretanos	2010-05-16
Dynamic situations, such as disaster relief, require the ability to create new feature types on-the-fly to reflect the situation on the ground. Also, collaborative data entry (e.g. crowd-sourcing) require this capability because it is difficult to a priori anticipate all the feature types that may be required.
Inaccurate wording in specification	1	10-068	Raj Singh	2010-05-15
Editorial Changes: page 143: In Table 65, the Keyword typeNames -- should it be typeName? page 151: 1 of 2 should this paragraph: The ElementName and ElementSetName parameters are mutually exclusive. Either an ElementSetName parameter OR one or more ElementSetName parameters shall be specified in a query. actually be: The ElementName and ElementSetName parameters are mutually exclusive. Either an ElementName parameter OR one or more ElementSetName parameters shall be specified in a query. (changed 2nd occurence of ElementSetName to ElementName) http://schemas.opengis.net/csw/2.0.2/examples/Clause_10.6.6_Example.xml -- and others there -- have a relative schema location. I think it should be fixed to http://schemas.opengis.net for greater clarity. (This might have been fixed recently?)
Table Joining Service RFC Responses	1	10-089	Peter Schut (editor)	2010-04-23
Responses received from the March 2010 TJS RFC
SWE Common Data Model 2.0 RFC Comments	1	10-077	Alexandre Robin	2010-04-16

WCS 2.0 RFC responses	1	10-076	Peter Baumann	2010-04-15

OWS-7 AIXM 5.1 Metadata CR	1	10-072	David Burggraf	2010-03-23

Management of a modularised specification and Application Domain Extensions	1	10-063	Carsten Roensdorf	2010-03-10
A mechanism needs to be found that guides and controls the development of the existing and additional thematic structuring of the CityGML standards. Previous discussion suggested the creation of specifying different CityGML modules in separate documents, though this was deferred to after version 1.0.
Harmonisation with Inspire Themes	1	10-062	Carsten Roensdorf	2010-03-10
There is an overlap between some themes in CityGML and the data themes identified by Inspire annexes, such as transportation networks, land use, terrain models or buildings. The differences to existing Inspire data specifications should be analysed. Proposals for harmonisations or practical reasons against harmonisations need to be documented and fed into the revision process.
Thematic module for walls in cities	1	10-053	Claus Nagel	2010-02-26
The semantic data model of CityGML 1.0 lacks a model for the representation of walls in cities. However, walls are essential features of cities and it should be possible to adequately represent them in virtual 3D city and landscape models. "City wall" should be broadly defined to not only comprise ancient fortifications, but also smaller walls such as garden walls or fences. As for CityGML 1.0, the only possibility to model and exchange walls in cities is to use a GenericCityObject as proxy or to define a corresponding ADE. Both approaches face disadvantages.
Compression archive format	1	10-052	Claus Nagel	2010-02-26
As with any plain-text XML encoding of any content, CityGML instance documents quickly grow in file size . This makes CityGML files slow to transfer over the Internet and the storage of CityGML documents costly. Since XML generally compresses well, file compression can be used to considerably reduce file size and speed up file distribution. Well-known file compression methods such as GZIP are available for this purpose. Furthermore, the OGC has proposed a binary XML encoding format (Binary Extensible Markup Language (BXML) Encoding Specification, OGC Best Practices Doc. No. 03-002r9) which not only addresses space reduction but also scanning-costs as well as costs for the conversion of text-encoded numerical coordinate and observation values.
Thematic module for bridges	1	10-051	Claus Nagel	2010-02-26
The semantic model of CityGML 1.0 covers many urban and regional features relevant to 3D city and landscape models. However, it lacks a data model for bridges. The only possibility to model and exchange bridges in CityGML 1.0 is to use a GenericCityObject as proxy. Alternatively, a corresponding ADE could be defined. Both approaches face disadvantages. First, GenericCityObjects are simple in structure and are hence not suitable to replace a semantically rich model for bridges. Second, bridges are not specific to just a single application domain. Several ADEs could emerge proposing different semantic models. What is required is a common and standardized thematic module on bridges in CityGML.
Enhancement of generic attributes	1	10-054	Claus Nagel	2010-02-26
Generic attributes allow for augmenting exisiting CityGML features by application-specific extra attributes in a simple and straightforward way, without the need for explicitly defining an ADE (which are not necessarily supported by CityGML-enabled software). In CityGML 1.0, generic attributes are implemented as simple Name-Value-Pairs with a predefined set of supported data types (gen:intAttribute, gen:doubleAttribute, gen:stringAttribute, gen:dateAttribute, gen:uriAttribute).
Additional properties for core:_CityObject	1	10-055	Claus Nagel	2010-02-26
The position of a CityObject regarding the surrounding terrain or water is important for varies application. If a terrain model is missing in the 3D city model, this position cannot be determined. If a terrain model is available though, this position can still not clearly be defined due to different geometric representations of the terrain in different level of details.
CityGML Change Request - Description of Doors and Windows	1	10-058	Nobuhiro Ishimaru	2010-02-26
Add the descriptions, such as door opening direction, how to open it, or if it is an automatic door.
CityGML Change Request - Description of Storey	1	10-057	Nobuhiro Ishimaru	2010-02-26
Clarify the description of Storey by any of the followings. 1) Add Storey class to Fig.25, and modify the clause 10.3.6. 2) Define individual fixed attribute "storey number" in clause 10.3.6.
CityGML Change Request - Network topology for indoor routing	1	10-056	Hideki Hayashi	2010-02-26
Add a network topology model necessary to realize the indoor routing. The network topology model is used to indicate a connection between spaces or rooms, and it is also used to calculate migration pathway of humans, objects or robots.
Surface property specification	1	10-050	Claus Nagel	2010-02-26
The current Appearance implementation heavily favors visualization data (colors), even though the specification states “Appearances are not limited to visual data but represent arbitrary categories called themes such as infrared radiation, noise pollution, or earthquake-induced structural stress”. All these different categories or surface properties require differing data representations, which are not possible to convey in a straightforward and well-defined manner in CityGML 1.0 and cannot be made explicit unless a specific ADE is defined. In particular, there is no obvious way to specify “non-color” materials.
enhance mask/ MaskInformation/ type	1	10-023	Stephan Zinke	2010-02-26
RapidEye's standard products (metadata) contain masks which mask not only clouds but as well other type of "unusable" data, e.g. missing lines, no data, etc. The UDM (unusable data mask) contains a bitmask with layers for clouds, no-data, band-specific problems, cf. RE Standard Product Specification at http://www.rapideye.de/upload/documents/PDF/RE_Product_Specifications_ENG.pdf
OGC-NA should review names in OGC standards	1	10-042	Simon Cox	2010-02-26
Most OGC implementation specification include definitions of persistent names that should be used in deployments conformant to the specification. These include XML Namespaces, URIs for 'definitions', MIME-type declarations, and various abbreviations. This should be reviewed by the OGC-NA prior to publication to ensure consistency with OGC name policies and to avoid clashes with other standards. Consistency is particularly important to enable complex applications and workflows involving multiple OGC standards, and as OGC moves towards better harmonization with generic web standards.
Modify maximum number of times an Input may be present	1	10-022	Alexander Padberg	2010-02-26
WPS does not support processes with an arbitrary number of a certain Input parameter with the same Identifier (for example a list of references or IDs where the number of entries is arbitrary). At the moment, the developer has to specify an upper limit (maxOccurs) for every Input in the process description (see Table 19 - parts of InputDescription data structure, maxOccurs)
Generic attributes for Appearance model	1	10-049	Claus Nagel	2010-02-26
Generic attributes as simple means for extending CityGML are very helpful to store additional, native information in CityGML objects, or to easily transport additional data to customers without the need for explicitly defining an ADE (which are not necessarily supported by CityGML-enabled software). Thus, all _CityObject-derived classes provide this capability. The major Appearance model classes are not derived from _CityObject but nevertheless should provide this convenient mechanism.
Replace ref syntax with xpath	1	10-045	Stefan Below	2010-02-26
The “ref” syntax used for connecting SensorML and SweCommon elements should be replaced. Navigating only on “property” elements or name attributes is error prone and cumbersome. This is especially problematic when writing application schemas extending SensorML. Sticking to the property navigation mechanism results in serious naming issues. Different objects with the same property cannot be used since they aren’t accessible. Also, the general OGC policy of reusing established IT technology implies the usage of XPath.
Fixing of ArrayLink	1	10-024	Stefan Below	2010-02-26
The ArrayLink in SensorML has some issues. It is insufficient for connecting/linking arrays. More documentation is required.
Clarify OGC versioning and backward compatibility policy	1	10-044	Simon Cox	2010-02-26
Elements of OGC versioning policy are provided in a number of places in the OGC P&P and in the OGC Directives on writing standards. These are generally consistent, but not fully clear to some members submitting documents for considerations as revisions of OGC standards. The versioning policy should be described in a single place in the P&P.
Additional boundary surfaces for building	1	10-047	Claus Nagel	2010-02-26
The current set of thematic classes representing the boundary surfaces of buildings has to be extended in order to be able to semantically classify the entire exterior shell of a building. For example, the floor surface of a loggia/balcony can neither be modeled as bldg:GroundSurface (which may only be used for the ground plate of the building) nor as bldg:FloorSurface (restricted to floor surfaces of interior rooms in LOD4). Further additional boundary surface types are required.
Thematic module for man-made subsurface structures	1	10-048	Claus Nagel	2010-02-26
Man-made subsurface structures such as tunnels, pedestrian subways, underground stations or subsurface buildings are essential urban objects which have to be adequately represented in virtual 3D city and landscape models. However, CityGML 1.0 does not provide a semantic model explictily dedicated to man-made subsurface structures. The only possibility to model and exchange subsurface objects in CityGML 1.0 is to use a GenericCityObject as proxy. Alternatively, a corresponding ADE could be defined. Both approaches face disadvantages. First, GenericCityObjects are simple in structure and are hence not suitable to replace a semantically rich model for underground objects. Second, subsurface structures are not specific to just a single application domain. Several ADEs could emerge proposing different semantic models. What is required is a common and standardized thematic module on man-made subsurface structures in CityGML.
Standard properties for boundary surfaces	1	10-046	Claus Nagel	2010-02-26
The current definitions of the feature class bldg:_BoundarySurface and its child classes do not provide a common set of standard properties for boundary surfaces such as "fire rating" or "load bearing" which are feasible in more than one application domain. As for CityGML 1.0, these common properties can only be modeled and exchanged as generic attributes or using the CityGML ADE mechanism.
serviceTypeID data type obsolete	1	10-016	Lorenzo Bigagli	2010-02-01
The data type of the serviceTypeID attribute of the Catalogue Service class is "URI, as specified in IETF RFC 2396" (see table 5). But RFC 2396 is now obsolete (RFC 3986 is the replacement). Moreover, OGC Commons mandates that its value be "OWS type abbreviation (e.g., “WMS”, “WFS”)". Lastly, in table 57 it is set to "fixed value of "CSW""
Query results default ordering inconsistency	1	10-015	Lorenzo Bigagli	2010-02-01
The default ordering of query results in inconsistently defined in the document: - Table 10 (UML attributes and roles in “query” operation request): sortSpec default is sorted on ID in descending order - §10.8.4.12 SortBy parameter: no default defined - Table 65 (KVP encoding for GetRecords operation request): default action is to present the records in the order in which they are retrieved
Operation level roles and security	1	10-013	Mike Botts	2010-02-01
There is expressed need for operation-level security based on roles. For example, an SOS may wish to allow a particular user to request one operation but not a different operation, while other users could request both.
Operation-level roles and security	1	10-014	Mike Botts	2010-02-01
There is expressed need for operation-level security based on roles. For example, an SPS may wish to allow a particular user to perform one operation but not a different operation, while other users could request both.
first sentence of overview is not a sentence.	1	10-010	Don Nadeau	2010-01-26
not a complete sentence.
CSW ISO Profile should use GML 3.2.1	1	10-012	Simon Cox	2010-01-26
The ISO Profile for CSW is the only normative publication of an XML Schema for ISO 19119, so the schema documents published at http://schemas.opengis.net/iso/19139/20060504/srv/ are the only normative ones available. There are a number of problems with this schema, including: 1. the XML namespace used is http://www.isotc211.org/2005/srv - this was never authorized by the owners of the http://www.isotc211.org domain; 2. the schema s the gco and gmd namespaces via a local copy of an interim version of the ISO 19139 implementation of the ISO 19115 metadata schema. In turn this s GML using a local copy of an interim version of GML, which was never formally published. The XML namespace used for the GML components is the one used for all versions of GML up to GML 3.1, but the schema documents are close to what was eventually published as GML 3.2.1. This complicates its use in combination with other GML-based schemas in applications that correctly use official releases of GML.
SensorML Add a statistical qualifier attribute to the Quantity class	1	10-006	Ollie Raymond	2010-01-26
The GeoSciML design group is considering using swe:Quantity to handle numeric values, and request an explicit attribute to describe the statistical type (eg, mean, median) of the quantity value. There are other options for denoting statistical types (eg: using the definition attribute, or xlink:role) but these are not attributes which explicitly denote statistical type.
planimetric building footprints in LOD0	1	10-007	Carsten Roensdorf	2010-01-26
improve the utilisation of existing 2D datasets (topographic building footprints) in the creation of 3D city models. This will allow models to include 2D data that can be rendered in 3D where feature height information does not exist.
Add support for fine grained raster input/output description	1	10-005	Bastian Schäffer	2010-01-26
WPS is lacking support for allwoing fine grained specification of raster input, such as 2 banded 32 unsigned int raster in geotiff format
Web Map Service (WMS) Implementation Specification	1	09-187	Paul Lacey	2009-12-22
The OGC Web Map Service (WMS) specification states that all data layers in the view must have the same projection and datum. However, in order to achieve this some of the data may have needed prior transformation (conversion from one Coordinate Reference System and projection to another) . The issue is that the WMS specification does not currently allow the service creator to record that a transformation has taken place or how it was done.
Improve specification of complex data input/output formats in process description	1	09-184	Edward Nash	2009-12-22
In WPS 1.0.0 the format of complex inputs/outputs to processes was specified using a tuple of (mimeType, encoding, schema). This allows only a very broad specification of the data format, and it is not possible for a client to correctly provide data using only this information, e.g.: - for an XML input it may be necessary to provide a specific root element. This cannot be specified. - for an XML input it may be necessary to provide a specific structure under the root element (e.g. a gml:FeatureCollection containing elements from a particular application schema, or features having a particular class of geometry attribute such as surface). This cannot be specified. - for a coverage input it may be necessary to provide a certain number of bands. - official mime types are not available for all geographic data types (e.g. GeoTIFF is not fully described by image/tiff). Identification of the correct format was only possible through manually inspecting the natural-language description (abstract) of the input/output. Additionally, for each input/output it is necessary to repeat the data type definition - e.g. for a process accepting 3 inputs and one output, all with an identical format, the same list of accepted and default formats must be given in total 4 times.
Add a Transactional Profile (WPS-T)	1	09-189	Bastian Schäffer	2009-12-22
WPS specification a lacking support for on-the-fly deployment of processes.
Need of more than one ABSTRACT for different languages	1	09-179	Marta Codinachs	2009-12-22
When there is a need of describing the processes and its parameters in different languages, it is not possible to do it using more than one ABASTRACT each with its xml:lang="xx" attribute.
Add separate property for sampling domain	1	09-180	Alexandre Robin	2009-12-22
The current model allows for the feature of interest to be either a domain feature or a sampling feature. This confuses the model and makes it especially difficult for filtering mechanisms to anticipate what kind of properties the feature of interest has. It is also not completely logical that the domain feature is nested inside the sampling feature when this last one is used.
Web Processing Service Change Request – methods for controlling, and checking the status of asynchronous process	1	09-109r1	Arif Shaon, Andrew Woolf	2009-12-07
Final version of CR 09-109
Clarification of Reference / ServiceReference Usage	1	09-173	Jolyon Martin	2009-11-20
Reference/ServiceReference is going to be used by SPS in its DescribeResultAccess operation to inform clients from which services they can retrieve data.
Multi-Language Support via AcceptLanguages Parameter	1	09-174	Jolyon Martin	2009-11-20
SPS needs to support responses with messages in multiple languages (e.g. both in French and English)
Profile version identification	1	09-172	Jolyon Martin	2009-11-20
The OWS Common 1.2 SWG Scope of Work includes the need to Define a URN to Identify Service Type, this should consider profile versions
Clarification of profile property	1	09-176	Jolyon Martin	2009-11-20
The "profile" property should be revised to support this new concept.
Request Base Type	1	09-175	Jolyon Martin	2009-11-20
The XML complexType "RequestBaseType" shown in 9.2.3 is NOT included in the schema of OWS Common 1.2 - this requires all specifications to copy the type definition in their own schema instead of just extending the type from OWS Common
Fix DistanceType to allow content within element	1	09-141	Tom Ingold	2009-11-20
Add the \"mixed\" attribute to the definition of DistanceType (http://schemas.opengis.net/filter/1.1.0/filter.xsd line 150) with a value of true.
Guidelines for creating and using WSDL	1	09-168	Jolyon Martin	2009-11-20
Provision of another - optional - section of the Capabilities document that can be queried by clients for WSDL description of a service within the XML Schema from OWS Common for the CapabilitiesBaseType
Service Identity	1	09-171	Jolyon Martin	2009-11-20

SOAP Exception	1	09-169	Jolyon Martin	2009-11-20
Improved Exception report within SOAP encoding
SOAP Version	1	09-170	Jolyon Martin	2009-11-20
OWS Common should be agnostic to the SOAP version so that implementations may choose freely.
CR SensorML - Enhancement of Connections.	1	09-160	Stefan Below, Arne Bröring	2009-11-16

Answers to the NO votes during the vote for adoption of WMTS 1.0.0	1	09-154	Joan Masó	2009-11-10

Design of ElementSetName/@typeName attribute	1	09-152	Lorenzo Bigagli	2009-11-03
Deprecation of ElementSetName/@typeName. Definition of Query/@resultTypeName, replacing it, with the exact same semantics and use.
Support for geometry types Null and Circle	1	09-150	Andreas Matheus	2009-11-03
Add support for the geometry types Null and Circle. This can be undertaken by (i) specifying all relevant adidtions in the new version of the GeoXACML specification, or (ii) by having ISO 19125 changed as such it will support the geometry types Null and Circle and become the new reference for the new version of the GeoXACML specification.
OGC Web Map Service 1.3.0 Corrigendum 1. Abstract test suite	1	09-111	Chuck Morris	2009-10-17
Uploaded by Joan Maso
GML change request - Add ReferencedGridByTrhansformation	1	09-091r1	Arliss Whiteside	2009-10-16

CR CSW ebRIM CR GetRepositoryItem Response In SOAP	1	09-136	Frédéric Houbie, Fabian Skivée	2009-09-28

CR CSW ebRIM CR Improve ElementSetName Definition	1	09-137	Frédéric Houbie, Fabian Skivée	2009-09-28

CR CSW ebRIM Add InternationalString DataType	1	09-134	Frédéric Houbie, Fabian Skivée	2009-09-28

CR CSW ebRIM CR Encode metadata In GetRecordsResponse	1	09-135	Frédéric Houbie, Fabian Skivée	2009-09-28

CR CSW ebRIM Change GetCapabilities service parameter value	1	09-133	Frédéric Houbie, Fabian Skivée	2009-09-28

OGC schema repo reorganization	1	09-128		2009-09-10
proposed OGC schema repo reorganization based on 06-135r7
Simplify KVP encoding	1	09-121	Peter Schut	2009-09-08
Simplify and improve the WPS operations using KVP encoding. Conform with conventions compatible with REST.
GML change request - Add ReferencedGridByTransformation	1	09-091	Arliss Whiteside	2009-08-11

Web Processing Service Change Request – methods for controlling, and checking the status of asynchronous process	1	09-109	Arif Shaon, Andrew Woolf	2009-08-06
Integrating OGC services with Grid technology is increasingly being seen as beneficial within the OGC community. The latest OGC test bed OWS-6 has run a thread of work that focused on integrating WPS with Grid computing to enable effective handling of resource-intensive geo-processes through standardised WPS. This work identified that the current version of WPS specification does not provide any mechanism for controlling an asynchronous process, which is a standard function of a Grid infrastructure and is often useful for managing the resources used by long running processes. We therefore envision that the users of a Grid-enabled WPS should have this option in order to be able to utilise the full benefit of Grid technology through standardised WPS. The WPS 1.0.0 specification does not provide any mechanism for querying the status of an asynchronous process, though the specification does require an ExecuteResponse document for an asynchronous process to contain a “statusLocation” attribute for indicating the status URL for the process. This often leads to ad-hoc approaches to implementing a suitable function for checking the status of asynchronous processes through standardised WPS. Hence, it results in non-interoperability between WPS clients, SOAP-based workflows in particular that have the need to submit an asynchronous process for execution, check its status for completion and retrieve the final output through a standardised WPS in an automated way.
WPS Change Request -"GetStatus" Method	1	09-094r1	Arif Shaon, Andrew Woolf	2009-08-03
An Official OGC CR document that proposes a new operation for checking the status of asynchronous WPS process to be included in the WPS specification
WPS Change Request - Controlling Asynchronous Process	1	09-093r2	Arif Shaon, Andrew Woolf	2009-08-03
An Official OGC Change Request document for including a new operation in the WPS specification for controlling asynchronous processes through WPS
WPS 1.0 Change Request - KVP encoding	1	09-107	Peter Schut and Steven Keens	2009-07-31

Support for SensorML	1	09-101	Mike Botts	2009-07-07
CR #8 for 05-007r7
Unify filters in GetOberservation requests in a common place	1	09-098	Alain Tamayo Fong	2009-07-07
CR #5 for 06-009r6
Specify the number of filters supported by servers	1	09-097	Alain Tamayo Fong	2009-07-07
CR #4 to 06-009r6
Define more precisely the format of time values supported by servers	1	09-096	Alain Tamayo Fong	2009-07-07
CR #3 to 06-009r6
WPS Change Request - Controlling Asynchronous Process	1	09-093r1	Arif Shaon, Andrew Woolf	2009-06-25
Updates to OGC Doc 09-093
WPS Change Request - "GetStatus" Method	1	09-094	Arif Shaon, Andrew Woolf	2009-06-23
An Official OGC CR document that proposes a new operation for checking the status of asynchronous WPS process to be included in the WPS specification
WPS Change Request - Controlling Asynchronous Process	1	09-093	Arif Shaon, Andrew Woolf	2009-06-23
An Official OGC Change Request document for including a new operation in the WPS specification for controlling asynchronous processes through WPS
OWS-6 AIXM 5.0 XSD CR	1	09-089	David Burggraf	2009-06-16

CR - CIM EP Conformance and ATS	1	09-074r1	ML. Vautier	2009-06-02

CIM EP Conformance and ATS	1	09-074	ML Vautier	2009-05-28

GML 3.2.1 change request - Change association to GeneralParameterValue	1	08-150r3	Arliss Whiteside	2009-05-27

OWS-6: Clarify interval value format in GetMap requests	1	09-070	Chuck Morris	2009-05-19
Change Request to Web Map Service (WMS) Implementation Specification / 1.3.0
Correct the base type and facet pattern for TypeNameListType in the WFS 1.1.0 Schema	1	09-069	Gerhard Sommer	2009-05-19
GetFeature requests, which use typeNames in the Query element, that are correct according to the specification (i.e. containing underscores or making use of aliases), currently do not validate, if the implementation (i.e. GeoServer in strict cite-conformance mode) uses schema validation to verify the request.
OWS-6 FES2.0 CR AnyInteractsTemporal Operator	1	09-066r1	Ian Painter, Daniel Hardwick	2009-05-18

FES2.0 CR AnyInteractsTemporal Operator	1	09-066	Ian Painter, Daniel Hardwick	2009-05-15
Change Proposal for the creation of an AnyInteracts temporal operation for FES2.0
GML 3.2.1 change request - Change association to GeneralParameterValue	1	08-150r2	Arliss Whiteside	2009-05-12

OWS-6 CityGML CR	1	09-039	Clemens Portele	2009-05-11

EO EP Conformance and ATS	1	09-060	Marie-Lise Vautier	2009-05-07

IGM change request - Improve CovarianceMatrix encoding	1	08-188r1	Arliss Whiteside	2009-05-01

IGS/IGM change request: Use new ISO 19130 terms	1	09-029	Arliss Whiteside	2009-04-30

OWS-6 Styled Layer Descriptor (SLD) CR	1	09-013	Craig Bruce	2009-04-28
OWS-6 Styled Layer Descriptor (SLD) CR
OWS-6 Symbology Encoding (SE) CR	1	09-014	Craig Bruce	2009-04-28
OWS-6 Symbology Encoding (SE) CR
GML CR Extend TimeIndeterminateValueType	1	09-023r2	David Burggraf	2009-04-08

Policies Change Request	1	09-051	Peter Baumann	2009-04-01

OWS-6 DSS IHO S-52-Related Symbology Encoding CR - Draft 2009-03-25	1	09-043	Alessandro Triglia	2009-03-26

SensorML CR - Harmonize with ISO 19115-2 and ISO 19130	1	09-040	Simon Cox	2009-03-24
Request to make explicit the way that SensorML implements classes defined in the ISO imagery specs
CR for Schema Location URLS as described in 06-135r5/r6	1	09-024	Keith Pomakis	2009-03-09
The proposed use of 2-digit version numbers in URLs that locate schema files has significant negative implications!`
GML CR Extend TimeIndeterminateValueType	1	09-023r1	David Burggraf	2009-03-09

GML CR Extend TimeIndeterminateValueType	1	09-023	David Burggraf	2009-03-09

IGM change request - Correct UML model	1	09-004	Arliss Whiteside	2009-02-13

OWS Common change request - Allow alternative URLs for operation HTTP endpoints	1	09-011r1	Keith Pomakis	2009-01-22

OWS Common change request - Allow URL aliases for operation HTTP endpoints	1	09-011	Keith Pomakis (pomakis@cubewerx.com)	2009-01-19
A Capabilities document needs to be able to provide URL aliases for the 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 built-in throttles). A specific use case for this requirement is the WMTS GetTile request.
IGM change request - Not require application schema extensions	1	09-003	Arliss Whiteside	2009-01-19

IGM change request - Improve CovarianceMatrix encoding	1	08-188	Arliss Whiteside	2008-12-17

OWS Common change request – Swap order of REQUEST and VERSION parameters	1	08-209	Keith Pomakis	2008-12-16

OWS Common change request - Clarify "not empty"	1	08-201r1	Arliss Whiteside	2008-12-09

OWS Common change request - Clarify "not empty"	1	08-201	Arliss Whiteside	2008-12-04

Ocean Science Interoperability Experiment Phase II	1	08-200	Luis Bermudez	2008-12-04

GML 3.2.1 CR for CurveInterpolationType	1	08-194	Christian Grothe	2008-11-24
ML 3.2.1 CR for CurveInterpolationType
IGM change request - Improve OperationMethod description	1	08-187	Arliss Whiteside	2008-11-14

GML 3.1.1 Application schema for Earth Observation products	1	06-080r4	Jerome Gasperi	2008-11-07
This document describes the context of use of the Earth Observation (EO) Product GML application schema
OpenSearch Extensions for OGC Catalogues	1	08-169	Panagiotis (Peter) A. Vretanos	2008-10-31
Describes a set of additional OpenSearch parameters to support the kinds of queries that we do on OGC catalogues. Also proposes a method of using the OpenSearch "searchTerms" to invoke searches using these extended parameters.
CSW 3.0 change request - Distributed Search	1	08-086r1	Uwe Voges	2008-10-20
Improvement of definition what distributed search is, which alternatives for distributed search are available and what problems can arise. Functional extensions to the discovery request and response messages (which define elements that allow for the retrieval and comprehension of a distributed result set).
WFS 1.1 CR_BBOX/Filter	1	08-163	Jonathan Hankes	2008-10-06
Change Request WFS 1.1 BBOX/Filter
Standards best practice CR - variant XML implementations	1	08-162	Simon Cox	2008-09-30
Dependencies between specifications lead to the requirement sometimes to issue variant implementations when their XML implementations are available in several versions. A standard pattern for denoting these is required.
KML Change Request: Index addressable placemarks	1	08-161	Jack Gratteau	2008-09-26
Placemarks could be more like style – the index pointer selects a placemark from a linked list of places that can be defined in the document (as opposed to a link).
GML CR - parametyric CRS	1	08-158	Andrew Woolf	2008-09-23
Add support in GML for ISO 19111-2 parametric coordinate reference systems widely used for environmental data.
GML CR - spatiotemporal support	1	08-159	Andrew Woolf	2008-09-23
Add support in GML (and correct some anomalies) for spatiotemporal CRS and geometries.
GML CR - rangeType	1	08-157	Andrew Woolf	2008-09-23
Modify GML coverage classes to include ISO 19123 rangeType attribute, for harmonising approaches for range semantics.
GML CR: Use of GML schema components outside of GML application schemas	1	08-156	Clemens Portele	2008-09-19

GML CR - CityGML extension mechanism	1	08-154	Nicolas Lesage	2008-09-18

GML CR: Coverage encoding approach	1	08-151	Clemens Portele	2008-09-17

GML CR: Reconsider deferred enhancements	1	08-153	Clemens Portele	2008-09-17

Topic 2 change request - Change associations to GeneralParameterValue	1	08-149	Arliss Whiteside	2008-09-12

GML 3.2.1 change request - Change association to GeneralParameterValue	1	08-150r1	Arliss Whiteside	2008-09-12

Topic 2 change request - Correct inconsistencies	1	08-089r3	Arliss Whiteside	2008-09-12

Topic 2 change request - Correct inconsistencies	1	08-089r2	Arliss Whiteside	2008-09-11

GML 3.2.1 change request - Change associations to GeneralParameterValue	1	08-150	Arliss Whiteside	2008-09-11

SensorML CR - improve interface specification	1	08-146	M. Botts	2008-09-11

OWS Common 1.1 Change Request - Use HTTP status codes for OGC Exceptions	1	08-143r1	Steven Keens	2008-09-04
Add a section listing HTTP status codes for OGC exception codes.
OWS Common 1.1 Change Request - Use HTTP status codes for OGC Exceptions	1	08-143	Steven Keens	2008-09-02
Add a section listing HTTP status codes for OGC exception codes
GML CR defaultStyle.xsd is broken	1	08-136	GMLJP2 V1.1 SWG	2008-08-28

GML CR Schema Subsetting Scripts	1	08-137r2	David Burggraf	2008-08-28

GML CR Schema Subsetting Scripts	1	08-137	David Burggraf	2008-08-28

GML CR Schema Subsetting Scripts	1	08-137r1	David Burggraf	2008-08-28

GML CR AbstractFeatureMemberType XSD	1	08-135	David Burggraf	2008-08-28

GML CR AbstractFeatureMemberType XSD	1	08-135r1	David Burggraf	2008-08-28

OWS Common Temporal Conventions	1	08-121	James Ressler, Dave Wesloh	2008-08-15
Add Temporal Conventions to address TimeZone Offset Request and Service handling
Catalogue (CSW) 2.0.2 CR: ElementName schema declaration contradicts specification	1	08-117	R. Martell	2008-08-07
The csw:ElementName declaration in the CSW-discovery.xsd schema assigns the type xsd:QName. However, this prohibits the use of XPath expressions as described in cl. 10.8.4.9 and invalidates Example 1.
WFS CR - Support of License Information in response	1	08-115	Chris Body	2008-08-03
Optionally allow license information to be associated with a WFS response
GML CR - use xlinks for property metadata	1	08-113	Simon Cox	2008-08-03
A pattern for the use of xlinks to attach feature-property metadata.
GML CR - deprecate various components	1	08-114	Simon Cox	2008-08-03
Some components in GML are immature, redundant, or would be better implemented outside the GML namespace. This CR identifies a number of those and recommends that they be marked "deprecated" pending them being refactored in a future version of GML
GML CR - allow "double" in TimePositionUnion	1	08-106	Simon Cox	2008-08-02
Representation of time position in GML does not allow the scientific "e" notation. This is inconsistent with the rest of GML where "xs:double" is the generic numeric form.
GML CR - encoding rule for UML redefine	1	08-112	Simon Cox	2008-08-02
UML redefine (override) is not currently implemented as a GML encoding rule. This CR proposes a solution, which requires one new tagged value, and Schematron.
GML CR - add temporal aggregates	1	08-108	Simon Cox	2008-08-02
A small number of temporal aggregate types are missing from GML, so had do be defined in SWE Common. GML should assume ownership of these.
GML CR - clarify identifier usage	1	08-110	Simon Cox	2008-08-02
GML provides gml:id, gml:identifier and gml:name for labels and identifiers. This CR proposes to add more guidance about how to use these.
GML 3.1.1 change request - Correct grid cell terms	1	08-082	Arliss Whiteside	2008-07-29

Topic 2 change request - Correct inconsistencies	1	08-089r1	Arliss Whiteside	2008-07-29

GML 3.2.1 change request - Correct grid cell terms	1	08-080	Arliss Whiteside	2008-07-29

Topic 2 change request - Correct grid cell terms	1	08-010r1	Arliss Whiteside	2008-07-29

OWS Common change request - Add general reference system Approach C	1	07-059r5	Arliss Whiteside	2008-07-29

OWS Common change request: support multilingual services	1	08-016r3	Peter Schut	2008-07-23

Filter 1.1 CR: Missing geometry types in GeometryOperandType definition	1	08-100	R. Martell	2008-07-21
The enumerated type ogc:GeometryOperandType incompletely covers GML 3.1 geometry types and omits several rudimentary types allowed by the GML Simple Features Profile (GMLSF 1.0, OGC 06-049).
Catalogue (CSW) 2.0.2 CR: Filter_Capabilities element is mandatory	1	08-099	R. Martell	2008-07-21
The element that is introduced as an extension element in csw:CapabilitiesType is required; this is inconsistent with the other top-level elements defined in OWS Common (OGC 05-008), all of which are optional in order to permit selective retrieval using the ‘sections’ parameter.
Catalogue (CSW) 2.0.2 CR: Service & version request parameters have fixed values	1	08-098	R. Martell	2008-07-21
The service and version request parameters defined in the CSW part (cl. 10) have fixed values (“CSW” and “2.0.2”, respectively) that prohibit profiling.
SLD Profile of WMS Change Request	1	08-064	Justin DeOliveira	2008-06-25

OWS Common change request: support multilingual services	1	08-016r2	Peter Schut, Keith Pomakis	2008-06-13
clarification to the use of MUL
Topic 2 change request - Correct inconsistencies	1	08-089	Arliss Whiteside	2008-06-06

OWS Common change request: Add SOAP encoding	1	06-094r1	Bastian Schaeffer	2008-05-15

OWS Common change request - Add general reference system version B	1	07-059r3	Arliss Whiteside	2008-05-13

OWS Common change request - Add general reference system version A	1	07-059r2	Arliss Whiteside	2008-05-13

Clarification of Sorting CSW Unconstrained Query Results	1	08-061	Archie Warnock	2008-04-08
Removes an ambiguity in the ordering of results returned from an unconstrained query.
CSW Change Request - support OpenSearch patterns	1	08-057	Doug Nebert	2008-03-24

WMC 1.1.0 Change Request: default namespace	1	08-045	Tom Kralidis	2008-03-11

WMC 1.1.0 Change Request: context:LayerType	1	08-047	Tom Kralidis	2008-03-11

WMC 1.1.0 Change Request: xlink namespace	1	08-046	Tom Kralidis	2008-03-11

WFS-1.1: Abstract test cases for XLink	1	08-044r1	R. Martell (ed.)	2008-03-07

WFS-1.1: Abstract test cases for XLink	1	08-044	R. Martell	2008-03-07

FE 1.1 Corrigendum 1	1	08-043	Clemens Portele	2008-03-06
Draft corrigendum for Filter Encoding 1.1.0
WFS 1.1 Corrigendum 1	1	08-042	Clemens Portele	2008-03-06
Draft Corrigendum for WFS 1.1.0
GMLJP2 Change Proposal	1	08-040	David Burggraf	2008-03-06

Topic 2 change request - Correct grid cell terms	1	08-010	Arliss Whiteside	2008-03-04

Combined SPS CRs from OWS-5 CITE	1	08-032	Johannes Echterhoff	2008-02-27
This document contains the change requests that address issues identified in the OWS-5 CITE thread for SPS (07-014r3).
SWECommon CR - Improve Documentation	1	08-026	Alexandre Robin	2008-02-25

SWECommon CR - Improve Extensibility Mechanisms	1	08-024	Alexandre Robin	2008-02-25

SWECommon Change Request - Add Choice + Optional Fields	1	08-025	Alexandre Robin	2008-02-25

OWS_Common_Add_nilValue_element_Change_Request	1	08-012	David Burggraf	2008-02-06

OWS Common 1.1 Change Request – Update Sequence and Contents Parameter Precedence	1	08-013	Steven Keens	2008-01-30
Dictate the precedence rules when UpdateSequence and Contents parameters conflict.
OWS Common 1.1 Change Request – Nested KVP parameter encoding	1	08-011	Steven Keens	2008-01-28
Provide a standard mechanism to nest parameters
OWS Common change request - Add general reference system	1	07-059r1	Arliss Whiteside	2008-01-21

Implementation Specification for Geographic Information - Simple feature access - Part 1: Common Architecture v1.2.1	1	06-103r4	John Herring	2007-11-27

Implementation Specification for Geographic Information - Simple feature access - Part 2: SQL option v1.2.1	1	06-104r4	John Herring	2007-11-27
corregendum
SE Change request for thematic mapping	1	07-105	Ionut Iosifescu	2007-08-27

CSW change request: Improve SOAP binding	1	06-090	Arliss Whiteside	2006-07-03

CSW change request: Correct SOAP binding	1	06-089	Arliss Whiteside	2006-07-03

WFS change request: Improve SOAP binding	1	06-088	Arliss Whiteside	2006-07-03

WFS change request: Correct SOAP binding	1	06-087	Arliss Whiteside	2006-07-03

CS-W change proposal for SOAP profile	1	04-042	Richard Martell	2004-12-13

WFS-T change proposal for SOAP profile	1	04-041	Richard Martell	2004-12-13

	Learn About OGC
	Membership Benefits
	Endorsements
	Join OGC
	OGC Standards
	OGC Network™
	OGC Public Forum
	Registered Products
	Domains
	Get Certified
	Learn How To

Standards

OGC Schema Repository Updates

Social Media

Areas of Interest

Change Requests by Date