1 / 16

TDWG Life Sciences Identifiers Applicability Statement

This document provides guidelines and recommendations for the proper application of LSIDs in the biodiversity domain. It covers topics such as LSID persistence, data and metadata handling, support for the Semantic Web, and domain name requirements. The Applicability Statement aims to help organizations decide if LSIDs are the right fit for their projects and provides guidance on integrating LSIDs with existing data.

bauerk
Download Presentation

TDWG Life Sciences Identifiers Applicability Statement

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. TDWG Life Sciences Identifiers Applicability Statement Ben Richardson Review Manager, LSID Applicability Statement Western Australian Herbarium Department of Environment and Conservation urn:lsid:biocol.org:col:15701

  2. Public Review • Details at: • http://bit.ly/p7Hwp • Comments open until 26 November

  3. What is an Applicability Statement? • An advisory document rather than a specification • The “glue” that connects technical specifications • Documents how to best apply relevant technical specifications • Specifies what is to be done to conform to a specification

  4. Review Process • Prior to April 2009 • Submissions on the Applicability Statement (AS) received from 4 peer reviewers • Late April 2009 • I agreed to be Review Manager for the LSID AS • May 2009 • I requested a revision based on reviewers comments and discussion on the Technical Architecture Group mailing list • 22 October • Revision accepted for Public Review • 26 October • Public Review begins

  5. Applicability Statement in two sections • GUID Applicability Statement • LSID Applicability Statement

  6. Part 1. GUID Applicability Statement • The GUID AS provides an overview • Documents the recommendations that apply to all GUID technologies • There are 6 types of GUID technology • HTTP URI • Life Sciences Identifiers (LSID) • Digital Object Identifiers (DOI)  a type of Handle • Permanent URL (PURL)  a type of HTTP URI • Universally Unique Identifier (UUID) • Handle System

  7. GUID Recommendation Summary • One object must have only one GUID • Only assign GUIDs to objects for which you are the authority • Support the Semantic Web • HTTP GET resolution must be provided • Default metadata response format = TDWG Ontology RDF/XML

  8. Part 2. LSID Applicability Statement • Documents best application of LSIDs for biodiversity domain to • Maximise LSID permanence • Explain LSID concepts of “data” and “metadata” • Support the Semantic Web

  9. LSID Recommendation Summary — Maximising Persistence • Providers should control domain names used in LSIDs • Avoid using your organization’s domain name if it is susceptible to change • If this is problematic, apply to use TDWG’s domain • Case in point: calm.wa.gov.au  dec.wa.gov.au • Don’t parse the LSID string (except to resolve it) • E.g. urn:lsid:authority.org:name:1234:2a • “authority.org” may no longer own the data • “name” might be a person rather than a taxon • Get the metadata to be certain

  10. LSID Recommendation Summary — LSID “data” vs “metadata” • LSID “data” must never change • Non-binary encoded objects should be served as LSID “metadata” • Taxon name, concept, occurrence data is LSID “metadata” • Images, audio, video is LSID “data”

  11. LSID Recommendation Summary — Semantic Web support • Provide a HTTP proxy version of the LSID • HTTP GET must retrieve LSID “metadata” by default • LSID “metadata” must be RDF/XML • Makes biodiversity data easily accessible to Semantic Web clients that can’t resolve LSIDs

  12. What next? • With some care, LSIDs are the best fit for biodiversity data • LSID permanence is enhanced by their independence from Internet protocol • Domain Name requirements can be overcome • Semantic Web clients can be supported • However: • HTTP URIs and PURLs are simpler to implement • DOIs already exist for publications, use them if available

  13. What next? • Use the Applicability Statement • Decide whether LSIDs will work for you • If so, implement LSIDs  many projects already have • Integrate your GUIDs with everyone else’s data

  14. What next? • Complete the TDWG Ontology in RDF

  15. Acknowledgements • Reviewers • GUID Applicability Statement • Author: Kevin Richards • LSID Applicability Statement • Authors: Ricardo Pereira, Kevin Richards, Donald Hobern, Roger Hyam, Lee Belbin, and Stan Blum • Lee Belbin  review process

  16. Public Review http://bit.ly/p7Hwp Comments open until26 November Merci beaucoup

More Related