Enhance Support for WFS Application Schema

[sdlime]

By updating mapwfs.c/mapgml.c code to:

  - support layer name spaces using layer metadata (falling back to map level 
values if not present)

    "wfs_namespace_uri"
    "wfs_namespace_prefix"
    "wfs_application_schema"

  - allow users to refer to an existing application schema via:

    "wfs_application_schema"

The latter would result in code in the schema returned by a getFeatureInfo 
request like:

  <include schemaLocation="layer_application_schema.xsd" /> </schema>

Steve

[sdlime]

Tom: Will you have some testing time available in the next week or two to do 
some testing with this? Let me know.

Steve

[tomkralidis]

sure, contact me offline email so we can discuss.

[tomkralidis]

1./ I tried this against latest CVS and see no difference when I do a
GetFeature.  Has this been committed?

2./ Note that this would have to be supported for DescribeFeatureType requests
as well, i.e.:

a./ if DescribeFeatureType is called, use layer level wfs_namespace_uri and
wfs_namespace_prefix is they exist, else fall to map level wfs_namespace_uri and
wfs_namespace_prefix

b./ if DescribeFeatureType is called, if wfs_application_schema exists, then
redirect to this URL (maybe via HTTP Location header), process else as per usual
(checking point a above too).

[sdlime]

Tom, do you recall if we ever went anywhere with this?

Steve

[tomkralidis]

Testing this against svn trunk, GetFeature requests behave correctly (i.e. if layer namespace metadata is defined, then override).

DescribeFeatureType is not fully implemented per comment:4. If layer namespace metadata is defined, empty xs:complexType's are outputted, instead of the definition of attributes. Also, wfs_application_schema is not implemented.

[sdlime]

Let's target 5.4 to clean it up. I do think it's a good idea.

Steve