Response .1 Response semantics ListStoredQueries operation .1 Request Semantics
14.5.1 Request Semantics
A stored query may be created using the CreateStoredQuery see Figure 27 operation. CreateStoredQuery + query [0. .] : St oredQueryDescript ion BaseRequest + service : Charact erSt ring = WFS {frozen} + version : Charact erSt ring = 2.0.0 {frozen} + handle [0..1] : CharacterString StoredQueryDesc ription + title [0..] : LocalisedCharacterString + abstract [0..] : LocalisedCharacterString + metadata [0..] : Any + id : URI + parameter [0..] : ParameterExpression + queryExpressionText [0. .] : QueryExpressionText Figure 27 — CreateStoredQuery request Not all stored queries that a server offers need to be created using the CreateStoredQuery operation. Servers can be pre-configured to offer any number of stored queries implemented in any number of ways. It is anticipated that profiles of this International Standard may define sets of stored queries that compliant WFSs must offer. NOTE It is further anticipated that in many cases, for the sake of efficiency and performance, pre-configured stored queries would be implemented as executable code. Such implementations would also allow for complex query logic to be implemented and hidden behind a simple stored query interface.14.5.2 XML encoding
The following XML Schema fragment defines the XML encoding for the CreateStoredQuery operation. xsd:element name=CreateStoredQuery type=wfs:CreateStoredQueryType xsd:complexType name=CreateStoredQueryType xsd:complexContent xsd:extension base=wfs:BaseRequestType xsd:sequence xsd:element name=StoredQueryDefinition type=wfs:StoredQueryDescriptionType minOccurs=0 maxOccurs=unbounded xsd:sequence xsd:extension xsd:complexContent xsd:complexType14.5.3 KVP encoding
No KVP-encoding is defined for the CreateStoredQuery operation.14.5.4 Parameter discussions
The StoredQueryDefinition parameter, encoded using the wfs:StoredQueryDefinition element, shall contain the definition of a stored query. Multiple stored queries may be created in a single CreateStoredQuery request. 88 Copyright © 2010 Open Geospatial Consortium See 14.2 for a description of the wfs:StoredQueryDescriptionType type.14.5.5 Response
Figure 28 describes the response to a CreateStoredQuery operation. ExecutionStatusResponse + status : Charact erSt ring = OK {frozen} Figure 28 — CreateStoredQuery response The following XML Schema fragment defines the response to a CreateStoredQuery operation: xsd:element name=CreateStoredQueryResponse type=wfs:CreateStoredQueryResponseType xsd:complexType name=ExecutionStatusType xsd:attribute name=status type=xsd:string fixed=OK xsd:complexType xsd:complexType name=CreateStoredQueryResponseType xsd:complexContent xsd:extension base=wfs:ExecutionStatusType xsd:complexContent xsd:complexType The root element of the response is wfs:CreateStoredQuery that contains a single attributed named status. The only valid value for the status attribute is OK indicating that the stored query was successfully processed and stored by the server. Otherwise the server shall generate an exception see 7.5. 14.6 DropStoredQuery operations 14.6.1 Request SemanticsParts
» 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