Jody Garnett wrote:
>> It seems to me that in GML an enclosing type has been introduced as  
>> an artifact to ensure that every complex property contains an  
>> element that gives its type information. To me this seems to be an  
>> encoding artifact that should be created at encoding time, not  
>> stored in our GeoAPI representation of the data.
> That does not seem too strange.  In this case I am guessing that  
> GeologicUnit is a bit dynamic in nature

This pattern is used for *every* complex-content property in GML. It is 
required by the encoding rule. It is not specific to GeologicUnit or to 
GeoSciML.

The XSD looks like this:
OuterType <>--- InnerPropertyType <>--- InnerType

The information model looks like this:
Outer <>-- Inner

We use GeoAPI to represent the former. But is this right?

Take, for example, gml:AbstractFeatureType, where three related GeoAPI 
objects represent a feature and its geometry:

gml:AbstractFeatureType
     <>--- gml:LocationPropertyType
               <>--- gml:AbstractGeometryType

The information we are trying to convey has only two GeoAPI objects:

Feature <>--- Geometry

I am not convinced that the extra layer of indirection we currently use 
is the correct use of GeoAPI. In my view, GeoAPI should represent the 
information model and the encoder should convert to and from XML. It 
seems to me that the GML encoding has influenced our use of GeoAPI, and 
we no longer have a separation of concerns.

-- 
Ben Caradoc-Davies <[email protected]>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to