Changes between Version 12 and Version 13 of GeoManual


Ignore:
Timestamp:
22/04/08 11:25:52 (11 years ago)
Author:
ashaon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeoManual

    v12 v13  
    229229 
    230230For instance, this information is 
    231       1.a reference to a source FeatureSource:  
     231      * a reference to a source FeatureSource:  
    232232         
    233233 
     
    243243}}} 
    244244 
    245       2.a reference to an output FeatureType (the "community" schema).  This essentially refers to the root element of the output XML document:  
     245      * a reference to an output FeatureType (the "community" schema).  This essentially refers to the root element of the output XML document:  
    246246         
    247247{{{ 
    248248<targetType>csml:PointSeriesFeature</targetType> 
    249249}}} 
    250       3.database fields by which the retrieved result sets are to be grouped.  This is only necessary if there exists one-to-many relationships between  
    251         the source and target schemas, i.e. if the output schema contains attribute(s) that has multiplicity greater than 1.  In such a case, it is   
    252         required to inform ComplexDataStore the names of the "grouping" attributes, using the GroupByAttribute elements, which come below the  
    253         targetType element.  Below is an example of this: 
     250      * database fields by which the retrieved result sets are to be grouped.  This is only necessary if there exist one-to-many relationships between the source and target schemas, i.e. if the output schema contains attribute(s) that has multiplicity greater than 1.  In such a case, it is required to inform ComplexDataStore the names of the "grouping" attributes, using the GroupByAttribute elements, which come below the targetType element.  Below is an example of this: 
    254251         
    255252{{{ 
     
    258255        </groupBy> 
    259256}}} 
    260       4.the mappings between FeatureSource and FeatureType. The mappings consist of three sets of mappings, one for the identifyable attributes (the  
     257      * the mappings between FeatureSource and FeatureType. The mappings consist of three sets of mappings, one for the identifyable attributes (the  
    261258        ones with gml:id), such as instances of the FeatureType itself and any direct or nested property that is also identifyable. The second is for   
    262259        mapping to any other attribute of an element in the target schema.  The final type of mapping is for the target attribute values. It should be