wfsv.xsd

电子地图服务器,搭建自己的地图服务

        transaction command that can be used to alter features at version m to turn them into
        version n
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetDiffType">
    <xsd:annotation>
      <xsd:documentation>
        A GetDiff element contains one or more DifferenceQuery elements that describe a difference
        query operation on one feature type. In response to a GetDiff request, a Versioning Web
        Feature Service must be able to generate a Transaction command that can be used to alter
        features at fromFeatureVersion and alter them into features at toFeatureVersion
      </xsd:documentation>
    </xsd:annotation>
    <xsd:complexContent>
      <xsd:extension base="wfs:BaseRequestType">
        <xsd:sequence>
          <xsd:element ref="wfsv:DifferenceQuery" maxOccurs="unbounded" />
        </xsd:sequence>
        <xsd:attribute name="outputFormat" type="xsd:string" use="optional"
          default="text/xml; subtype=wfs-transaction/1.1.0">
          <xsd:annotation>
            <xsd:documentation>
              The outputFormat attribute is used to specify the output format that the Versioning
              Web Feature Service should generate in response to a GetDiff element. The default
              value of 'application/xml; subtype=wfsv-transaction/1.1.0' indicates that the output
              is an XML document that conforms to the WFS 1.1.0 Transaction definition. For the
              purposes of experimentation, vendor extension, or even extensions that serve a
              specific community of interest, other acceptable output format values may be used to
              specify other formats as long as those values are advertised in the capabilities
              document.
            </xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <!-- ================================================================== -->
  <!-- =   Extended Transaction elements: update                        = -->
  <!-- ================================================================== -->
  <xsd:element name="VersionedUpdate" type="wfsv:VersionedUpdateElementType"
    substitutionGroup="wfs:Update" />
  <xsd:complexType name="VersionedUpdateElementType">
    <xsd:complexContent>
      <xsd:extension base="wfs:UpdateElementType">
        <xsd:attribute name="featureVersion" type="xsd:string" use="required">
          <xsd:annotation>
            <xsd:documentation>
              The syntax and semantics is the same as featureVersion in Query. If specified, update
              will check that every updated feature is still at the specified version before
              executing, and will fail if a change occurred on the server in the meantime.
            </xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <!-- ================================================================== -->
  <!-- =   Extended Transaction elements: delete                        = -->
  <!-- ================================================================== -->
  <xsd:element name="VersionedDelete" type="wfsv:VersionedDeleteElementType"
    substitutionGroup="wfs:Delete" />
  <xsd:complexType name="VersionedDeleteElementType">
    <xsd:complexContent>
      <xsd:extension base="wfs:DeleteElementType">
        <xsd:attribute name="featureVersion" type="xsd:string" use="required">
          <xsd:annotation>
            <xsd:documentation>
              See VersionedUpdateElementType featureVersion attribute.
            </xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <!-- ================================================================== -->
  <!-- =   Extended Transaction elements: rollback                      = -->
  <!-- ================================================================== -->
  <xsd:element name="Rollback" type="wfsv:RollbackType" substitutionGroup="wfs:Native">
    <xsd:annotation>
      <xsd:documentation>
        Rolls back the changes occurred on all matched features between fromFeatureVersion and
        featureVersion
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="RollbackType">
    <xsd:complexContent>
      <xsd:extension base="wfs:NativeType">
        <xsd:sequence>
          <xsd:element ref="ogc:Filter" minOccurs="0" maxOccurs="1">
            <xsd:annotation>
              <xsd:documentation>
                The Filter element is used to define spatial and/or non-spatial constraints on
                query. Spatial constrains use GML3 to specify the constraining geometry. A full
                description of the Filter element can be found in the Filter Encoding Implementation
                Specification.
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
        <xsd:attribute name="typeName" type="xsd:QName" use="required">
          <xsd:annotation>
            <xsd:documentation>
              The typeName attribute is a single feature type name that indicates which type of
              feature instances should be included in the reponse set. The names must be a valid
              type that belong to this query's feature content as defined by the GML Application
              Schema.
            </xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="toFeatureVersion" type="xsd:string" default="FIRST">
          <xsd:annotation>
            <xsd:documentation>
              Same as featureVersion in QueryType. Rollback will restore the "toFeatureVersion" 
              feature state, removing all changes occurred between "toFeatureVersion" and current
            </xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="user" type="xsd:string" use="optional" default="">
          <xsd:annotation>
            <xsd:documentation>
              User id to be used in addition to the filter in order to isolate the features to be
              rolled back. Only the features modified by the specified user between
              fromFeatureVersion and the current version will be subjected to roll back.
            </xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <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 an Insert action. The handle is included to facilitate error reporting.
              If a Rollback action in a Transaction request fails, then a Versioning WFS may include
              the handle in an exception report to localize the error. If no handle is included of
              the offending Rollback element then a WFS may employee other means of localizing the
              error (e.g. line number).
            </xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:schema>