1 / 20

EOL and DwC -Archives

EOL and DwC -Archives. Patrick Leary pleary@eol.org. Brief Background. Darwin Core ratified by TDWG October 2009 Consists of a vocabulary of terms M ultiple representations in XML, RDF Documentation includes Text Guide Text archives called Darwin Core Archives. DwC - Archive Structure.

sorley
Download Presentation

EOL and DwC -Archives

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EOL and DwC-Archives Patrick Leary pleary@eol.org

  2. Brief Background • Darwin Core ratified by TDWG October 2009 • Consists of a vocabulary of terms • Multiple representations in XML, RDF • Documentation includes Text Guide • Text archives called Darwin Core Archives

  3. DwC-Archive Structure source: http://www.gbif.org/resources/2554

  4. Meta File source: http://yuml.me/

  5. Validating • fileType has dateFormat attribute • DD-MM-YYYY, MM-DD-YYYY • fieldcannot specify data type to expect • field has vocabulary attribute • URI for a vocabulary; should be machine readable • Uncertain the format of the vocabulary • Recommendations: • dataType attribute to field (string, float, integer, date, boolean, uri) • values, optionalValues attribute; delimited choices

  6. Handling Multiple Values • Some DwC terms recommend multiple values • 10% of all terms suggest “A list (concatenated and separated)” • DwC nor Archive meta file specify delimiter • Recommendations: • multiValueDelimiterattribute to field • allowsMultiValue attribute to field

  7. Original Meta File source: http://yuml.me/

  8. If Recommendations Were Applied source: http://yuml.me/

  9. DwC-Archive Structure source: http://www.gbif.org/resources/2554

  10. EOL Partial Data Model source: http://yuml.me/

  11. Adding Structured Data source: http://yuml.me/

  12. Extending Extensions • core can have extensions • extensions do not have to be linked to core • index attribute of coreid is optional • extensions have no explicit id • extensions cannot be linked to each other

  13. Possible Workarounds • Flatten and repeat data • works for non-structured extension data • don’t want to end up with JSON values • Create multiple archives • Create multiple meta files • Modify the structure of the meta file • Create alternate meta file • Modify the meta file XSD

  14. Changing Meta File • Minimal change • Add idelement to extension / fileType • Add extensionid element to fileType • With attributes rowType • Possibly some indication of hasMany • Larger change • Unify core and extension • Change coreid accordingly

  15. Original Meta File source: http://yuml.me/

  16. Diagram of minimal change source: http://yuml.me/

  17. Diagram of larger change source: http://yuml.me/

  18. Summary of Recommendations • dataType attribute to field (string, float, integer, date, boolean, uri) • values, optionalValuesattributes to field • multiValueDelimiter attribute to field • allowsMultiValue attribute to field

  19. Open Questions • Are these recommendations worth pursuing? • How to proceed with extending extensions? • How to update Darwin Core Text Guide with respect to Darwin Core terms? • Should Darwin Core Text Guide be separated? • Should meta file schema be separated from Text Guide?

  20. Thank You Patrick Leary pleary@eol.org

More Related