attribute

Chad Berkley berkley at nceas.ucsb.edu
Mon Jun 3 11:07:05 PDT 2002


You're right.  that is the only way to keep a reference from being
referenced.  Do you think this is the content model that we want?  It's
kind of ugly, but it makes sense to me.  I don't really like the fact
that we are just assuming that the content tag under attributes is an
attributeList without being explicit and calling it an attributeList. 
One way around that is to call attributes attributeList instead, but
there is no way to regulate what the importing element is called.  Maybe
the complexType should be AttributeList instead of Attribute then it
would be more natural to call the importing element attributeList.


On Mon, 2002-06-03 at 10:04, Peter McCartney wrote:
> the content tag is wierd no matter what - attribute makes it just that much
> worse because we want to reference both lists and singles. To be completely
> consistent, it would have to look even more wierd: 
> 
> <dataTable id=table.1>
>   <attributes>
>     <content id=attributeList.1>
>       <attribute>
> 		<content id=attribute.1/>
>       <attribute>
> 		<references>attribute.4</references>
>       <attribute>
> 		<content id=attribute.2/>
>     </content>
>   </attributes>
> </dataTable>
> 
> This is the only model that would let us set id's to be required while not
> allowing them when referencing.
> 
> 
> 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, June 03, 2002 9:56 AM
> To: Eml-Dev (E-mail)
> Subject: attribute
> 
> 
> I made the changes to attribute and checked them in to CVS.  take a
> look.  I'm not sure if it is exactly how we want it.  Now would have an
> instance document that looks like:
> <dataTable id=table.1>
>   <attributes>
>     <content id=attributeList.1>
>       <attribute id=attribute.1/>
>       <attribute id=attribute.2/>
>       <attribute id=attribute.3/>
>     </content>
>   </attributes>
> </dataTable>
> 
> is that what we want?  I guess the content tag takes the place of a
> named attributeList tag.  It's kind of weird though.  
> 
> comments?
> 
> chad
> -- 
> -----------------------
> Chad Berkley
> National Center for 
> Ecological Analysis 
> and Synthesis (NCEAS)
> berkley at nceas.ucsb.edu
> -----------------------
> 
> _______________________________________________
> eml-dev mailing list
> eml-dev at ecoinformatics.org
> http://www.ecoinformatics.org/mailman/listinfo/eml-dev
-- 
-----------------------
Chad Berkley
National Center for 
Ecological Analysis 
and Synthesis (NCEAS)
berkley at nceas.ucsb.edu
-----------------------




More information about the Eml-dev mailing list