Changes between Version 8 and Version 9 of FDORfc51
- Timestamp:
- Jul 28, 2010, 1:36:40 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FDORfc51
v8 v9 47 47 WFS 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. 48 48 49 2 Handle GML 349 2. Handle GML 3 50 50 51 51 WFS1.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: 52 52 53 GML 3 to FDO[[BR]]53 GML 3 to FDO[[BR]] 54 54 55 • GML 3 schema to FDO schema55 • GML 3 schema to FDO schema 56 56 57 • 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)57 • 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) 58 58 59 FDO to GML 3[[BR]]59 FDO to GML 3[[BR]] 60 60 61 • FDO schema to GML 3 schema61 • FDO schema to GML 3 schema 62 62 63 • FDO feature to GML 3 feature63 • FDO feature to GML 3 feature 64 64 65 65 Note: Those transform functions are implemented in the FDO component. 66 66 67 3. 67 3. Handle different version request 68 68 69 69 Currently, 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.