anchor.diff:  
   |DisableDynamicSchema |0..1 |Complex |Controls DescribeFeatureType
   strategy, default: regenerate schema
  +
  +|SchemaLocation |0..1 |Complex |Location of the GML application schema
  +for this GML version
   
   |DisableStreaming |0..1 |Boolean |Disables output streaming, include
   numberOfFeature information/gml:boundedBy
  
positive.code:       http://www.opengis.net/gml/3.2 http://schemas.opengis.net/gml/3.2.1/deprecatedTypes.xsd
      </AdditionalSchemaLocation>
      <DisableDynamicSchema>true</DisableDynamicSchema>
      <DisableStreaming>false</DisableStreaming>
      <GeometryLinearization>
        <Accuracy>0.1</Accuracy>
  
negative.code: to an external copy of your GML application schema files (instead of
  pointing back to the deegree WFS), use the optional attribute
  _baseURL_ that this element provides.
  * _SchemaLocation_: By default, the GML application schema
  returned in DescribeFeatureType reponses (and referenced in the
  _xsi:schemaLocation_ of query responses) will be generated dynamically
  from the internal feature type representation or, if DisableDynamicSchema
  is set to _true_, the original schema files used for configuring the feature
  store is used. If your service supports multiple GML version it may be useful
  to configure the GML application schema for each version differently.
  Use _SchemaLocation_ to configure the original GML application schema
  for this GML version. To enable this option _DisableDynamicSchema_ must be _true_.
  * _DisableStreaming_: By default, returned features are not collected
  in memory, but directly streamed from the backend (e.g. an SQL database)
  and individually encoded as GML. This enables the querying of huge
  