[Bug 429] - add additional entity types to EML

Chad Berkley berkley at nceas.ucsb.edu
Wed May 22 11:45:42 PDT 2002


Hi Peter,

see my comments inline below:

On Wed, 2002-05-22 at 10:57, bugzilla-daemon at ecoinformatics.org wrote:
> http://bugzilla.ecoinformatics.org/show_bug.cgi?id=429
>  
> ------- Additional Comments From peter.mccartney at asu.edu  2002-05-22 10:57 -------
> Ok im working on two files - spatialVector and spatialRaster (the latter will 
> merge grid and image since both esri and the iso 19115.3 seem be viewing images 
> as raster data with additional image and band descriptors). i have a couple 
> questions for Chad:
> 
> you created a dataQuality complex type in eml-entity which is used for both 
> horizonalAccuracy and verticalAccuracy. you added attributeAccuracy in eml-
> attribute but implented the content model locally rather than importing the 
> complext type. 

attributeAccuracy is a complexType, I don't understand what you mean
when you say I "implemented the content model locally rather than
importing the complex type."  I didn't import the whole FGDC type (if
that's what you mean) because a lot of the fields in that are redundant
with other EML fields.

Should we be consistent on this - ie should i just implement the 
> accuracy elements locally in each of the spatial models or should we leave the 
> complex type in eml-entity and change attribute.xsd so that in imports the same 
> structure?
> 

If you think the information in DataQuality and AttributeAccuracy are
basically the same (It kind of appears that way to me) then we might as
well merge them and use one complex type.  When I implemented this, I
just did what the notes said without really thinking too hard about it. 
When I look at it now, the two types look mostly the same.

I think we should be a consistent as possible in regargs to importing
complexTypes, as Matt has already pointed out several times.

> If we drop the complex type from eml-entity, then should we also drop the 
> spatialRepresentation complex type since the only thing it brings in is 
> spatialRepresentationType (which is really redundant with the module names)


chad
-- 
-------------------------------
Chad Berkley
National Center for Ecological
Analysis and Synthesis (NCEAS)
735 State St. Ste. 204
Santa Barbara, CA 93101
805-892-2530
berkley at nceas.ucsb.edu
-------------------------------




More information about the Eml-dev mailing list