751 lines
29 KiB
Plaintext
751 lines
29 KiB
Plaintext
|
head 1.26;
|
||
|
|
access;
|
||
|
|
symbols;
|
||
|
|
locks; strict;
|
||
|
|
comment @# @;
|
||
|
|
|
||
|
|
|
||
|
|
1.26
|
||
|
|
date 2006.02.16.19.54.19; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.25;
|
||
|
|
|
||
|
|
1.25
|
||
|
|
date 2006.02.14.11.46.15; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.24;
|
||
|
|
|
||
|
|
1.24
|
||
|
|
date 2006.02.14.11.45.29; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.23;
|
||
|
|
|
||
|
|
1.23
|
||
|
|
date 2006.02.13.21.02.44; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.22;
|
||
|
|
|
||
|
|
1.22
|
||
|
|
date 2006.02.13.20.59.28; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.21;
|
||
|
|
|
||
|
|
1.21
|
||
|
|
date 2006.02.13.19.35.52; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.20;
|
||
|
|
|
||
|
|
1.20
|
||
|
|
date 2006.02.13.19.07.33; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.19;
|
||
|
|
|
||
|
|
1.19
|
||
|
|
date 2006.02.13.12.01.31; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.18;
|
||
|
|
|
||
|
|
1.18
|
||
|
|
date 2006.02.13.10.08.21; author DonaldHobern; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.17;
|
||
|
|
|
||
|
|
1.17
|
||
|
|
date 2006.02.13.10.07.58; author DonaldHobern; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.16;
|
||
|
|
|
||
|
|
1.16
|
||
|
|
date 2006.02.13.02.23.46; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.15;
|
||
|
|
|
||
|
|
1.15
|
||
|
|
date 2006.02.13.02.23.24; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.14;
|
||
|
|
|
||
|
|
1.14
|
||
|
|
date 2006.02.13.02.17.32; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.13;
|
||
|
|
|
||
|
|
1.13
|
||
|
|
date 2006.02.11.13.19.07; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.12;
|
||
|
|
|
||
|
|
1.12
|
||
|
|
date 2006.02.11.13.17.35; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.11;
|
||
|
|
|
||
|
|
1.11
|
||
|
|
date 2006.02.10.20.37.57; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.10;
|
||
|
|
|
||
|
|
1.10
|
||
|
|
date 2006.02.10.18.22.36; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.9;
|
||
|
|
|
||
|
|
1.9
|
||
|
|
date 2006.02.10.14.56.56; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.8;
|
||
|
|
|
||
|
|
1.8
|
||
|
|
date 2006.02.10.14.13.42; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.7;
|
||
|
|
|
||
|
|
1.7
|
||
|
|
date 2006.02.10.13.50.40; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.6;
|
||
|
|
|
||
|
|
1.6
|
||
|
|
date 2006.02.10.12.07.56; author DonaldHobern; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.5;
|
||
|
|
|
||
|
|
1.5
|
||
|
|
date 2006.02.10.12.07.11; author DonaldHobern; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.4;
|
||
|
|
|
||
|
|
1.4
|
||
|
|
date 2006.02.10.12.05.29; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.3;
|
||
|
|
|
||
|
|
1.3
|
||
|
|
date 2006.02.10.01.56.27; author RichardPyle; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.2;
|
||
|
|
|
||
|
|
1.2
|
||
|
|
date 2006.02.10.01.53.36; author RichardPyle; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.1;
|
||
|
|
|
||
|
|
1.1
|
||
|
|
date 2006.02.09.11.49.10; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next ;
|
||
|
|
|
||
|
|
|
||
|
|
desc
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.26
|
||
|
|
log
|
||
|
|
@Minor fix
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@---++ GUID-1 Workshop Report
|
||
|
|
|
||
|
|
---+++ Introduction
|
||
|
|
The Taxonomic Databases Working Group (TDWG) and the Global Biodiversity Information Facility (GBIF) completed their first Workshop on Globally Unique Identifiers for Biodiversity Informatics (GUID-1) at the National Evolutionary Synthesis Center (NESCent), Durham, NC, USA on Feb 1 3, 2006.
|
||
|
|
|
||
|
|
See [[GUID1Minutes]] for a complete set of materials presented during the workshop. Download the [[wiki.gbif.org/guidwiki/images/GUID-1Report.pdf][report in PDF format]].
|
||
|
|
|
||
|
|
---+++ Motivation
|
||
|
|
A GUID framework is foundational in facilitating systems interoperability in biodiversity informatics. It meets the need for a universally adopted system for assigning and recognizing identifiers in the domain.
|
||
|
|
|
||
|
|
A GUID framework will help to manage and cross-link the many different types of entities that are manipulated analytically in biodiversity informatics and will improve interoperability with other related life sciences domains, such as bioinformatics and ecology.
|
||
|
|
|
||
|
|
---+++ The Group
|
||
|
|
The workshop delegates consisted of a representative cross-section of domain experts from around the world (see [[GUID1Participants]]).
|
||
|
|
|
||
|
|
---+++ Goals
|
||
|
|
The goals of the workshop were to:
|
||
|
|
* Discuss the requirements for globally unique identifiers for biodiversity informatics
|
||
|
|
* Select an optimal GUID technology (LSID, DOI, Handles or other)
|
||
|
|
* Begin to identify key parameters for implementing an effective system
|
||
|
|
* Investigate the use of a RDF-based metadata architecture for GUIDs
|
||
|
|
* Form working groups to address key identified issues before the GUID-2 workshop
|
||
|
|
|
||
|
|
---+++ Outcomes
|
||
|
|
* Life Science Identifiers (LSID) seem the most appropriate GUID strategy in biodiversity informatics.
|
||
|
|
* The use of LSIDs does not preclude the use of other technologies where appropriate.
|
||
|
|
* LSID authorities must use the Domain Name Service (DNS) to support identifier resolution. (The LSID specification allows for other resolution mechanisms, but DNS is currently the only mechanism in use.)
|
||
|
|
* Although it is not possible to prevent multiple data providers from issuing alternate identifiers resolving to the same data record, the community should develop processes and tools to coordinate issuing of single identifiers for some classes of data (e.g. taxon names).
|
||
|
|
* Metadata should be provided as RDF serialized as XML and should exploit existing vocabularies such as Dublin Core wherever these are in wide use.
|
||
|
|
* The LSID getData method should be used only where it is possible and appropriate to return an unchanging series of bytes. In other cases only the LSID getMetadata method should be used. (This reflects the use of the terms "data" and "metadata" in connection with LSIDs.)
|
||
|
|
|
||
|
|
---+++ Justifications
|
||
|
|
The main criteria leading to the selection of LSID technology were:
|
||
|
|
* The cost-model of DOI. That technology is predicated on the idea that a revenue stream can be constructed for the identified objects, typically sufficient to defray the cost. That this is not the case for most, if not all, of the objects that are likely to be identified in our systems.
|
||
|
|
* The more dynamic nature of LSIDs, which does not require prior registration of every individual identifier before use.
|
||
|
|
* The open nature of the LSID protocol and software stack, and the ease of implementing LSIDs on different platforms.
|
||
|
|
Technology Comparison
|
||
|
|
The group compared the GUID technologies according to the following criteria:
|
||
|
|
|
||
|
|
*Opacity*: Is the identifier free from embedded semantic information?
|
||
|
|
Opacity was identified as a possibly important criterion in that genuinely opaque identifiers could not be used to make false inferences about the object represented by a GUID. Handles, DOIs and LSIDs all include similar levels of embedded information.
|
||
|
|
|
||
|
|
*Governance*: Is there a body that monitors the assignment of identifiers?
|
||
|
|
DOI has a more formal governance model for identifiers than the other standards. Assignment of identifiers is a more strongly contractual matter and all identifier assignment and access is mediated through the DOI registration infrastructure. Several use cases for GUIDs in biodiversity informatics require more dynamic assignment and resolution paths.
|
||
|
|
|
||
|
|
*Guaranteed persistent*: Is there any guarantee that identifiers will remain resolvable other than the commitments made by the assigning authority (commitments which must be made regardless of which technology is adopted)?
|
||
|
|
The central DOI infrastructure holds the registered identifiers and makes some commitments to host orphaned data.
|
||
|
|
|
||
|
|
*Registration of assigning organisations*: Must institutions register before being permitted to issue identifiers?
|
||
|
|
Issuing authorities for Handles and DOIs are registered centrally. LSID resolvers must be registered in DNS but do not need to be identified to a central LSID authority.
|
||
|
|
|
||
|
|
*Registration of identifiers*: Must institutions register each identifier before use?
|
||
|
|
DOIs are only resolvable if they are known to the central authority.
|
||
|
|
|
||
|
|
*Metadata*: Do the identifiers have a standard association with metadata?
|
||
|
|
Both DOIs and LSIDs have mechanisms to provide access to metadata.
|
||
|
|
|
||
|
|
*Resolvable*: Does the identifier include a mechanism to retrieve the associated metadata and data?
|
||
|
|
Handles, DOIs and LSIDs are all resolvable in this way.
|
||
|
|
|
||
|
|
*Globally unique*: Is there a commitment that the identifier will uniquely identify a single object?
|
||
|
|
Handles, DOIs and LSIDs all involve commitments to global uniqueness.
|
||
|
|
|
||
|
|
*Relocatable*: Can an organisation's identifiers be transferred for a different organisation to resolve (e.g. upon closure of the issuing institution)?
|
||
|
|
An assigner of Handles, DOIs or LSIDs can pass responsibility for resolution to another resolver organisation.
|
||
|
|
|
||
|
|
*Individually relocatable*: Can individual identifiers be transferred for a different organisation to resolve?
|
||
|
|
Individual DOIs may be assigned to other organisations to resolve. This is not possible with LSIDs.
|
||
|
|
|
||
|
|
*Open architecture*: Does TDWG have the ability to take over ownership of the standard and software if others stop supporting it?
|
||
|
|
Handle and DOI are both based on proprietary technologies. LSID is based on a more open strategy.
|
||
|
|
|
||
|
|
*Affordable*: Is the technology affordable for TDWG, GBIF and its partners?
|
||
|
|
TDWG partners together expect to assign many millions of GUIDs and have no model to fund the cost of DOIs. The cost of licensing Handle technology is unclear. LSIDs will involve costs in development of processes and infrastructure, but TDWG has more control over the process.
|
||
|
|
|
||
|
|
---+++ Summary Technology Comparison
|
||
|
|
The following table includes catalogue numbers and taxon names for comparison as these are examples of identifiers currently in use for data integration in biodiversity informatics.
|
||
|
|
|
||
|
|
""
|
||
|
|
<table border=0 cellspacing=0 cellpadding=0>
|
||
|
|
<tr>
|
||
|
|
<td> Criterion </td>
|
||
|
|
<td> Catalogue numbers </td>
|
||
|
|
<td> Taxon names </td>
|
||
|
|
<td> Handle </td>
|
||
|
|
<td> DOI </td>
|
||
|
|
<td> LSID </td></tr>
|
||
|
|
<tr><td>Opaque</td><td>+/-</td><td>-</td><td>-</td><td>-</td><td>-</td></tr>
|
||
|
|
<tr><td>Governance</td><td>+/-</td><td>+</td><td>-</td><td>+</td><td>-</td></tr>
|
||
|
|
<tr><td>Guaranteed persistent</td><td>N/A</td><td>N/A</td><td>-</td><td>+</td><td>-</td></tr>
|
||
|
|
<tr><td>Registration of assigning organisations</td><td>-</td><td>-</td><td>+</td><td>+</td><td>-</td></tr>
|
||
|
|
<tr><td>Registration of identifiers</td><td>+/-</td><td>+/-</td><td>-</td><td>+</td><td>-</td></tr>
|
||
|
|
<tr><td>Metadata</td><td>-</td><td>-</td><td>-</td><td>+</td><td>+</td></tr>
|
||
|
|
<tr><td>Resolvable</td><td>-</td><td>-</td><td>+</td><td>+</td><td>+</td></tr>
|
||
|
|
<tr><td>Globally unique</td><td>-</td><td>-</td><td>+</td><td>+</td><td>+</td></tr>
|
||
|
|
<tr><td>Relocatable</td><td>-</td><td>-</td><td>+</td><td>+</td><td>+</td></tr>
|
||
|
|
<tr><td>Individually relocatable</td><td>-</td><td>-</td><td>-</td><td>+</td><td>-</td></tr>
|
||
|
|
<tr><td>Open architecture</td><td>-</td><td>-</td><td>-</td><td>-</td><td>+</td></tr>
|
||
|
|
<tr><td>Affordable</td><td>+</td><td>+</td><td>?</td><td>-</td><td>+</td></tr>
|
||
|
|
</table>
|
||
|
|
""
|
||
|
|
|
||
|
|
Table 1 - Summary Comparison of GUID Technologies
|
||
|
|
|
||
|
|
---+++ Work plan
|
||
|
|
There are still many issues to address before our community can fully implement an identifier system based on LSIDs. The workshop addressed a number of specific issues and developed working groups to address the following issues:
|
||
|
|
* Developing white papers to address best practices and key infrastructure questions.
|
||
|
|
* Prototyping activities.
|
||
|
|
|
||
|
|
*The Infrastructure Working Group*
|
||
|
|
This group was formed to address the key issues regarding the deployment of LSID as the GUID technology for biodiversity informatics. The mandate of this working group is to identify required or desirable policies and infrastructure components to ensure robust, long-term operation of shared GUIDs.
|
||
|
|
|
||
|
|
The following activities were identified:
|
||
|
|
1. [[LSIDMinimalStandards][Specify minimal standards (including tools and services) for GUID issuance.]]
|
||
|
|
1. [[LSIDLongTermArchival][Investigate long-term archival of LSIDs and associated data and metadata.]]
|
||
|
|
1. [[GUIDCentralRegistrationAuthority][Investigate establishing (optional) central registration authority.]]
|
||
|
|
1. [[GUIDOrphanDatasets][Investigate establishing repository for data and (orphan) datasets with GUIDs.]]
|
||
|
|
1. [[PublicationBank][Investigate the feasibility, existing actors and requirements for a "Publication Bank"]], i.e, a resource to act as a central registry of taxonomic literature and its digital representations, including assigning GUIDs to each publication.
|
||
|
|
1. [[ConceptualVsDigitalLSIDs][Clarify the distinction between GUIDs assigned to data objects and to conceptual entities.]]
|
||
|
|
1. [[GUIDAnnotationAndLinkOut][Investigate 3rd-party annotation and link-out mechanisms.]]
|
||
|
|
1. [[GUIDOutreach][Develop materials to communicate with wider community.]]
|
||
|
|
1. [[LSIDResolverNamespaces][Develop best practices for assigning resolver namespaces for LSIDs.]]
|
||
|
|
1. [[LSIDSpecificationReview][Perform review of LSID specification to identify possible enhancements.]]
|
||
|
|
1. [[LSIDSoftwareGapAnalysis][Perform gap analysis of LSID software.]]
|
||
|
|
|
||
|
|
(Click the links above to view more information about each activity, including current status.)
|
||
|
|
|
||
|
|
The outcomes of this group will be a series of white papers addressing the key infrastructure issues. Those will be reviewed during the second GUID meeting later this year.
|
||
|
|
|
||
|
|
*The Prototyping Working Group*
|
||
|
|
Our community must experiment with LSID technology and Ontology Engineering if we are to implement a production quality LSID system, The working group will develop prototypes of test cases to test aspects of a GUID infrastructure.
|
||
|
|
|
||
|
|
The group will develop test LSID resolvers using data objects provided by each domain, such as names, specimens, and concepts. This activity will also help involve (and train) the community in developing appropriate RDF ontologies, leading to concrete recommendations and implementations.
|
||
|
|
|
||
|
|
The potential prototypes to be developed and respective Conveners are:
|
||
|
|
1. [[LSIDResolverForTaxonNames][LSID resolver for taxon names]] - developed by nomenclators using IPNI database and an RDF version of TCS-Names - Group responsible: Roger Hyam, Sally Hinchcliffe, Paul Kirk
|
||
|
|
1. [[LSIDResolverForSpecimens][LSID resolver for specimens]] using DarwinCore (also ABCD?) - Steve Perry.
|
||
|
|
1. [[LSIDResolverForTaxonConcepts][LSID resolver for taxon concepts]] by SEEK using TCS.
|
||
|
|
1. [[LSIDResolverForObservations][LSID resolver for observations]] by SEEK using EML.
|
||
|
|
1. [[LSIDResolverForCharacterData][LSID resolver for character data]] by Damian Barnier, Kevin Thiele
|
||
|
|
1. [[LSIDResolverForImages][LSID resolver for images]]: Greg Riccardi (Morphbank), Bob Morris
|
||
|
|
|
||
|
|
The taxon names resolver has the highest priority.
|
||
|
|
|
||
|
|
Prototypes will address one or more of the following (but may not be full implementations of an LSID resolution service):
|
||
|
|
* Hardware and software (including LSID stack)
|
||
|
|
* RDFS/OWL vocabulary for domain
|
||
|
|
* Data mapping between local data store scheme and shared ontology
|
||
|
|
|
||
|
|
Other important tasks identified by this group are:
|
||
|
|
* Development of ontologies to represent metadata for the various domains. Coordinated by TDWG TAG with help of experienced ontology engineers.
|
||
|
|
* To set up a real live LSID server to [[LSIDScalabilityTesting][perform scalability testing]].
|
||
|
|
* [[LSIDBasedIntegrationAntsDemo][A project to demonstrate the potential from LSID-based integration of data for a particular group (Ants)]] - LSIDs, taxonomic lit, specimen, images, names, sequences from Genbank - Rod Page
|
||
|
|
* To use [[LSIDSeekTaxonResolutionServer][SEEK Taxon resolution server (alpha) for testing]].
|
||
|
|
|
||
|
|
This group will have 3 months to work on the specified tasks before preparing for the second GUID workshop.
|
||
|
|
|
||
|
|
---+++ Next Workshop: GUID-2
|
||
|
|
The TDWG Infrastructure Project is planning a second GUID workshop in late May or early June, 2006. At the time of writing a venue has not been decided.
|
||
|
|
|
||
|
|
The second workshop should cover the following:
|
||
|
|
* Review of the material produced between the workshops by both working groups (prototypes and white papers).
|
||
|
|
* Summary of the lessons learned in the process.
|
||
|
|
* Identify open issues and devise specific work plans to address them.
|
||
|
|
* Draft concrete recommendations on GUIDs for production systems - in general and for each specific domain (names, specimens, concepts, images, etc).
|
||
|
|
|
||
|
|
Information about GUID-2 will be distributed as soon as possible.
|
||
|
|
|
||
|
|
|
||
|
|
----
|
||
|
|
---++++ How to provide your feedback on this report
|
||
|
|
|
||
|
|
Contrary to the nature of wikis (including this one), we would like this report to be an static document reflecting what was discussed and agreed during the GUID-1 workshop, rather than a continuously evolving document.
|
||
|
|
|
||
|
|
For that reason, we will lock this page for editing. If you have any questions and comments, please edit the [[GUID1ReportComments]] page.
|
||
|
|
|
||
|
|
Ongoing discussion should happen elsewhere in this wiki. We are currently working to reorganize the wiki to provide suitable places for those discussions.
|
||
|
|
|
||
|
|
Thanks for your understanding.
|
||
|
|
|
||
|
|
|
||
|
|
----
|
||
|
|
---+++++ Categories
|
||
|
|
CategoryGUID1
|
||
|
|
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.25
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d9 1
|
||
|
|
a9 2
|
||
|
|
A GUID framework is foundational in facilitating systems interoperability in biodiversity informatics. It meets the need for a universally
|
||
|
|
adopted system for assigning and recognizing identifiers in the domain.
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.24
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d146 1
|
||
|
|
a146 1
|
||
|
|
Each prototype will include the following components:
|
||
|
|
d148 1
|
||
|
|
a148 1
|
||
|
|
* RDFS/OWL ontology for domain
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.23
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d4 1
|
||
|
|
a4 1
|
||
|
|
The Taxonomic Databases Working Group (TDWG) and the Global Biodiversity Information Facility (GBIF) completed their first Workshop on Globally Unique Identifiers for Biodiversity Informatics (GUID-1) at the National Center for Evolutionary Synthesis (NESCent), Durham, NC, USA on Feb 1 3, 2006.
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.22
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d127 1
|
||
|
|
a127 1
|
||
|
|
(Click the links above to view more information, including current status, of each activity)
|
||
|
|
d137 6
|
||
|
|
a142 6
|
||
|
|
1. LSID resolver for taxon names - developed by nomenclators using IPNI database and an RDF version of TCS-Names - Group responsible: Roger Hyam, Sally Hinchcliffe, Paul Kirk
|
||
|
|
1. LSID resolver for specimens using DarwinCore (also ABCD?) - Steve Perry.
|
||
|
|
1. LSID resolver for taxon concepts by SEEK using TCS.
|
||
|
|
1. LSID resolver for observations by SEEK using EML.
|
||
|
|
1. LSID resolver for character data by Damian Barnier, Kevin Thiele
|
||
|
|
1. LSID resolver for images: Greg Riccardi (MorphBank), Bob Morris
|
||
|
|
d153 3
|
||
|
|
a155 3
|
||
|
|
* To set up a real live LSID server to perform scalability testing.
|
||
|
|
* A project to demonstrate the potential from LSID-based integration of data for a particular group (Ants) - LSIDs, taxonomic lit, specimen, images, names, sequences from Genbank - Rod Page
|
||
|
|
* To use SEEK Taxon resolution server (alpha) for testing.
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.21
|
||
|
|
log
|
||
|
|
@Added page to CategoryGUID1
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d115 13
|
||
|
|
a127 11
|
||
|
|
1. Specify minimal standards (including tools and services) for GUID issuance.
|
||
|
|
1. Investigate long-term archival of LSIDs and associated data and metadata.
|
||
|
|
1. Investigate establishing (optional) central registration authority.
|
||
|
|
1. Investigate establishing repository for data and (orphan) datasets with GUIDs
|
||
|
|
1. Investigate the feasibility, existing actors and requirements for a "Publication Bank" (a resource to act as a central registry of taxonomic literature and its digital representations, including assigning GUIDs to each publication.
|
||
|
|
1. Clarify the distinction between GUIDs assigned to data objects and to conceptual entities ([[ConceptualVsDigitalLSIDs]]).
|
||
|
|
1. Investigate 3rd-party annotation and link-out mechanisms.
|
||
|
|
1. Develop materials to communicate with wider community.
|
||
|
|
1. Develop best practices for assigning resolver namespaces for LSIDs.
|
||
|
|
1. Perform review of LSID specification to identify possible enhancements.
|
||
|
|
1. Perform gap analysis of LSID software.
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.20
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d178 7
|
||
|
|
a184 1
|
||
|
|
Thanks for your understanding.@
|
||
|
|
|
||
|
|
|
||
|
|
1.19
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@a109 1
|
||
|
|
* Distingusihing GUIDs for Data Objects vs. Conceptual Entities
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.18
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d175 1
|
||
|
|
a175 1
|
||
|
|
For that reason, we will lock this page for editing. If you have any questions and comments, please use the *add comment* link below or edit the [[GUID1ReportComments]] page.
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.17
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d175 1
|
||
|
|
a175 1
|
||
|
|
For that reason, we will lock this page for editing. If you have any questions and comments, please use the *add comment* link below or edit the GUID1ReportComments page.
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.16
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d175 1
|
||
|
|
a175 1
|
||
|
|
For that reason, we will lock this page for editing. If you have any questions and comments, please use the *add comment* link below.
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.15
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d6 1
|
||
|
|
a6 3
|
||
|
|
See [[GUID1Minutes]] for a complete set of materials presented during the workshop.
|
||
|
|
|
||
|
|
Here is the [[wiki.gbif.org/guidwiki/images/GUID-1Report.pdf][report in PDF format]].
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.14
|
||
|
|
log
|
||
|
|
@Added link to PDF version of report.
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d128 1
|
||
|
|
a128 1
|
||
|
|
1. Perform gap analysis of LSID software..
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.13
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d4 5
|
||
|
|
a8 1
|
||
|
|
The Taxonomic Databases Working Group (TDWG) and the Global Biodiversity Information Facility (GBIF) completed their first Workshop on Globally Unique Identifiers for Biodiversity Informatics (GUID-1) at the National Center for Evolutionary Synthesis (NESCent), Durham, NC, USA on Feb 1 3, 2006. See [[GUID1Minutes]] for a complete set of materials presented during the workshop.
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.12
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d119 1
|
||
|
|
a119 1
|
||
|
|
1. Clarify the distinction between GUIDs assigned to data objects and to conceptual entities ([[ConceptualVsDigitalLSIDs]][[NullHubGUIDs]]).
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.11
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d119 1
|
||
|
|
a119 1
|
||
|
|
1. Clarify the distinction between GUIDs assigned to data objects and to conceptual entities ([[NullHubGUIDs]]).
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.10
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d119 1
|
||
|
|
a155 14
|
||
|
|
*The "GUIDs for Data Objects vs. Conceptual Entities" Working Group*
|
||
|
|
GUIDs may be assigned to both "digital objects" (specific byte sequences), or to conceptual ("abstract") entities, and this group concluded that both play a role in biodiversity informatics.
|
||
|
|
|
||
|
|
__Digital Byte Sequences__
|
||
|
|
* Permanent, unchanging sequences of digital bits (e.g., digital images, ASCII-rendered DNA sequences, locked PDF files, specific versions of a particular database record [e.g. XML or RDF serialization of a database record], etc.)
|
||
|
|
|
||
|
|
__Conceptual ("Abstract") Entities__
|
||
|
|
* Conceptualized "notions" of an object or event
|
||
|
|
* No data content (null)
|
||
|
|
* Serve as "hubs" to cluster and relate other GUID-tagged objects
|
||
|
|
* Rarely exists without at least one Digital Byte Sequence GUID directly or indirectly linked
|
||
|
|
|
||
|
|
This group agreed to take on the task of developing a series of Wiki Pages to clarify the distinction between these two fundamental kinds of GUIDs, and to illustrate how both would be used within the biodiversity informatics community.
|
||
|
|
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.9
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d133 1
|
||
|
|
a133 1
|
||
|
|
1. LSID resolver for taxon names - developed by nomenclators using IPNI database and an RDF version of TCS-Names - Group responsible: Roger Hyam, Sally Hunchcliffe, Paul Kirk
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.8
|
||
|
|
log
|
||
|
|
@Minor change to link to participants.
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d4 1
|
||
|
|
a4 1
|
||
|
|
The Taxonomic Databases Working Group (TDWG) and the Global Biodiversity Information Facility (GBIF) completed their first Workshop on Globally Unique Identifiers for Biodiversity Informatics (GUID-1) at the National Center for Evolutionary Synthesis (NESCent), Durham, NC, USA on Feb 1 3, 2006.
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.7
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d13 1
|
||
|
|
a13 1
|
||
|
|
The workshop delegates consisted of a representative cross-section of domain experts from around the world.(see [[GUID1Participants]]).
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.6
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d178 13
|
||
|
|
a190 1
|
||
|
|
Information about GUID-2 will be distributed as soon as possible.@
|
||
|
|
|
||
|
|
|
||
|
|
1.5
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d108 1
|
||
|
|
a108 1
|
||
|
|
* Distingusihing GUIDs for Data Objecs vs. Conceptual Entities
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.4
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d155 1
|
||
|
|
a155 1
|
||
|
|
*The "GUIDs for Data Objecs vs. Conceptual Entities" Working Group*
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.3
|
||
|
|
log
|
||
|
|
@Minor corrections to Data GUIDs vs. Concepual GUIDs section
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d17 5
|
||
|
|
a21 5
|
||
|
|
• Discuss the requirements for globally unique identifiers for biodiversity informatics
|
||
|
|
• Select an optimal GUID technology (LSID, DOI, Handles or other)
|
||
|
|
• Begin to identify key parameters for implementing an effective system
|
||
|
|
• Investigate the use of a RDF-based metadata architecture for GUIDs
|
||
|
|
• Form working groups to address key identified issues before the GUID-2 workshop
|
||
|
|
d24 6
|
||
|
|
a29 6
|
||
|
|
• Life Science Identifiers (LSID) seem the most appropriate GUID strategy in biodiversity informatics.
|
||
|
|
• The use of LSIDs does not preclude the use of other technologies where appropriate.
|
||
|
|
• LSID authorities must use the Domain Name Service (DNS) to support identifier resolution. (The LSID specification allows for other resolution mechanisms, but DNS is currently the only mechanism in use.)
|
||
|
|
• Although it is not possible to prevent multiple data providers from issuing alternate identifiers resolving to the same data record, the community should develop processes and tools to coordinate issuing of single identifiers for some classes of data (e.g. taxon names).
|
||
|
|
• Metadata should be provided as RDF serialized as XML and should exploit existing vocabularies such as Dublin Core wherever these are in wide use.
|
||
|
|
• The LSID getData method should be used only where it is possible and appropriate to return an unchanging series of bytes. In other cases only the LSID getMetadata method should be used. (This reflects the use of the terms "data" and "metadata" in connection with LSIDs.)
|
||
|
|
d33 3
|
||
|
|
a35 3
|
||
|
|
• The cost-model of DOI. That technology is predicated on the idea that a revenue stream can be constructed for the identified objects, typically sufficient to defray the cost. That this is not the case for most, if not all, of the objects that are likely to be identified in our systems.
|
||
|
|
• The more dynamic nature of LSIDs, which does not require prior registration of every individual identifier before use.
|
||
|
|
• The open nature of the LSID protocol and software stack, and the ease of implementing LSIDs on different platforms.
|
||
|
|
d80 7
|
||
|
|
a86 1
|
||
|
|
<tr><td>Criterion</td><td>Catalogue numbers</td><td>Taxon names</td><td>Handle</td><td>DOI</td><td>LSID</td></tr>
|
||
|
|
d106 3
|
||
|
|
a108 3
|
||
|
|
• Developing white papers to address best practices and key infrastructure questions.
|
||
|
|
• Prototyping activities.
|
||
|
|
• Distingusihing GUIDs for Data Objecs vs. Conceptual Entities
|
||
|
|
d114 10
|
||
|
|
a123 10
|
||
|
|
1. Specify minimal standards (including tools and services) for GUID issuance.
|
||
|
|
2. Investigate long-term archival of LSIDs and associated data and metadata.
|
||
|
|
3. Investigate establishing (optional) central registration authority.
|
||
|
|
4. Investigate establishing repository for data and (orphan) datasets with GUIDs
|
||
|
|
5. Investigate the feasibility, existing actors and requirements for a "Publication Bank" (a resource to act as a central registry of taxonomic literature and its digital representations, including assigning GUIDs to each publication.
|
||
|
|
6. Investigate 3rd-party annotation and link-out mechanisms.
|
||
|
|
7. Develop materials to communicate with wider community.
|
||
|
|
8. Develop best practices for assigning resolver namespaces for LSIDs.
|
||
|
|
9. Perform review of LSID specification to identify possible enhancements.
|
||
|
|
10. Perform gap analysis of LSID software..
|
||
|
|
d133 6
|
||
|
|
a138 6
|
||
|
|
1. LSID resolver for taxon names - developed by nomenclators using IPNI database and an RDF version of TCS-Names - Group responsible: Roger Hyam, Sally Hunchcliffe, Paul Kirk
|
||
|
|
2. LSID resolver for specimens using DarwinCore (also ABCD?) - Steve Perry.
|
||
|
|
3. LSID resolver for taxon concepts by SEEK using TCS.
|
||
|
|
4. LSID resolver for observations by SEEK using EML.
|
||
|
|
5. LSID resolver for character data by Damian Barnier, Kevin Thiele
|
||
|
|
6. LSID resolver for images: Greg Riccardi (MorphBank), Bob Morris
|
||
|
|
d143 3
|
||
|
|
a145 3
|
||
|
|
• Hardware and software (including LSID stack)
|
||
|
|
• RDFS/OWL ontology for domain
|
||
|
|
• Data mapping between local data store scheme and shared ontology
|
||
|
|
d148 4
|
||
|
|
a151 4
|
||
|
|
• Development of ontologies to represent metadata for the various domains. Coordinated by TDWG TAG with help of experienced ontology engineers.
|
||
|
|
• To set up a real live LSID server to perform scalability testing.
|
||
|
|
• A project to demonstrate the potential from LSID-based integration of data for a particular group (Ants) - LSIDs, taxonomic lit, specimen, images, names, sequences from Genbank - Rod Page
|
||
|
|
• To use SEEK Taxon resolution server (alpha) for testing.
|
||
|
|
d159 1
|
||
|
|
a159 1
|
||
|
|
• Permanent, unchanging sequences of digital bits (e.g., digital images, ASCII-rendered DNA sequences, locked PDF files, specific versions of a particular database record [e.g. XML or RDF serialization of a database record], etc.)
|
||
|
|
d162 4
|
||
|
|
a165 4
|
||
|
|
• Conceptualized "notions" of an object or event
|
||
|
|
• No data content (null)
|
||
|
|
• Serve as "hubs" to cluster and relate other GUID-tagged objects
|
||
|
|
• Rarely exists without at least one Digital Byte Sequence GUID directly or indirectly linked
|
||
|
|
d173 4
|
||
|
|
a176 4
|
||
|
|
• Review of the material produced between the workshops by both working groups (prototypes and white papers).
|
||
|
|
• Summary of the lessons learned in the process.
|
||
|
|
• Identify open issues and devise specific work plans to address them.
|
||
|
|
• Draft concrete recommendations on GUIDs for production systems - in general and for each specific domain (names, specimens, concepts, images, etc).
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.2
|
||
|
|
log
|
||
|
|
@Added section on GUIDs for conceptula vs. data objects
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d161 1
|
||
|
|
a161 1
|
||
|
|
This group agreed to take on the task of developing a series of Wiki Pages to clarify the distinction between these two fundamental kinds of LSIDs, and to illustrate how both would be used within the biodiversity informatics community.
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.1
|
||
|
|
log
|
||
|
|
@Initial revision
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d102 1
|
||
|
|
d121 1
|
||
|
|
a121 1
|
||
|
|
---+++ The Prototyping Working Group
|
||
|
|
d149 14
|
||
|
|
d172 1
|
||
|
|
a172 1
|
||
|
|
Information about GUID-2 will be distributed as soon as possible.
|
||
|
|
@
|