Parameter ordering and case
6.4 Service bindings
The main body of this International Standard defines the encoding of WFS request and response messages, independent of any particular communication protocol. However, implementations of this International Standard shall support one of HTTP GET, HTTP POST or SOAP over HTTP POST see Clause 2. Annex D contains a detailed discussion of these service bindings. 7 Common elements7.1 Encoding of features
Servers that conform to this International Standard shall operate upon features encoded using GML. The version of GML that shall be supported is ISO 19136:2007. However the operations in this International Standard are defined in a manner that allows them to work with pervious and future versions of GML. So, servers may implement support for additional versions of GML, other than ISO 19136:2007. Servers shall advertise all supported versions of GML in their capabilities document using the inputFormat and outputFormat parameter domains see Table 12. Servers may also support additional non-GML feature encodings that shall also be listed in the servers capabilities document see Table 12. However, this International Standard does not describe how a server would operate upon such encodings. 7.2 Resource Identifiers 7.2.1 Assigning resource identifiers Each feature instance in a WFS shall be assigned a persistent unique resource identifier which is assigned by the server when the feature is created. This identifier shall be invariant under all WFS operations including delete which means that a resource identifier cannot be reused once it has been assigned. Resource identifiers are not intended to associate WFS resources with real world objects and the values do not have to be meaningful outside the scope of a web feature service instance.7.2.2 Encoding resource identifiers
For features encoded using GML, the resource identifier shall be encoded in the XML attribute gml:id. This International Standard does not describe how resource identifiers are encoded for other output formats. Within filter expressions, specific feature instances can be identified using the fes:ResourceId element. If the server supports versioning, specific versions of a feature can be referenced using the versionAction attribute contained within an fes:ResourceId element see ISO 19143, 7.11.2.7.2.3 Version identification
If the server supports versioning of features, then the server shall maintain version information about each feature instance. This International Standard makes no assumptions about how that version information is maintained. Functions defined in the Filter Encoding Standard see ISO 19143, 7.11.2 allow version navigation based on the resource identifier.Parts
» feature identifier Change Requests | OGC
» namespace XML operation Change Requests | OGC
» response model schema Change Requests | OGC
» Uniform Resource Identifier Change Requests | OGC
» Abbreviated terms Use of examples
» State machine notation UML Notation .1 Class diagrams
» Version number form and value
» Appearance in service metadata and in requests
» Version number negotiation Introduction
» Namespaces Change Requests | OGC
» Service bindings Change Requests | OGC
» Encoding of features Change Requests | OGC
» Encoding resource identifiers Resource Identifiers .1 Assigning resource identifiers
» Version identification Resource Identifiers .1 Assigning resource identifiers
» Predicate expression encoding Change Requests | OGC
» KVP encoding Base request type .1
» handle parameter Base request type .1
» Parameter Semantics KVP encoding
» startIndex parameter count parameter
» resultType parameter Base request type .1
» outputFormat parameter Base request type .1
» KVP encoding resolve parameter
» resolveDepth parameter resolveTimeout parameter
» Unresolvable references Standard resolve parameters .1
» KVP encoding inputFormat parameter
» srsName parameter Standard input parameters .1
» XML encoding Standard response parameters .1 Parameter Semantics
» KVP encoding Standard response parameters .1 Parameter Semantics
» numberMatched parameter numberReturned parameter
» Declaring transactional consistency Transactional consistency of response paging
» Response paging with transactional consistency
» Response paging without transactional consistency
» Use of the schemaLocation attribute
» KVP encoding Ad hoc query expression .1
» typeNames parameter Parameter discussion
» schema-element function Parameter discussion
» aliases parameter Parameter discussion
» Request Semantics Projection clause
» PropertyName parameter Parameter discussion
» Standard resolve parameters Parameter discussion
» srsName parameter Resolution path
» XML Encoding Selection clause
» Shared properties KVP encoding
» Use of the schema-element function in joins
» Coordinate reference system handling
» Request Semantics Sorting clause
» KVP encoding Sort processing
» KVP encoding Stored query identifier Stored query parameters
» KVP encoding Request .1 Request Semantics
» XML encoding Response .1 Response Semantics
» Capabilities document Response .1 Response Semantics
» Introduction Parameter domains FeatureTypeList section
» Service and operation constraints
» Introduction Extension points Change Requests | OGC
» Exceptions Introduction Change Requests | OGC
» outputFormat parameter Parameter discussion .1
» Supporting multiple namespaces Response .1 Introduction
» Introduction Change Requests | OGC
» Standard resolve parameters Parameter discussion .1 Standard presentation parameters
» valueReference parameter Parameter discussion .1 Standard presentation parameters
» state parameter Response .1 Response Semantics
» Standard response parameters Response .1 Response Semantics
» Exceptions Change Requests | OGC
» state parameter Parameter discussions .1 lockId parameter
» Standard response parameters Parameter discussions .1 lockId parameter
» Single query response Parameter discussions .1 lockId parameter
» Multiple query response Parameter discussions .1 lockId parameter
» Join query response Parameter discussions .1 lockId parameter
» Introduction Introduction Change Requests | OGC
» State machine for WFS locking
» Response semantics Request .1 Request Semantics
» lockAction parameter Parameter discussion .1 expiry parameter
» resultType parameter Parameter discussion .1 expiry parameter
» Introduction Response .1 Introduction Change Requests | OGC
» Title, Abstract and Metadata parameters
» name parameter Metadata parameter
» type parameter Metadata parameter
» Declaring the returned feature types Implementation language IsPrivate parameter
» KVP encoding ListStoredQueries operation .1 Request Semantics
» Response Exceptions ListStoredQueries operation .1 Request Semantics
» Request Semantics KVP encoding
» Response .1 Response semantics ListStoredQueries operation .1 Request Semantics
» Parameter discussions ListStoredQueries operation .1 Request Semantics
» releaseAction parameter Parameter discussions .1 Locking
» srsName parameter Parameter discussions .1 Locking
» Standard input parameters Parameter discussion .1 Filter expression
» Filter expression Parameter discussions .1 typeName attribute
» TransactionSummary element Response .1 Response Semantics
» InsertResults element Response .1 Response Semantics
» UpdateResults element Response .1 Response Semantics
» ReplaceResults element Response .1 Response Semantics
Show more