Changes between Version 2 and Version 3 of FDORfc51


Ignore:
Timestamp:
Jul 27, 2010, 11:58:19 PM (14 years ago)
Author:
leodai
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • FDORfc51

    v2 v3  
    3434WFS spec changes a lot while upgrading from 1.0.0 to 1.1.0. For example: The service schema’s structure changed, and it now uses GML 3 instead of GML 2. Accordingly, we need to enhance the provider in the following areas in order to make sure it can consume both versions:
    3535
    36 1.      Support WFS 1.1.0 capability schema
     361. Support WFS 1.1.0 capability schema
     37
    3738The WFS spec defines new capability schema while upgrading from 1.0.0 to 1.1.0, so we must enhance the parsing process in WFS FDO provider also to support both versions.
    3839The following diagram shows capability schema in 1.0.0.
    … …  
    4142WFS 1.1.0 spec has also defined some new operations, like GetGMLObject, LockFeature… We are not going to support these commands yet in this updates. In this enhancement, we will focus on the elements and operations which already existed in 1.0.0 version but changed in 1.1.0 version.
    4243
    43 2.      Handle GML 3
     442 Handle GML 3
     45
    4446WFS1.1.0 uses GML 3 instead of GML 2 as default format for DescribeFeatureType and GetFeature request. Currently FDO can only handle GML 2 correctly and have some problem with GML 3, we need to enhance it to support both versions well. This includes two aspects:
    45        GML 3 to FDO
    46 •       GML 3 schema to FDO schema
    47 •       GML 3 feature to FDO feature (FDO only has a reader API, used by the WFS provider, which exposes GML features as FDO features. This API should be updated to handle GML 3)
    48        FDO to GML 3
    49 •       FDO schema to GML 3 schema
    50 •       FDO feature to GML 3 feature
     47GML 3 to FDO
     48  •     GML 3 schema to FDO schema
     49  •     GML 3 feature to FDO feature (FDO only has a reader API, used by the WFS provider, which exposes GML features as FDO features. This API should be updated to handle GML 3)
     50FDO to GML 3
     51  •     FDO schema to GML 3 schema
     52  •     FDO feature to GML 3 feature
    5153Note: Those transform functions are implemented in the FDO component.
    5254
    53553.      Handle different version request
     56
    5457Currently, the WFS FDO provider uses version 1.0.0 (hard-coded) while sending the request to server. So first, we need to accept version information while open connection, and also set the correct version in the request parameters. Similar with WMS FDO provider, the design solution is to store the version information in the Feature server connecting property. And parse it in the provider, a default version will be provided if user doesn’t set.
    5558