eml-entity

[Chad Berkley]

Can someone clarify item 10 in bug 484?  I don't want to attempt a fix
until I have more information.  Namely, how the tree structure described
will denote a dataTable with 2 columns with a bunch of codes in it.  Why
not just make it:
enumeratedDomain
    |- codeList
    |    |- EntityId
    |    |- codeAttributeId
    |    |- codeDefinitionAttributeId

basically a pointer to the entity where the code list is and two
pointers to the code attribute and the codeDef attribute.  this could
also just be a pointer to an entire entity block in the merged eml
document...so if you have
<entity id="1">
  <entName>Lookup table 1</entName>
  <attribute id="2">
    <attName>codecolumn</attName>
  </attribute>
  <attribute id="3">
    <attName>codedefcolumn</attName>
  </attribute>
</entity>

the enumeratedDomain could just be 
  <enumeratedDomain>
    <codelist>
      <entityId>1</entityId>
    </codelist>
  </enumeratedDomain>

the way I described above it would be
  <enumeratedDomain>
    <codelist>
      <entityId>1</entityId>
      <codeAttributeId>2</codeAttributeId>
      <codeDefinitionAttributeId>3</codeDefinitionAttributeId>
    </codelist>
  </enumeratedDomain>              
  
What do you think?

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
-------------------------------