<xsd:complexType name="DescribeFeatureTypeType">
<xsd:annotation>
<xsd:documentation>
The DescribeFeatureType operation allows a client application
to request that a Web Feature Service describe one or more
feature types. A Web Feature Service must be able to generate
feature descriptions as valid GML3 application schemas.
The schemas generated by the DescribeFeatureType operation can
be used by a client application to validate the output.
Feature instances within the WFS interface must be specified
using GML3. The schema of feature instances specified within
the WFS interface must validate against the feature schemas
generated by the DescribeFeatureType request.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="wfs:BaseRequestType">
<xsd:sequence>
<xsd:element name="TypeName" type="xsd:QName" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
The TypeName element is used to enumerate the
feature types to be described. If no TypeName
elements are specified then all features should
be described. The name must be a valid type
that belongs to the feature content as defined
by the GML Application Schema.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="outputFormat" type="xsd:string" use="optional" default="text/xml; subtype=gml/3.1.1">
<xsd:annotation>
<xsd:documentation>
The outputFormat attribute is used to specify what schema
description language should be used to describe features.
The default value of 'text/xml; subtype=3.1.1' means that
the WFS must generate a GML3 application schema that can
be used to validate the GML3 output of a GetFeature
request or feature instances specified in Transaction
operations.
For the purposes of experimentation, vendor extension,
or even extensions that serve a specific community of
interest, other acceptable output format values may be
advertised by a WFS service in the capabilities document.
The meaning of such values in not defined in the WFS
specification. The only proviso is such cases is that
clients may safely ignore outputFormat values that do
not recognize.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
|
XSD Schema Diagram:
