Changes between Version 2 and Version 3 of MapGuideRfc106


Ignore:
Timestamp:
07/25/10 19:25:13 (14 years ago)
Author:
liuar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc106

    v2 v3  
    3232It's described in WFS 1.1.0 specification section 8.1 that the only mandatory output in response to a !DescribeFeatureType request is a GML3 application schema defined using XML Schema.  Because GML2 application schema is kept for backward compatibility, it is necessary for MapGuide to enhance the !HttpWfsGetFeatureType to handle different GML formats.
    3333[[BR]][[BR]]
    34 
    35 '''2) Enhance the !GetFeature operation to support mutiple GML formats'''[[BR]]
    36 [[BR]]
    37 In WFS 1.1.0 specification section 9.2:  ''The optional output format attribute specifies the format of the response to a !GetFeature request. The default value is text/xml;subtype=gml/3.1.1 indicating that a vald GML3 document, that validate s against a valid GML3 application schema, must be generated.  For backward compatibility, the value GML2 may be specified indicating that a valid GML2 document, that validates against a valid GML2 application schema, must be generated.'' So,it is necessary for MapGuide to enhance the !HttpWfsGetFeature to handle different GML formats.
    38 
    39 
    40 == Implications ==
    4134
    4235A new !DescribeWfsFeature API should be added to handle the output GML format
     
    7770
    7871}}}
     72
     73'''2) Enhance the !GetFeature operation to support mutiple GML formats'''[[BR]]
     74[[BR]]
     75In WFS 1.1.0 specification section 9.2:  ''The optional output format attribute specifies the format of the response to a !GetFeature request. The default value is text/xml;subtype=gml/3.1.1 indicating that a vald GML3 document, that validate s against a valid GML3 application schema, must be generated.  For backward compatibility, the value GML2 may be specified indicating that a valid GML2 document, that validates against a valid GML2 application schema, must be generated.'' So,it is necessary for MapGuide to enhance the !HttpWfsGetFeature to handle different GML formats.
     76[[BR]][[BR]]
    7977
    8078A new !DescribeWfsFeature API should be added to handle the output GML format
     
    125123
    126124
     125
     126== Implications ==
     127
    127128== Test Plan ==
    128129