[eml-dev] EML 2.0.2 changes to text leaf nodes

[Callie Bowdish]

Hi All,

I'm not sure I follow completely the eml changes thread but I think we 
need to keep in mind the possible usage of the eml to crosswalk to other 
xml schemas. I think by keeping the eml elements as close to the schemas 
that we have borrowed from we will be able to cross walk or data from 
one schema to another more easily. I also liked the earlier mention of 
being able to include MathXML which would be helpful in the future

Compatibility: EML adopts much of it's syntax from the other metadata 
standards that have evolved from the expertise of groups in other 
disciplines. Whenever possible, EML adopted entire trees of information 
in order to facilitate conversion of EML documents into other metadata 
languages. EML was designed with with the following standards in mind: 
Dublin Core Metadata Initiative, the Content Standard for Digital 
Geospatial Metadata (CSDGM from the US geological Survey's Federal 
Geographic Data Committee (FGDC)), the Biological Profile of the CSDGM 
(from the National Biological Information Infrastructure), the 
International Standards Organization's Geographic Information Standard 
(ISO 19115), the ISO 8601 Date and Time Standard, the OpenGIS 
Consortiums's Geography Markup Language (GML), the Scientific, 
Technical, and Medical Markup Language (STMML), and the Extensible 
Scientific Interchange Language (XSIL).
(http://knb.ecoinformatics.org/software/eml/eml-2.0.1/index.html#moduleOverview) 


Callie



Christopher Jones wrote:
> Margaret,
>
> About searching txt:TextType nodes:
>
> On Mar 20, 2008, at Mar20---6:15:43 PM, Margaret O'Brien wrote:
>   
>> First, one comment on Chris's original question about drawbacks to  
>> mixed content instead of xs:string: I recall one possible drawback  
>> in searches. If someone searches on the string "uptake rates for  
>> Alnus tenuifolia" the search will fail if <title> is text instead of  
>> a string because of the embedded tags. One solution is an optional  
>> <complexTitle> which is txt:TextType, in addition to <title>. The  
>> search on the simple <title> returns the correct doc, and the title  
>> template needs to look for the complexTitle first. Apologies for not  
>> remembering who to credit for this - I think it was a verbal exchange.
>>     
>
>
> To me, this seems like a database implementation detail, rather than a  
> schema issue.  For instance, metacat models the DOM, and so places  
> child nodes as unique records from their parents.  Other XML databases  
> do this differently.  I think it is the onus of the database to  
> correctly interpret data typing, and search appropriately (or at least  
> create indices based on data types so that they are searched correctly).
>
> Cheers,
> Chris
> _________________________________________________________________
> christopher jones       cjones at msi.ucsb.edu      (805) 680-5946
> marine science institute  university of california, santa barbara
> _________________________________________________________________
>
>
>
>
> _______________________________________________
> Eml-dev mailing list
> Eml-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/eml-dev
>
>   

-- 
Callie Bowdish
Metadata Coordinator
National Center for Ecological Analysis and Synthesis
735 State St., Suite 300
Santa Barbara, CA  93101-5504
phone: (805) 892-2160,  fax: (805) 892-2160
email:bowdish at nceas.ucsb.edu
knb-help at nceas.ucsb.edu  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20080321/1f877466/attachment.htm