eml-spatialReference
Peter McCartney
peter.mccartney at asu.edu
Fri May 31 15:42:38 PDT 2002
ok...ill have to do it later tonight. ive got a review thats due NOW!.
Regarding attribute. We had a meeting with robin, corinna and amy. Our
concerns followed some points that ive made before.
1) They liked the consistency of haveing a choice between content and
references. if we dont use the content elements in AttributeType and
AttributeListType then you wind up not being able to enforce the proper
assignment of id's (which we normally expect to find in <content>)
2) There doesnt seem to be any reason for providing a choice between single
and attribute list. if you import only attribute list into entityBase, then
you can ensure that all entities will have one and only one attribute list
containing one or more attributes. We could envision cases where you would
want to restrict to either a list or a single attribute, but we couldnt
think of any cases where allowing a choice would gain you anything.
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: Friday, May 31, 2002 3:18 PM
To: Peter McCartney
Cc: Eml-Dev (E-mail)
Subject: eml-spatialReference
Hi Peter,
Could you please add the top level type ("SpatialReference") with the
references and content choice to spatialReference? I'm having problems
following all of the element references in that module. Since you know
what it is for, I think you can evaluate how to add the packaging better
than I.
thanks,
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
-------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20020531/71874cdc/attachment.htm
More information about the Eml-dev
mailing list