spatial and other entity types
Peter McCartney
peter.mccartney at asu.edu
Tue Apr 16 10:29:15 PDT 2002
I'm wiling to go through and clean up the documentation once we decide on
how these are to be implemented - what's in there now was cut and and pasted
from the ISO pdf file.
Spref is missing from chad's file, but i assume thats because he intended to
link it with packaging? we also defined some horizonal and vertical quality
elements that correspond to FGDC quality descriptors that got dropped
Image also makes use of the rasterSpatialRepresentation elements as well as
imageSpatialRepresentation.
I realized after seeing chads file that these were older schemas where I
hadnt gone back through and added the suffix "Type" to allthe complex types
to prevent them from having the same names as the elements that use them.
Looks like chad changed the elementnames instead.
If i read this file right, you have now changed to using one instance of
eml-entity per entity, and have dropped the container element <eml-entity>?
So what we have is a single schema with several alternate roots depending on
which type of entity we do? So far so good. But wouldnt it be cleaner to do
like we do with the resource-level schemas and just make separate schema
files for these types so that they could be edited (or new ones defined)
without needing to edit a common entity file?
Along that line, vector, grid, and image are really three different entity
types, even though they do share certain modules such as spref. There is no
real gain in lumping them together into a "spatial entity" class - each
requires totally different approaches to handling them.
So i guess my preference would be to start with the three files as they are
and change them only to extent the entity base from the agreed upon version
rather than ours.
Peter McCartney (peter.mccartney at asu.edu)
Center for Environmental Studies
Arizona State University
480-965-6791
-----Original Message-----
From: chad berkley [mailto:berkley at nceas.ucsb.edu]
Sent: Monday, April 15, 2002 4:55 PM
To: Matt Jones
Cc: eml-dev at ecoinformatics.org
Subject: Re: spatial and other entity types
Hi Matt, Peter and others,
The eml spatial entity information was adapted entirely from the ASU
spatial entity schema. You can check it out in eml-entity.xsd. The
type name is spatial-entity. It extends entityBase and adds all of the
information that the ASU files included for spatial references. The
documentation is kind of sparse because I took it straight from the ASU
files. I am not an expert in that area so I only added additional
comments when I really knew what I was talking about. The ASU gang may
want to look over my documentation and feel free to edit/add/delete
where appropriate. Also, please let me know if you find any problems
with the way that I translated the ASU schema.
thanks,
chad
Matt Jones wrote:
> Peter and Chad,
>
> Chad put together an EML module for the spatial entity types based on
> Peter's earlier work. Are you both happy with the state of the
> current eml-entity module in this regard? In particular, can you
> comment on any further things that need to be incorporated in order to
> resolve bug 429?
>
> http://bugzilla.ecoinformatics.org/show_bug.cgi?id=429
>
> Thanks,
>
> Matt
--
-------------------------------
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
-------------------------------
_______________________________________________
eml-dev mailing list
eml-dev at ecoinformatics.org
http://www.ecoinformatics.org/mailman/listinfo/eml-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20020416/ba52bdf1/attachment.htm
More information about the Eml-dev
mailing list