Changes between Version 10 and Version 11 of FdoEnhancedSchemaNameSupport


Ignore:
Timestamp:
10/19/07 09:49:23 (17 years ago)
Author:
gregboone
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FdoEnhancedSchemaNameSupport

    v10 v11  
    5353When no !FdoXmlFlags are specified, the FDO schema name is translated by prepending a default osgeo-defined schema prefix (http://fdo.osgeo.org/schemas/feature/) to the schema name and escaping any characters not allowed in a URI. For example, the FDO Schema "Water Service" becomes:
    5454
    55 http://fdo.osgeo.org.schemas/feature/Water-x20-Service
     55        http://fdo.osgeo.org.schemas/feature/Water-x20-Service
    5656
    5757===== GML to FDO =====
     
    5959When no !FdoXmlFlags are specified, GML schema names are translated by dropping any http:// prefix and escaping '.' and ':' to '-dot-' and '-colon-' respectively. This means that the example schema name from the Overview:
    6060
    61 http://www.mycity.on.ca/departments/transportation/Roads
     61        http://www.mycity.on.ca/departments/transportation/Roads
    6262
    6363becomes:
     
    7373simply becomes:
    7474
    75         Roads.
     75        Roads
    7676
    7777This is done to preserve round-trip fidelity.
     
    287287
    288288        • This is the most elegant solution but it lacks the simplicity of the Schema Name Attributes option:
    289                 o it requires the use of Schema Overrides, which are not popular with application developers.
     289                o it requires the use of Schema Overrides, which are not popular with application developers.[[br]]
    290290                o the persistence problems are worse. Instead of needing to persist a name, a whole set of classes or an XML fragment must be persisted.
    291291
     
    382382
    383383        • This option is viable but not recommended. The main reasons are:
    384                 o it departs from the !OpenGeospatial schema model
    385                 o it adds complication to the FDO Feature Schema model
    386                 o the implementation effort is a bit high. 
     384                o it departs from the !OpenGeospatial schema model[[br]]
     385                o it adds complication to the FDO Feature Schema model[[br]]
     386                o the implementation effort is a bit high.[[br]]
    387387
    388388
     
    392392
    393393{{{
    394         class FdoFeatureSchema
    395         {
    396                 void SetNamespace( FdoString* namespace );
    397                 FdoString* GetNamespace();
    398         }
     394class FdoFeatureSchema
     395{
     396        void SetNamespace( FdoString* namespace );
     397        FdoString* GetNamespace();
     398}
    399399}}}
    400400