Filter expression Parameter discussions .1 typeName attribute
Copyright © 2010 Open Geospatial Consortium
97 15.2.8 Native action
It is clear that an open interface may only support a certain common set of capabilities. The wfs:Native element is intended to allow access to vendor specific capabilities of any particular WFS or data store.
The wfs:Native element is defined by the following XML Schema fragment:
xsd:element name=Native type=wfs:NativeType substitutionGroup=wfs:AbstractTransactionAction
xsd:complexType name=NativeType mixed=true xsd:complexContent
xsd:extension base=wfs:AbstractTransactionActionType xsd:sequence
xsd:any processContents=lax namespace=other minOccurs=0 xsd:sequence
xsd:attribute name=vendorId type=xsd:string use=required xsd:attribute name=safeToIgnore type=xsd:boolean use=required
xsd:extension xsd:complexContent
xsd:complexType
The wfs:Native element simply contains the vendor specific command or operation. The vendorId attribute shall be used to identify the vendor that recognizes the command or operation
enclosed by the wfs:Native element. The attribute is provided as a means of allowing a web feature service to determine if it can deal with the command or not. Valid vendorId values shall be advertised, using a parameter
constraint named vendorId, in the services capabilities document see 8.3.3.
The safeToIgnore attribute is used to guide the behaviour of a web feature service when the Native action is not recognized. The safeToIgnore attribute has two possible values True or False. The values have the
following meanings:
safeToIgnore=False A value of False indicates that the wfs:Native element cannot be ignored and the operation that the element is
associated with shall fail if the web feature service cannot deal with it. safeToIgnore=True
A value of True indicates that the wfs:Native element may be safely ignored.
EXAMPLE This example illustrates the use of the wfs:Native element to enable a special feature of a SQL-based
relational database. In this instance, the element indicates that this is an Oracle command and that the command may be safely ignored.
Native vendorId=Oracle safeToIgnore=True ALTER SESSION ENABLE PARALLEL DML
Native
15.3 Response 15.3.1 Response Semantics
In response to a Transaction request, a web feature service shall generate an XML document indicating the termination status of the transaction. In addition, if the Transaction request includes wfs:Insert elements, then
the web feature service shall report the feature identifiers of all newly created features.
Figure 31 describes the response to a Transaction operation.
98
Copyright © 2010 Open Geospatial Consortium TransactionResponse
+ transactionSummary : TransactionSummary + insertResults [0..1] : InsertResults
+ version : CharacterString = 2.0. 0 {frozen}
TransactionSummary + totalInserted : Int eger
+ totalDeleted : Integer + totalUpdated : Int eger
+ totalReplaced : Int eger InsertResults
+ feature [1..] : InsertResult
Ins ertResult + resource [1..] : ResourceId
+ handle [ 0..1] : CharacterString {transactionSummary.totalInserted0
implies insert Result s-notEmpty}
Figure 31 — Transaction response 15.3.2 TransactionResponse element
The root element of the response to a transaction request is called wfs:TransactionResponse. The following XML Schema fragment declares the wfs:TransactionResponse element:
xsd:element name=TransactionResponse type=wfs:TransactionResponseType
xsd:complexType name=TransactionResponseType xsd:sequence
xsd:element name=TransactionSummary type=wfs:TransactionSummaryType
xsd:element name=InsertResults type=wfs:ActionResultsType minOccurs=0
xsd:element name=UpdateResults type=wfs:ActionResultsType minOccurs=0
xsd:element name=ReplaceResults type=wfs:ActionResultsType minOccurs=0
xsd:sequence xsd:attribute name=version type=xsd:string use=required fixed=2.0.0
xsd:complexType
The wfs:TransactionResponse element contains a summary of the actions performed by the transaction and optionally a list of identifiers of any new features or feature versions created by the transaction.