[mapguide-trac] #1574: Rewrite MaestroAPI schema classes

[MapGuide Open Source]

#1574: Rewrite MaestroAPI schema classes
-----------------------+----------------------------------------------------
   Reporter:  jng      |       Owner:  jng        
       Type:  task     |      Status:  new        
   Priority:  high     |   Milestone:  Maestro-3.0
  Component:  Maestro  |     Version:             
   Severity:  major    |    Keywords:             
External_id:           |  
-----------------------+----------------------------------------------------
Description changed by jng:

Old description:

> The current FDO schema classes in the MaestroAPI
> (FeatureSourceDescription, ClassDefinition, etc), do not conceptually
> line up with the data they are trying to represent (FDO schema elements).
> This makes it difficult for those already familiar with FDO, and makes
> integration with other things like Configuration Documents (#1495) or
> serializing/deserializing to and from XML equally difficult.
>
> They should be rewritten so that they better line up with
> MgClassDefinition/FdoClassDefinition APIs

New description:

 The current FDO schema classes in the MaestroAPI
 (FeatureSourceDescription, ClassDefinition, etc), do not conceptually line
 up with the data they are trying to represent (FDO schema elements). This
 makes it difficult for those already familiar with FDO, and makes
 integration with other things like Configuration Documents (#1495) or
 serializing/deserializing to and from XML equally difficult.

 They should be rewritten so that they better line up with
 MgClassDefinition/FdoClassDefinition APIs and to offer a similar developer
 experience for those who are already familiar with the aforementioned APIs

--

-- 
Ticket URL: <http://trac.osgeo.org/mapguide/ticket/1574#comment:2>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals