Proposal for Simplifying FDO Schema and Class Names

Last week I was in Australia and had a chance to touch base with Zac Spitzer , who is the Solution Architect with Ennoble Consultancy and who was responsible for implementing the architectural design pattern that I blogged about a few weeks ago.

Zac is a MapGuide/FDO developer, and one of the things we talked about is his six point proposal to simplify schema and class naming in FDO.  In essence what Zac is proposing is to move FDO in the direction of making it more provider independent.  It would make it easier to use FDO, and would also make it easier to migrate applications from one provider to another, for example, from Oracle to MySQL, or from SHP to Oracle.

According to Zac, currently FDO reports

    OSGEO.SHP reports Default:shpfilename
    OSGEO.Gdal reports default:default
    KingOracle reports KingOra:ZAC~BUILDINGOUTLINES~SHPGEOM
    OSGEO.OGR reports OGRSchema:BUILDING
    MySql reports Fdoreports:aquifer_property

With Zac's proposal FDO would report

    OSGEO.SHP reports filename
    OSGEO.Gdal reports filename
    KingOracle reports schema:tablename or if connected as "schema" then just tablename
    OSGEO.OGR reports filename
    MySql reports schema:tablename or if connected as "schema" then just tablename
    SDF still reports what ever you like as a schema name

Thoughts ?