Version number form and value
6.2.5.2 Parameter ordering and case
Parameter names shall not be case sensitive, but parameter values shall be case sensitive. In this International Standard, parameter names used in KVP encoding are typically shown in uppercase for typographical clarity, not as a requirement. Parameters in a request may be specified in any order. A web feature service shall be prepared to encounter parameters that are not part of this International Standard. In terms of producing results per this International Standard, a web feature service shall ignore such parameters.6.2.5.3 Parameter lists
Parameters consisting of lists shall be encoded as described in ISO 19143, 5.5. EXAMPLE In the case where multiple join queries see 7.9.2.5.3 are KVP-encoded, parentheses are used to isolate the various parameters so that their values align correctly. This is illustrated by the following example: TYPENAMES=ns1:F1,ns2:F2ns1:F1,ns1:F1ALIASES=A,BC,DFILTER=Filter … for A,B … FilterFilter…for C,D…Filter This KVP-encoded fragment encodes two join queries. The first query joins the feature types ns1:F1 and ns2:F2 which have been aliased to A and B. The second query joins the feature types ns1:F1 and ns1:F1 a self-join which have been aliased to C and D. The FILTER parameter encodes two filters, one for each query, delimited with parentheses. All the parameter values align 1:1. This fragment is equivalent to the following two individual KVP-encoded fragments: TYPENAMES=ns1:F1,ns2:F2ALIASES=A,BFILTER=Filter…for A,B…Filter TYPENAMES=ns1:F1,ns1:F1ALIASES=C,DFILTER=Filter…for C,D…Filter6.3 Namespaces
Namespaces see W3C XML Namespaces are used to discriminate XML vocabularies from one another. For the WFS there are four normative namespace definitions, namely: ⎯ http:www.opengis.netwfs2.0 - for the WFS interface vocabulary ⎯ http:www.opengis.netgml3.2 - for the GML vocabulary see ISO 19136:2007 ⎯ http:www.opengis.netfes2.0 - for the OGC Filter vocabulary see ISO 19143, 5.4 ⎯ http:www.opengis.netows1.1 - for the OWS Common vocabulary see OGC 06-121r3 In addition, WFS implementations may make use of one or more GML Application Schemas and these schemas will, in turn, use one or more application namespaces e.g. http:www.someserver.commyns. While many of the examples in this International Standard use a single namespace, multiple namespaces may be used, as shown in 11.3.3.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