📄 wfs.xsd
字号:
<xsd:attribute name="expiry" type="xsd:positiveInteger" use="optional" default="5"> <xsd:annotation> <xsd:documentation> The expiry attribute is used to set the length of time (expressed in minutes) that features will remain locked as a result of a LockFeature request. After the expiry period elapses, the locked resources must be released. If the expiry attribute is not set, then the default value of 5 minutes will be enforced. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:attribute name="lockAction" type="wfs:AllSomeType" use="optional" default="ALL"> <xsd:annotation> <xsd:documentation> The lockAction attribute is used to indicate what a Web Feature Service should do when it encounters a feature instance that has already been locked by another client application. Valid values are ALL or SOME. ALL means that the Web Feature Service must acquire locks on all the requested feature instances. If it cannot acquire those locks then the request should fail. In this instance, all locks acquired by the operation should be released. SOME means that the Web Feature Service should lock as many of the requested features as it can. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:simpleType name="AllSomeType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="ALL"/> <xsd:enumeration value="SOME"/> </xsd:restriction> </xsd:simpleType> <xsd:complexType name="LockType"> <xsd:annotation> <xsd:documentation> This type defines the Lock element. The Lock element defines a locking operation on feature instances of a single type. An OGC Filter is used to constrain the scope of the operation. Features to be locked can be identified individually by using their feature identifier or they can be locked by satisfying the spatial and non-spatial constraints defined in the filter. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:element ref="ogc:Filter" minOccurs="0" maxOccurs="1"/> </xsd:sequence> <xsd:attribute name="handle" type="xsd:string" use="optional"> <xsd:annotation> <xsd:documentation> The handle attribute allows a client application to assign a client-generated request identifier to a Lock action. The handle is included to facilitate error reporting. If one of a set of Lock actions failed while processing a LockFeature request, a WFS may report the handle in an exception report to localize the error. If a handle is not present then a WFS may employ some other means of localizing the error (e.g. line number). </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:attribute name="typeName" type="xsd:QName" use="required"> <xsd:annotation> <xsd:documentation> The value of the typeName attribute is the name of the feature type to be updated. The name specified must be a valid type that belongs to the feature content as defined by the GML Application Schema. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:complexType> <!-- RESPONSE --> <xsd:element name="LockFeatureResponse" type="wfs:LockFeatureResponseType"> <xsd:annotation> <xsd:documentation> The LockFeatureResponse element contains a report about the completion status of a LockFeature request. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:complexType name="LockFeatureResponseType"> <xsd:annotation> <xsd:documentation> The LockFeatureResponseType is used to define an element to contains the response to a LockFeature operation. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:element ref="wfs:LockId"> <xsd:annotation> <xsd:documentation> The LockFeatureResponse includes a LockId element that contains a lock identifier. The lock identifier can be used by a client, in subsequent operations, to operate upon the locked feature instances. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="FeaturesLocked" type="wfs:FeaturesLockedType" minOccurs="0"> <xsd:annotation> <xsd:documentation> The LockFeature or GetFeatureWithLock operations identify and attempt to lock a set of feature instances that satisfy the constraints specified in the request. In the event that the lockAction attribute (on the LockFeature or GetFeatureWithLock elements) is set to SOME, a Web Feature Service will attempt to lock as many of the feature instances from the result set as possible. The FeaturesLocked element contains list of ogc:FeatureId elements enumerating the feature instances that a WFS actually managed to lock. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="FeaturesNotLocked" type="wfs:FeaturesNotLockedType" minOccurs="0"> <xsd:annotation> <xsd:documentation> In contrast to the FeaturesLocked element, the FeaturesNotLocked element contains a list of ogc:Filter elements identifying feature instances that a WFS did not manage to lock because they were already locked by another process. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> <xsd:complexType name="FeaturesLockedType"> <xsd:sequence maxOccurs="unbounded"> <xsd:element ref="ogc:FeatureId"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="FeaturesNotLockedType"> <xsd:sequence maxOccurs="unbounded"> <xsd:element ref="ogc:FeatureId"/> </xsd:sequence> </xsd:complexType> <!-- ================================================================== --> <!-- = TRANSACTION Request and Response = --> <!-- ================================================================== --> <!-- REQUEST --> <xsd:element name="Transaction" type="wfs:TransactionType"> <xsd:annotation> <xsd:documentation> This is the root element for a Transaction request. A transaction request allows insert, update and delete operations to be performed to create, change or remove feature instances. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:complexType name="TransactionType"> <xsd:annotation> <xsd:documentation> The TransactionType defines the Transaction operation. A Transaction element contains one or more Insert, Update Delete and Native elements that allow a client application to create, modify or remove feature instances from the feature repository that a Web Feature Service controls. </xsd:documentation> </xsd:annotation> <xsd:complexContent> <xsd:extension base="wfs:BaseRequestType"> <xsd:sequence> <xsd:element ref="wfs:LockId" minOccurs="0"> <xsd:annotation> <xsd:documentation> In order for a client application to operate upon locked feature instances, the Transaction request must include the LockId element. The content of this element must be the lock identifier the client application obtained from a previous GetFeatureWithLock or LockFeature operation. If the correct lock identifier is specified the Web Feature Service knows that the client application may operate upon the locked feature instances. No LockId element needs to be specified to operate upon unlocked features. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:choice minOccurs="0" maxOccurs="unbounded"> <xsd:element ref="wfs:Insert"/> <xsd:element ref="wfs:Update"/> <xsd:element ref="wfs:Delete"/> <xsd:element ref="wfs:Native"/> </xsd:choice> </xsd:sequence> <xsd:attribute name="releaseAction" type="wfs:AllSomeType" use="optional"> <xsd:annotation> <xsd:documentation> The releaseAction attribute is used to control how a Web Feature service releases locks on feature instances after a Transaction request has been processed. Valid values are ALL or SOME. A value of ALL means that the Web Feature Service should release the locks of all feature instances locked with the specified lockId regardless or whether or not the features were actually modified. A value of SOME means that the Web Feature Service will only release the locks held on feature instances that were actually operated upon by the transaction. The lockId that the client application obtained shall remain valid and the other, unmodified, feature instances shall remain locked. If the expiry attribute was specified in the original operation that locked the feature instances, then the expiry counter will be reset to give the client application that same amount of time to post subsequent transactions against the locked features. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="LockId" type="xsd:string"> <xsd:annotation> <xsd:documentation> The LockId element contains the value of the lock identifier obtained by a client application from a previous GetFeatureWithLock or LockFeature request. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="Insert" type="wfs:InsertElementType"> <xsd:annotation> <xsd:documentation> The Insert element is used to indicate that the Web Feature Service should create a new instance of a feature type. The feature instance is specified using GML3 and one or more feature instances to be created can be contained inside the Insert element. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:complexType name="InsertElementType"> <xsd:annotation> <xsd:docu
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -