Changes between Version 5 and Version 6 of FDORfc12

Timestamp:

11/30/07 09:38:41 (17 years ago)

Author:

gregboone

Comment:

--

FDORfc12

@@ -252 +252 @@
     * Add support for creating and modifying schema with existing schema. This could be done in the second phase. This is new work that existing GenericRdbms based providers do not support yet, but this would be a good opportunity to add this. Users would find this very useful.
 
-
+=== Implementation Plan ===
+
+Here is a starting list of high level changes that are need to do to produce an OSGeo SQL Server 2008 provider.
+
+    * Develop a preview to be available March, with a more mature version for a June release to coincide with Microsoft’s formal release.
+
+    * Use the new spatial data type and spatial indexing scheme. It supports OGC simple feature spec geometry.
+
+    * There is no coordinate system library for non-geodetic coordinate system definitions, but the spatial data type supports saving an SRID. SQL Server doesn’t use the SRID itself, just saves and returns it. This is the same as what OSGeo MySQL Provider implements.
+
+    * Map FDO geometry to the new SQL Server spatial data type. If the FDO geometry has spatial context that includes a geodetic coordinate system, then the FDO property will map to a geography type. Otherwise, the property will map to a geometry type. Also, the providers physical schema overrides should allow the user to specify one or the other type. The Geography type may require an SRID to be specified. (TBD) 
+
+    * Create a spatial index using the new spatial index type. Initially use the planar geometry type, not the geography type. The geography type is not fully implemented yet in the SQLServer CTP, but the goal is to support it as well. The geography type would be used for a 3d whole-earth model as used by Virtual Earth. 
+
+    * Map spatial queries to the new spatial query functions. These are based on OGC simple feature spec as well so should be straight forward to map.
+
+    * The spatial data type has functions to set/get the geometry via OGC WKB and WKT formats. Z and M are handled with separate functions.
+
+    * Modifications to Select, Insert, Update of geometry using the new functions. 
+
+    * Support existing schema. Include reverse engineering of existing schema, which previous releases of SQL Server Providers did not implement completely.
+
+    * Support Apply Schema to create FDO-enabled schema as currently done.
+
+    * Support Apply Schema to existing schema in data stores. This is new functionality and should be done in the second phase.
+
+    * Make sure the new provider is compatible with FDO 3.2.3 and 3.3.0. 
+