head	1.144;
access;
symbols;
locks; strict;
comment	@# @;


1.144
date	2013.01.21.20.31.29;	author KevinRichards;	state Exp;
branches;
next	1.143;

1.143
date	2009.11.12.15.16.06;	author BenRichardson;	state Exp;
branches;
next	1.142;

1.142
date	2009.10.21.22.01.21;	author KevinRichards;	state Exp;
branches;
next	1.141;

1.141
date	2008.12.19.02.41.40;	author KevinRichards;	state Exp;
branches;
next	1.140;

1.140
date	2008.12.16.22.14.17;	author LeeBelbin;	state Exp;
branches;
next	1.139;

1.139
date	2008.12.05.05.43.21;	author LeeBelbin;	state Exp;
branches;
next	1.138;

1.138
date	2007.11.06.14.09.33;	author RogerHyam;	state Exp;
branches;
next	1.137;

1.137
date	2007.08.20.17.47.16;	author RicardoPereira;	state Exp;
branches;
next	1.136;

1.136
date	2007.05.07.14.09.54;	author RicardoPereira;	state Exp;
branches;
next	1.135;

1.135
date	2007.04.11.15.44.33;	author AlexChapman;	state Exp;
branches;
next	1.134;

1.134
date	2007.02.24.11.27.09;	author RicardoPereira;	state Exp;
branches;
next	1.133;

1.133
date	2007.02.23.11.15.59;	author RicardoPereira;	state Exp;
branches;
next	1.132;

1.132
date	2007.02.23.03.20.51;	author LeeBelbin;	state Exp;
branches;
next	1.131;

1.131
date	2007.02.22.15.35.13;	author RicardoPereira;	state Exp;
branches;
next	1.130;

1.130
date	2007.02.21.19.29.05;	author RicardoPereira;	state Exp;
branches;
next	1.129;

1.129
date	2007.02.15.23.39.07;	author RicardoPereira;	state Exp;
branches;
next	1.128;

1.128
date	2007.01.29.17.19.15;	author RicardoPereira;	state Exp;
branches;
next	1.127;

1.127
date	2007.01.29.14.26.09;	author RicardoPereira;	state Exp;
branches;
next	1.126;

1.126
date	2006.10.11.13.53.15;	author RicardoPereira;	state Exp;
branches;
next	1.125;

1.125
date	2006.10.11.13.38.03;	author RicardoPereira;	state Exp;
branches;
next	1.124;

1.124
date	2006.10.11.13.36.40;	author RicardoPereira;	state Exp;
branches;
next	1.123;

1.123
date	2006.10.11.13.35.07;	author RicardoPereira;	state Exp;
branches;
next	1.122;

1.122
date	2006.06.22.17.39.05;	author RicardoPereira;	state Exp;
branches;
next	1.121;

1.121
date	2006.06.13.10.43.33;	author RicardoPereira;	state Exp;
branches;
next	1.120;

1.120
date	2006.06.12.20.55.59;	author RicardoPereira;	state Exp;
branches;
next	1.119;

1.119
date	2006.06.10.14.28.28;	author RicardoPereira;	state Exp;
branches;
next	1.118;

1.118
date	2006.05.24.15.35.02;	author RicardoPereira;	state Exp;
branches;
next	1.117;

1.117
date	2006.05.18.09.26.00;	author LeeBelbin;	state Exp;
branches;
next	1.116;

1.116
date	2006.04.18.09.20.56;	author LeeBelbin;	state Exp;
branches;
next	1.115;

1.115
date	2006.04.17.17.08.56;	author RicardoPereira;	state Exp;
branches;
next	1.114;

1.114
date	2006.03.09.11.42.46;	author RicardoPereira;	state Exp;
branches;
next	1.113;

1.113
date	2006.03.08.23.53.59;	author RicardoPereira;	state Exp;
branches;
next	1.112;

1.112
date	2006.03.02.14.17.41;	author RicardoPereira;	state Exp;
branches;
next	1.111;

1.111
date	2006.03.02.14.15.28;	author RicardoPereira;	state Exp;
branches;
next	1.110;

1.110
date	2006.03.02.14.12.29;	author RicardoPereira;	state Exp;
branches;
next	1.109;

1.109
date	2006.03.02.14.11.18;	author RicardoPereira;	state Exp;
branches;
next	1.108;

1.108
date	2006.03.02.14.03.42;	author RicardoPereira;	state Exp;
branches;
next	1.107;

1.107
date	2006.03.02.14.03.26;	author RicardoPereira;	state Exp;
branches;
next	1.106;

1.106
date	2006.03.02.14.03.03;	author RicardoPereira;	state Exp;
branches;
next	1.105;

1.105
date	2006.02.24.21.23.10;	author RicardoPereira;	state Exp;
branches;
next	1.104;

1.104
date	2006.02.23.23.40.01;	author RicardoPereira;	state Exp;
branches;
next	1.103;

1.103
date	2006.02.13.19.38.29;	author RicardoPereira;	state Exp;
branches;
next	1.102;

1.102
date	2006.02.13.19.02.36;	author RicardoPereira;	state Exp;
branches;
next	1.101;

1.101
date	2006.02.13.02.19.37;	author RicardoPereira;	state Exp;
branches;
next	1.100;

1.100
date	2006.02.13.02.18.45;	author RicardoPereira;	state Exp;
branches;
next	1.99;

1.99
date	2006.02.10.14.37.33;	author RicardoPereira;	state Exp;
branches;
next	1.98;

1.98
date	2006.02.10.12.16.40;	author RicardoPereira;	state Exp;
branches;
next	1.97;

1.97
date	2006.02.09.11.35.06;	author RicardoPereira;	state Exp;
branches;
next	1.96;

1.96
date	2006.01.27.19.37.14;	author RicardoPereira;	state Exp;
branches;
next	1.95;

1.95
date	2006.01.27.03.51.38;	author RicardoPereira;	state Exp;
branches;
next	1.94;

1.94
date	2006.01.27.03.51.12;	author RicardoPereira;	state Exp;
branches;
next	1.93;

1.93
date	2006.01.27.03.23.45;	author RicardoPereira;	state Exp;
branches;
next	1.92;

1.92
date	2006.01.27.03.17.23;	author RicardoPereira;	state Exp;
branches;
next	1.91;

1.91
date	2006.01.27.03.17.14;	author RicardoPereira;	state Exp;
branches;
next	1.90;

1.90
date	2006.01.27.03.14.20;	author RicardoPereira;	state Exp;
branches;
next	1.89;

1.89
date	2006.01.27.03.13.51;	author RicardoPereira;	state Exp;
branches;
next	1.88;

1.88
date	2006.01.27.03.11.36;	author RicardoPereira;	state Exp;
branches;
next	1.87;

1.87
date	2006.01.27.03.10.36;	author RicardoPereira;	state Exp;
branches;
next	1.86;

1.86
date	2006.01.27.03.09.27;	author RicardoPereira;	state Exp;
branches;
next	1.85;

1.85
date	2006.01.27.03.09.00;	author RicardoPereira;	state Exp;
branches;
next	1.84;

1.84
date	2006.01.27.03.08.13;	author RicardoPereira;	state Exp;
branches;
next	1.83;

1.83
date	2006.01.27.02.58.55;	author RicardoPereira;	state Exp;
branches;
next	1.82;

1.82
date	2006.01.23.17.36.12;	author RicardoPereira;	state Exp;
branches;
next	1.81;

1.81
date	2006.01.19.17.09.48;	author RicardoPereira;	state Exp;
branches;
next	1.80;

1.80
date	2006.01.07.00.06.52;	author RicardoPereira;	state Exp;
branches;
next	1.79;

1.79
date	2005.12.22.20.56.15;	author RicardoPereira;	state Exp;
branches;
next	1.78;

1.78
date	2005.12.22.20.54.58;	author RicardoPereira;	state Exp;
branches;
next	1.77;

1.77
date	2005.12.22.20.48.17;	author RicardoPereira;	state Exp;
branches;
next	1.76;

1.76
date	2005.12.22.20.33.11;	author RicardoPereira;	state Exp;
branches;
next	1.75;

1.75
date	2005.12.22.20.31.54;	author RicardoPereira;	state Exp;
branches;
next	1.74;

1.74
date	2005.12.22.20.01.42;	author RicardoPereira;	state Exp;
branches;
next	1.73;

1.73
date	2005.12.22.15.31.37;	author RicardoPereira;	state Exp;
branches;
next	1.72;

1.72
date	2005.12.22.15.30.54;	author RicardoPereira;	state Exp;
branches;
next	1.71;

1.71
date	2005.12.22.15.30.34;	author RicardoPereira;	state Exp;
branches;
next	1.70;

1.70
date	2005.12.22.15.29.46;	author RicardoPereira;	state Exp;
branches;
next	1.69;

1.69
date	2005.12.22.15.29.16;	author RicardoPereira;	state Exp;
branches;
next	1.68;

1.68
date	2005.12.22.15.28.30;	author RicardoPereira;	state Exp;
branches;
next	1.67;

1.67
date	2005.12.22.15.14.10;	author RicardoPereira;	state Exp;
branches;
next	1.66;

1.66
date	2005.12.22.15.12.46;	author RicardoPereira;	state Exp;
branches;
next	1.65;

1.65
date	2005.12.22.15.10.28;	author RicardoPereira;	state Exp;
branches;
next	1.64;

1.64
date	2005.12.22.15.09.50;	author RicardoPereira;	state Exp;
branches;
next	1.63;

1.63
date	2005.12.22.15.09.13;	author RicardoPereira;	state Exp;
branches;
next	1.62;

1.62
date	2005.12.22.15.00.16;	author RicardoPereira;	state Exp;
branches;
next	1.61;

1.61
date	2005.12.22.14.58.58;	author RicardoPereira;	state Exp;
branches;
next	1.60;

1.60
date	2005.12.22.14.57.03;	author RicardoPereira;	state Exp;
branches;
next	1.59;

1.59
date	2005.12.22.14.51.44;	author RicardoPereira;	state Exp;
branches;
next	1.58;

1.58
date	2005.12.22.14.51.11;	author RicardoPereira;	state Exp;
branches;
next	1.57;

1.57
date	2005.12.22.14.45.37;	author RicardoPereira;	state Exp;
branches;
next	1.56;

1.56
date	2005.12.22.14.44.59;	author RicardoPereira;	state Exp;
branches;
next	1.55;

1.55
date	2005.12.22.14.43.29;	author RicardoPereira;	state Exp;
branches;
next	1.54;

1.54
date	2005.12.22.14.42.32;	author RicardoPereira;	state Exp;
branches;
next	1.53;

1.53
date	2005.12.22.14.34.33;	author RicardoPereira;	state Exp;
branches;
next	1.52;

1.52
date	2005.12.22.14.32.18;	author RicardoPereira;	state Exp;
branches;
next	1.51;

1.51
date	2005.12.22.14.31.49;	author RicardoPereira;	state Exp;
branches;
next	1.50;

1.50
date	2005.12.22.14.30.31;	author RicardoPereira;	state Exp;
branches;
next	1.49;

1.49
date	2005.12.22.14.29.14;	author RicardoPereira;	state Exp;
branches;
next	1.48;

1.48
date	2005.12.08.01.49.21;	author DonaldHobern;	state Exp;
branches;
next	1.47;

1.47
date	2005.12.08.01.48.41;	author DonaldHobern;	state Exp;
branches;
next	1.46;

1.46
date	2005.11.03.16.18.51;	author DonaldHobern;	state Exp;
branches;
next	1.45;

1.45
date	2005.10.11.17.45.29;	author DonaldHobern;	state Exp;
branches;
next	1.44;

1.44
date	2005.10.11.17.45.13;	author DonaldHobern;	state Exp;
branches;
next	1.43;

1.43
date	2005.09.22.22.23.11;	author RicardoPereira;	state Exp;
branches;
next	1.42;

1.42
date	2005.09.13.15.49.56;	author DonaldHobern;	state Exp;
branches;
next	1.41;

1.41
date	2005.09.10.00.11.20;	author DonaldHobern;	state Exp;
branches;
next	1.40;

1.40
date	2005.09.09.12.08.27;	author DonaldHobern;	state Exp;
branches;
next	1.39;

1.39
date	2005.09.09.12.07.26;	author DonaldHobern;	state Exp;
branches;
next	1.38;

1.38
date	2005.09.09.12.07.00;	author DonaldHobern;	state Exp;
branches;
next	1.37;

1.37
date	2005.09.09.12.06.08;	author DonaldHobern;	state Exp;
branches;
next	1.36;

1.36
date	2005.09.09.12.05.31;	author DonaldHobern;	state Exp;
branches;
next	1.35;

1.35
date	2005.09.09.11.49.39;	author DonaldHobern;	state Exp;
branches;
next	1.34;

1.34
date	2005.09.09.11.18.15;	author DonaldHobern;	state Exp;
branches;
next	1.33;

1.33
date	2005.09.09.11.03.13;	author DonaldHobern;	state Exp;
branches;
next	1.32;

1.32
date	2005.09.09.11.01.55;	author DonaldHobern;	state Exp;
branches;
next	1.31;

1.31
date	2005.09.04.19.23.55;	author DonaldHobern;	state Exp;
branches;
next	1.30;

1.30
date	2005.08.30.13.44.26;	author RicardoPereira;	state Exp;
branches;
next	1.29;

1.29
date	2005.08.30.13.36.45;	author RicardoPereira;	state Exp;
branches;
next	1.28;

1.28
date	2005.08.05.16.28.38;	author DonaldHobern;	state Exp;
branches;
next	1.27;

1.27
date	2005.08.05.16.17.04;	author DonaldHobern;	state Exp;
branches;
next	1.26;

1.26
date	2005.08.05.15.50.13;	author DonaldHobern;	state Exp;
branches;
next	1.25;

1.25
date	2005.08.05.15.27.36;	author DonaldHobern;	state Exp;
branches;
next	1.24;

1.24
date	2005.08.05.15.26.03;	author DonaldHobern;	state Exp;
branches;
next	1.23;

1.23
date	2005.08.05.15.25.34;	author DonaldHobern;	state Exp;
branches;
next	1.22;

1.22
date	2005.08.05.13.06.01;	author DonaldHobern;	state Exp;
branches;
next	1.21;

1.21
date	2005.08.01.10.56.34;	author DonaldHobern;	state Exp;
branches;
next	1.20;

1.20
date	2005.08.01.10.54.50;	author DonaldHobern;	state Exp;
branches;
next	1.19;

1.19
date	2005.07.08.14.50.18;	author DonaldHobern;	state Exp;
branches;
next	1.18;

1.18
date	2005.07.08.14.37.05;	author DonaldHobern;	state Exp;
branches;
next	1.17;

1.17
date	2005.07.08.14.17.00;	author DonaldHobern;	state Exp;
branches;
next	1.16;

1.16
date	2005.07.08.14.15.57;	author DonaldHobern;	state Exp;
branches;
next	1.15;

1.15
date	2005.07.07.16.07.14;	author DonaldHobern;	state Exp;
branches;
next	1.14;

1.14
date	2005.07.07.14.46.20;	author DonaldHobern;	state Exp;
branches;
next	1.13;

1.13
date	2005.07.07.14.15.02;	author DonaldHobern;	state Exp;
branches;
next	1.12;

1.12
date	2005.07.07.14.14.43;	author DonaldHobern;	state Exp;
branches;
next	1.11;

1.11
date	2005.07.07.14.13.17;	author DonaldHobern;	state Exp;
branches;
next	1.10;

1.10
date	2005.07.07.14.12.27;	author DonaldHobern;	state Exp;
branches;
next	1.9;

1.9
date	2005.07.07.14.05.48;	author DonaldHobern;	state Exp;
branches;
next	1.8;

1.8
date	2005.07.07.14.05.06;	author DonaldHobern;	state Exp;
branches;
next	1.7;

1.7
date	2005.07.07.14.04.41;	author DonaldHobern;	state Exp;
branches;
next	1.6;

1.6
date	2005.07.07.14.04.19;	author DonaldHobern;	state Exp;
branches;
next	1.5;

1.5
date	2005.07.07.14.03.52;	author DonaldHobern;	state Exp;
branches;
next	1.4;

1.4
date	2005.07.07.12.55.55;	author DonaldHobern;	state Exp;
branches;
next	1.3;

1.3
date	2005.07.07.12.55.32;	author DonaldHobern;	state Exp;
branches;
next	1.2;

1.2
date	2005.07.07.12.54.31;	author DonaldHobern;	state Exp;
branches;
next	1.1;

1.1
date	2005.05.12.11.38.32;	author WikkaInstaller;	state Exp;
branches;
next	;


desc
@
.
@


1.144
log
@none
@
text
@%META:TOPICINFO{author="KevinRichards" date="1358800289" format="1.1" version="1.144"}%
---+!! Welcome to the Globally Unique Identifiers (GUID) Wiki

Welcome to the *TDWG GUID Wiki*. This is a collaboration area used to discuss the use of *Globally Unique Identifiers* (*GUIDs*) in our community. The [[http://wiki.gbif.org/guidwiki/wikka.php?wakka=HomePage][first Wiki discussion]] about GUIDs in the lead up to the two TIP sponsored GUID meetings (see below) was hosted on the GBIF site.

---++!! Table of Contents

%TOC%

---++ LSID Home Page

Visit the LSID page for documentation on LSIDs.

---++GUID and LSID Applicability Statements Public Review

   * [[GUID and LSID AS Review]] - a page for the collation of submissions for the GUID and LSID Applicability Statement Public Review.

---++ A Definition of Globally Unique Identifiers (for the purposes of this group)

A *globally unique identifier*, or *GUID*, is a system that provides mechanisms to identify and access *data objects* on the Web. The main characteristics of a GUID system are:
   * GUID systems have *identifiers*, which are character strings associated with data objects. *urn:lsid:tdwg.org:TaxonName:12345* and *doi:10.1000/182* are examples of identifiers.
   * An identifier in a GUID system is *persistent*, i.e., it is *permanently* associated with a data object. 
   * An identifier in a GUID system is *globally unique*, i.e., it identifies a single data object uniquely within the system.
   * Identifiers in a GUID system are *actionable*, i.e., the system provides mechanisms for clients to access a data object from its associated identifier. This is equivalent to saying that objects in a GUID system are *locatable*.
   * A GUID system also provides mechanisms to describe data objects, i.e., it provides *metadata* about them.

---++ Relevant Documents

   * [[LsidHttpProxyUsageRecommendations][LSID HTTP Proxy Usage Recommendations]] - a set of rules to make LSID more interoperable with standard World Wide Web and Semantic Web applications.

---++ GUID Working Groups

Two main working groups have been created during [[GUID1Workshop][GUID-1 Workshop]] (see the [[GUID1Report][report]]) to implement the initial components of the GUID infrastructure and to address outstanding issues:

   * InfrastructureWorkingGroup - will address the key issues regarding the deployment of LSID as the GUID technology for biodiversity informatics.
   * PrototypingWorkingGroup - will develop prototypes of test cases to test aspects of a GUID infrastructure.


---++ Events
   * [[AustralasianBiodiversityFederationLsidPolicy][Meeting to develop an LSID deployment policy for the Australasian Biodiversity Federation]] - April 2-4, 2007 at the Australian National Botanic Gardens, Canberra, Austrailia - *This event is past*

   * [[GUID1Workshop][GUID-1 Workshop]] - Feb 1-3, 2006 at [[http://www.nescent.org/main/][NESCent]], Durham, NC, USA - *This event is past*

   * [[GUID2Workshop][GUID-2 Workshop]] - June 10-12, 2006 at the e-Science Institute (e-SI) in Edinburgh, Scotland - *This event is past*


---++ General Content
   * [[Background]] - Information on the TDWG/GBIF GUID initiative
   * [[Glossary]] - Definition of terms used by this community
   * [[Process]] - How we are organizing the work
   * [[HowToParticipate][How to participate]] - Add your comments to the wiki and join our [[http://lists.tdwg.org/mailman/listinfo/tdwg-guid][mailing list]]
   * [[Main.ThreeEasySteps][How to use this wiki]] - Please read before adding new pages
   * People
   * ExistingProjects
   * OutdatedPages


---++ Other Documents
   * [[Technologies][GUID Technologies]] - Candidate technologies under evaluation
   * [[GUIDUseCases][Use Cases]]
   * [[http://www.tdwg.org/2004meet/EV/TDWG_2004_Papers_Thau_1.zip][GUIDs and LSIDs]] - Powerpoint presentation by David Thau (TDWG meeting 2004)
   * [[http://circa.gbif.net/Public/irc/gbif/dadi/library?l=/architecture/globallyuniqueidentifier/_EN_1.0_&a=d][Globally Unique Identifiers for Biodiversity Informatics]] - Powerpoint presentation by Donald Hobern
   * [[http://wiki.gbif.org/dadiwiki/wikka.php?wakka=DPSGloballyUniqueIdentifierServices][GBIF GUID Services Strategy]] - outline plan for development of GBIF GUID services from [[http://circa.gbif.net/Public/irc/gbif/dadi/library?l=/architecture/portal_strategy_1/][GBIF Data Portal Strategy]]
   * ReallyLeanPhpAuthority
  
---++ Software
   * [[LsidSoftwareInventory][Software Inventory]]
   * [[CurrentGuidWork][Current work]]

---++ Contact

The TDWG Infrastructure Project Team was:
   * Lee Belbin, Australia - Project Manager (lee@@tdwg.org)
   * Roger Hyam, United Kingdom - Technical Architect
   * Ricardo Pereira, Brazil - Software Engineer

The GBIF contact is:
   * Éamonn Ó Tuama (eotuama@@gbif.org)


----
---+++++!! Categories
CategoryWiki
CategoryUsers

@


1.143
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BenRichardson" date="1258038966" format="1.1" reprev="1.143" version="1.143"}%
a70 1
*Kevin Richards* of Landcare New Zealand is leading the TDWG work on LSIDs so please contact him for any issues or further information (RichardsK@@landcareresearch.co.nz).
@


1.142
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="KevinRichards" date="1256162481" format="1.1" version="1.142"}%
a5 3
---++GUID and LSID Applicability Statements Review
    * [[GUID and LSID AS Review]] - a page for the collation of submissions for the review process.

d10 8
a26 3
*Join* the [[http://lists.tdwg.org/mailman/listinfo/tdwg-guid][TDWG-GUID Mailing List]] to follow the discussions.


@


1.141
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="KevinRichards" date="1229654500" format="1.1" version="1.141"}%
d6 3
@


1.140
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="LeeBelbin" date="1229465657" format="1.1" version="1.140"}%
d61 4
@


1.139
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="LeeBelbin" date="1228455801" format="1.1" reprev="1.139" version="1.139"}%
d4 1
a4 1
Welcome to the *TDWG GUID Wiki*. This is a collaboration area used to discuss the use of *Globally Unique Identifiers* (*GUIDs*) in our community.
@


1.138
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RogerHyam" date="1194358173" format="1.1" version="1.138"}%
d61 2
a62 2
---++ Contacts
For further information, please send messages to ricardo@@tdwg.org.
d64 2
a65 2
The TDWG Infrastructure Project Team is:
   * Lee Belbin, Australia - Project Manager
d70 1
a70 1
   * Donald Hobern, Programmer Officer for Data Access and Database Interoperability (dhobern@@gbif.org)
@


1.137
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RicardoPereira" date="1187632036" format="1.1" version="1.137"}%
d59 1
a59 1

@


1.136
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RicardoPereira" date="1178546994" format="1.1" version="1.136"}%
d46 1
a46 1
   * [[HowToParticipate][How to participate]] - Add your comments to the wiki and join our [[http://listserv.nhm.ku.edu/archives/tdwg-guid.html][mailing list]]
@


1.135
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="AlexChapman" date="1176306273" format="1.1" version="1.135"}%
d24 1
a24 10
   <!-- Under construction: * [[StatusReportJan2007][Status Report - Jan/2007]]: Current status of the GUID efforts. -->

   * [[TdwgLsidApplicabilityStatement][TDWG LSID Applicability Statement]]

The TDWG GUID group is now drafting the [[TdwgLsidApplicabilityStatement][TDWG LSID Applicability Statement]]. This document is planed to serve as guideline for implementation of LSID resolvers in biodiversity information applications. This specification will summarize all agreed decisions by the GUID group. Comments and suggestions are very welcome.

   * [[LSIDRoadmapOct2006][LSID Roadmap]]

We are also defining the priorities for the group for the next 6 to 9 months regarding LSID work. Take a look and provide your comments on the [[LSIDRoadmapOct2006][LSID Roadmap]].

@


1.134
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RicardoPereira" date="1172316429" format="1.1" reprev="1.134" version="1.134"}%
d44 1
a44 1
   * [[AustralasianBiodiversityFederationLsidPolicy][Meeting to develop an LSID deployment policy for the Australasian Biodiversity Federation]] - April 2-4, 2007 at the Australian National Botanic Gardens, Canberra, Austrailia
@


1.133
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RicardoPereira" date="1172229359" format="1.1" version="1.133"}%
d44 2
a48 5
      * [[GUID2Agenda][Agenda]]
      * [[GUID2Participants][List of Participants]]
      * [[GUID2Report][GUID-2 Report]] - [[http://www.tdwg.gbif.org/fileadmin/subgroups/tip/GUID2Report.pdf][PDF Version]]
      * [[GUID2ReportComments][GUID-2 Report Comments]]
   * [[AustralasianBiodiversityFederationLsidPolicy][Meeting to develop an LSID deployment policy for the Australian Biodiversity Federation]] - April 2-4, 2007 at the Australian National Botanic Gardens, Canberra, Austrailia
@


1.132
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="LeeBelbin" date="1172200851" format="1.1" reprev="1.132" version="1.132"}%
d51 1
a51 1
   * [[AustralianBiodiversityFederationLsidPolicy][Meeting to develop an LSID deployment policy for the Australian Biodiversity Federation]] - April 2-4, 2007 at the Australian National Botanic Gardens, Canberra, Austrailia
@


1.131
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RicardoPereira" date="1172158513" format="1.1" version="1.131"}%
d51 1
@


1.130
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RicardoPereira" date="1172086145" format="1.1" version="1.130"}%
d19 1
a19 1
*Join* the [[http://mailman.nhm.ku.edu/mailman/listinfo/tdwg-guid][TDWG-GUID Mailing List]] to follow the discussions.
@


1.129
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RicardoPereira" date="1171582747" format="1.1" reprev="1.129" version="1.129"}%
d24 1
a24 1
   * [[StatusReportJan2007][Status Report - Jan/2007]]: Current status of the GUID efforts.
@


1.128
log
@none
@
text
@d1 10
a10 2
%META:TOPICINFO{author="RicardoPereira" date="1170091155" format="1.1" version="1.128"}%
---++ TDWG - Globally Unique Identifiers 
a18 2
This group has selected [[LSID]] as the GUID technology for identifying [[http://www.calacademy.org/research/informatics/sblum/pub/biodiv_informatics.html][Biodiversity Informatics]] objects and is standardising its use within the community.

a20 1
----
d34 1
a34 1
----
a42 1
----
d53 1
a53 2
----
---+++ General Content
d64 1
a64 2
----
---+++ Other Documents
d72 1
a72 2
----
---+++ Contacts
d85 1
a85 1
---+++++ Categories
@


1.127
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RicardoPereira" date="1170080769" format="1.1" version="1.127"}%
d5 1
a5 1
   * GUID systems have *identifiers*, which are character strings associated with data objects. *GBIF* and *doi:10.1000/182* are examples of identifiers.
d16 1
d19 2
d55 1
a55 1
   * [[UsingGUIDWiki][How to use this wiki]] - Please read before adding new pages
d87 1
@


1.126
log
@Fixed typo
.
@
text
@d1 1
d13 1
a13 1
*Join* the [[http://listserv.nhm.ku.edu/archives/tdwg-guid.html][TDWG-GUID Mailing List]] to follow the discussions.
d69 1
a69 1
For further information, please send messages to [[guids@@gbif.org]].
d77 1
a77 1
   * Donald Hobern, Programmer Officer for Data Access and Database Interoperability ([[dhobern@@gbif.org]])
d83 1
a83 1
CategoryUsers@


1.125
log
@
.
@
text
@d17 1
a17 1
   * [[TdwgLsidApplibilityStatement][TDWG LSID Applibility Statement]]
d19 1
a19 1
The TDWG GUID group is now drafting the [[TdwgLsidApplibilityStatement][TDWG LSID Applibility Statement]]. This document is planed to serve as guideline for implementation of LSID resolvers in biodiversity information applications. This specification will summarize all agreed decisions by the GUID group. Comments and suggestions are very welcome.
@


1.124
log
@Made links to LSID AS and Roadmap more scannable
.
@
text
@d19 1
a19 2
The TDWG GUID group is now drafting the [[TdwgLsidApplibilityStatement][TDWG LSID Applibility Statement]]. This document is planed to serve as guideline for implementation of LSID resolvers in biodiversity information applications. This specification will summarize all agreed 
decisions by the GUID group. Comments and suggestions are very welcome.
@


1.123
log
@Added hooks for LSID AS and Roadmap
.
@
text
@d17 2
d22 2
@


1.122
log
@Added link to GUID-2 Report (PDF version)
.
@
text
@d15 8
d55 1
a55 1
---+++ Documents
@


1.121
log
@
.
@
text
@d25 1
a25 1
   * [[GUID1Workshop][GUID-1 Workshop]] - Feb 1-3, 2006 at [[http://www.nescent.org/main/][NESCent]], Durham, NC, USA - *Applications are closed*
d27 1
a27 4
   * [[GUID2Workshop][GUID-2 Workshop]] - Planned for June 10-12, 2006 at the e-Science Institute (e-SI) in Edinburgh, Scotland. 
      * [[GUID2Call1][First call for GUID-2]] - First e-mail about GUID-2 (7th March, 2006)
      * [[GUID2Call2][Second call for GUID-2]] - Second e-mail about GUID-2 (5th April, 2006)
      * [[GUID2Announcement][Final issues for GUID-2]] - Announcement of issues (18th May, 2006)
d30 2
a31 1
      * [[GUID2Report][GUID-2 Report]]
@


1.120
log
@
.
@
text
@d33 2
@


1.119
log
@
.
@
text
@a30 1
      * [[CategoryWorkingGroup][Working Groups]]
@


1.118
log
@Added link to GUID-2 agenda and list of participants.
.
@
text
@d32 1
a32 1
      * [[GUID2Agenda][Draft Agenda]]
@


1.117
log
@Add Donald's announcement of issues remaining
.
@
text
@d32 2
@


1.116
log
@Add GUID2-call2
.
@
text
@d30 1
@


1.115
log
@Changed introductory paragraph a bit
.
@
text
@d29 1
@


1.114
log
@Removed GUID-1 details and added some links to GUID-2 resources
.
@
text
@d10 1
a10 1
This group has already selected [[LSID]] as the GUID technology for use in [[http://www.calacademy.org/research/informatics/sblum/pub/biodiv_informatics.html][Biodiversity Informatics]].
@


1.113
log
@Added link to GUID-2 Workshop page
.
@
text
@a25 4
      * [[GUID1Participants][List of Participants]]
      * [[GUID1Minutes][Workshop Minutes and Presentations]]
      * [[GUID1Report][Report (Wiki page)]] or [[%ATTACHURL%/GUID-1Report.pdf][in PDF format]] 
      * [[GUID1ReportComments][Report Comments]]
d28 2
@


1.112
log
@
.
@
text
@d31 1
a31 1
   * GUID-2 Workshop - Planned for mid-2006. Location to be defined.
@


1.111
log
@
.
@
text
@d69 2
a70 1
CategoryWiki@


1.110
log
@
.
@
text
@d41 2
a42 2
   * [[ExistingProjects][Existing Projects]]
   * [[OutdatedPages]]
@


1.109
log
@General update on homepage
.
@
text
@d42 1
a54 11
---+++ Out-of-Date Pages

These [[Topics]] were raised for discussion prior to [[GUID1Workshop][GUID-1 Workshop]]. 

Requirements: 
   * [[Requirements][General GUID Requirements]]
   * [[GUIDRequirementsTaxonomy][Requirements specific to Taxonomic Names and Concepts]]
   * [[GUIDRequirementsSpecimens][Requirements specific to Collections and Specimens]]


----
@


1.108
log
@
.
@
text
@d43 1
d45 1
a45 1
---++ Technical Documents
a47 14
   * Requirements: 
      * [[Requirements][General GUID Requirements]]
      * [[GUIDRequirementsTaxonomy][Requirements specific to Taxonomic Names and Concepts]]
      * [[GUIDRequirementsSpecimens][Requirements specific to Collections and Specimens]]
      * Other domains to be addressed (add yours here)
   * Ontology based framework for GUID metadata - coming soon 

----
---+++ Current Issues and Review Items
*Welcome to the TDWG Globally Unique Identifiers Wiki.  The following topics have been raised for discussion.  Please provide your comments.*  (See [[Topics]] for a full list of topics.)
{{shortsummary catmajor="Topics" catminor="Highlight" textlength="400" hlight="1" extra="1"}}

----
---+++ Documents
d51 1
d54 11
@


1.107
log
@
.
@
text
@d19 1
a19 1
   * InfrastructureWorkingGroup - will address the key issues regarding the deployment of LSID as the GUID technology for biodiversity informatics
@


1.106
log
@Updated homepage content
.
@
text
@d17 1
a17 1
Two main working groups have been created during [[GUID1Workshop][GUID-1 Workshop]](see the [[GUID1Report][report]]) to implement the initial components of the GUID infrastructure and to address outstanding issues:
@


1.105
log
@
.
@
text
@d10 1
a10 4
This group is performing the following tasks: 
   * Reviewing requirements on the use of *GUIDs* to identify collections, specimen, taxonomic and other related datasets
   * Evaluating candidate GUID technologies, such as DOI, Handle, LSID, and ARK
   * Making recommendations to standardize the use of *GUIDs* in [[http://www.calacademy.org/research/informatics/sblum/pub/biodiv_informatics.html][Biodiversity Informatics]]
d17 1
a17 1
Two main working groups have been created during GUID-1 workshop (see the [[GUID1Report][report]]) to implement the initial components of the GUID infrastructure and to address outstanding issues:
@


1.104
log
@
.
@
text
@d80 1
@


1.103
log
@Added link to GUID-1 report comments
.
@
text
@d20 1
a20 1
Two main working groups have been created during GUID-1 workshop to implement the initial components of the GUID infrastructure and to address outstanding issues:
@


1.102
log
@Added links to newly formed GUID working groups
.
@
text
@d32 1
@


1.101
log
@Removed links to obsolete GUID-1 workshop materials
.
@
text
@d18 9
@


1.100
log
@Added link to PDF version of report.
.
@
text
@a19 2
      * [[GUID1Logistics][Logistics]]
      * [[GUID1Agenda][Draft Agenda]]
a20 1
      * [[GUID1Homework][Homework]] for workshop participants
@


1.99
log
@
.
@
text
@d25 1
a25 1
      * [[GUID1Report][Report]]
@


1.98
log
@
.
@
text
@d24 1
@


1.97
log
@Added link to GUID-1 Report
.
@
text
@a9 7
The definition above neatly limits the *scope* of this working group. Therefore, the following topics, although intrinsically related to GUIDs, are outside their scope:
   * How to establish relationships and meaningful linking between objects.
   * Mechanisms that allow clients to query data objects on properties other than their identifiers.
   * Indexing services and data warehouses and the related mechanisms for discovery and harvest of data and metadata.

These topics should be, and already are being addressed by other research groups in our community. This group will provide guidance to them as to how to use the GUIDs effectively to improve data integration and systems interoperability. We hope that the GUID solution being devised here will help those groups achieve their goals.

@


1.96
log
@
.
@
text
@d31 1
@


1.95
log
@
.
@
text
@d27 5
@


1.94
log
@
.
@
text
@d4 1
a4 1
   * GUID systems have *identifiers*, which are character strings associated with data objects. GBIF and doi:10.1000/182 are examples of identifiers.
@


1.93
log
@
.
@
text
@d4 1
a4 1
   * GUID systems have *identifiers*, which are character strings associated with data objects.
@


1.92
log
@
.
@
text
@d3 1
a3 1
A *globally unique identifier* or *GUID* is a system that provides mechanisms to identify and access *data objects* on the Web. The main characteristics of a GUID system are:
@


1.91
log
@
.
@
text
@d10 1
a10 1
The definition above neatly limit the *scope* of this working group. Therefore, the following topics, although intrinsically related to GUIDs, are outside their scope:
@


1.90
log
@
.
@
text
@d10 1
a10 1
The characterization above neatly defines the *scope* of this working group. Therefore, the following topics, although intrinsically related to GUIDs, are outside their scope:
@


1.89
log
@
.
@
text
@d10 1
a10 1
The definition above neatly the *scope* of this working group. Therefore, the following topics, although intrinsically related to GUIDs, are outside their scope:
@


1.88
log
@
.
@
text
@d15 1
a15 1
Other research groups in our community are addressing the topics mentioned above. We hope that the GUID solution being devised here will help those groups achieve their goals.
@


1.87
log
@
.
@
text
@d10 1
a10 1
The definition above neatly defines a GUID system and also the *scope* of this working group. Therefore, the following topics, although intrinsically related to GUIDs, are outside their scope:
@


1.86
log
@
.
@
text
@d5 1
a5 1
   * An identifier in a GUID system is *persistent*, i.e., it is associated with a data object *permanently*. 
d7 1
a7 1
   * Identifiers in a GUID system are *actionable*, i.e., the system provides mechanisms for clients to access a data object from its associated identifier. This is equivalent to say that objects in a GUID system are *locatable*.
@


1.85
log
@
.
@
text
@d3 1
a3 1
A *globally unique identifier* or *GUID* is a system that provides mechanisms to identify and access *data objects* on the Web. The main characteristics of GUID system are:
@


1.84
log
@
.
@
text
@d3 1
a3 1
A *globally unique identifier* (GUID) is a system that provides mechanisms to identify and access *data objects* on the Web. The main characteristics of GUID system are:
@


1.83
log
@Rewrote main definition of GUIDs
.
@
text
@d3 1
a3 1
A *globally unique identifier* (GUID) is system that provides mechanisms to identify and access *data objects* on the Web. The main characteristics of GUID system are:
d8 1
a8 1
   * A GUID system also provides mechanisms to describe the data object, i.e., it provides *metadata* about data objects.
d10 1
a10 1
The definition above neatly defines a GUID system and also the *scope* of this working group. Therefore, the following topics, although are intrinsically related to GUIDs, are outside their scope:
d12 4
a15 2
   * Mechanisms that allow clients to query data objects by properties other than its identifier.
   * Indexing services or data warehouses and related mechanisms for discovery and harvest of data and metadata.
@


1.82
log
@
.
@
text
@d3 11
a13 1
A *globally unique identifier* is a *permanent identifier* used to reference and retrieve *data resources* (i.e. information) on the Web. GUIDs solve the problem of broken links (common in regular URLs) as they can be used to retrieve the associated resource regardless of changes in its location. GUIDs also provide a fundamental infrastructure to improve systems interoperability. 
@


1.81
log
@
.
@
text
@d3 1
a3 1
A *globally unique identifier* is a *permanent identifier* used to identify, reference and retrieve *data resources* (i.e. information) on the Web. GUIDs solve the problem of broken links (common in regular URLs) as they can be used to retrieve the associated resource regardless of changes in its location. GUIDs also provide a fundamental infrastructure to improve systems interoperability. 
@


1.80
log
@
.
@
text
@d20 1
@


1.79
log
@
.
@
text
@d55 1
a55 1
   * Ricardo Pereira, Brazil - Senior Software Engineer
@


1.78
log
@
.
@
text
@d15 1
a15 1
   * GUID-2 Workshop - 3-day workshop to take place in mid-2006 - location to be defined
@


1.77
log
@
.
@
text
@d35 1
@


1.76
log
@
.
@
text
@d32 3
a34 2
      * [[GUIDRequirementsTaxonomy][Requirements specific to taxonomic names and concepts]]
      * [[GUIDRequirementsSpecimens][Requirements specific collections and specimens]]
@


1.75
log
@
.
@
text
@d30 4
a33 1
   * Requirements: [[Requirements][General]], [[GUIDRequirementsTaxonomy][taxonomic names and concepts]], [[GUIDRequirementsSpecimens][Collections and specimens]]
@


1.74
log
@
.
@
text
@d30 1
a30 2
   * [[Requirements]]

@


1.73
log
@
.
@
text
@d30 1
a30 1
   * Requirements
@


1.72
log
@
.
@
text
@d6 1
a6 1
   * Reviewing [[Requirements]] on the use of *GUIDs* to identify collections, specimen, taxonomic and other related datasets
@


1.71
log
@
.
@
text
@d11 1
@


1.70
log
@
.
@
text
@d3 1
a3 1
A *globally unique identifier* is a *permanent identifier* used to identify, reference and retrieve *data resources* (i.e. information) on the Web. GUIDs solve the problem of broken links (common in regular URLs) as they are meant to be permanent and can be used to retrieve the associated resource regardless of changes in its location. GUIDs also provide a fundamental infrastructure to improve systems interoperability. 
@


1.69
log
@
.
@
text
@a10 2


@


1.68
log
@
.
@
text
@d10 1
a10 1
*Join* our [[http://listserv.nhm.ku.edu/archives/tdwg-guid.html][TDWG-GUID Mailing List]] to follow the discussions.
@


1.67
log
@
.
@
text
@d10 3
a39 3
A mailing list ([[http://listserv.nhm.ku.edu/archives/tdwg-guid.html][TDWG-GUID]]) has been established to support discussion in parallel with this wiki.  Instructions on joining the list and archives of previous discussions can be found at http://listserv.nhm.ku.edu/archives/tdwg-guid.html.

----
@


1.66
log
@
.
@
text
@d21 1
a21 1
   * [[People]]
d28 1
a28 1
   * [[Requirements]]
@


1.65
log
@
.
@
text
@d12 2
a13 1
   * [[GUID1Workshop][GUID-1 Workshop]] - Feb 1-3, 2006 at [[http://www.nescent.org/main/][NESCent]], Durham, NC, USA (Applications are closed)
@


1.64
log
@
.
@
text
@d5 1
a5 1
This group is: 
@


1.63
log
@
.
@
text
@d3 1
a3 1
A *globally unique identifier* is a *permanent identifier* used to identify, reference and retrieve *data resources* (i.e. information) on the Web. GUIDs solve the problem of broken links (common in regular URLs) as they are meant to be permanent and can be used to retrieve the associated resource regardless of changes in its location. GUIDs are also provides infrastructure to improve systems interoperability. 
@


1.62
log
@
.
@
text
@d3 1
a3 1
A *globally unique identifier* is a *permanent identifier* assigned to a *digital resource* (i.e. information) so that the resource can be referenced and later retrieved, regardless of the original location. 
@


1.61
log
@
.
@
text
@d3 1
a3 1
A *globally unique identifier* is a *permanent identifier* assigned to a *digital resource* (i.e. information) so it can be referenced and later retrieved, regardless of the original location. 
@


1.60
log
@
.
@
text
@d6 1
a6 1
   * Reviewing [[Requirements]]
@


1.59
log
@
.
@
text
@d3 6
a8 1
We are researching and standardizing the use of *Globally Unique Identifiers* (or just *GUIDs*) for [[http://www.calacademy.org/research/informatics/sblum/pub/biodiv_informatics.html][Biodiversity Informatics]].
d10 1
a10 2
A *globally unique identifier* is a *permanent identifier* assigned to a *digital resource* (i.e. information) so it can be referenced and later retrieved, regardless of the original location. 
 
d14 1
d23 1
@


1.58
log
@
.
@
text
@d3 1
a3 1
We are researching and standardizing the use of *Globally Unique Identifiers* or *GUIDs* for [[http://www.calacademy.org/research/informatics/sblum/pub/biodiv_informatics.html][Biodiversity Informatics]].
@


1.57
log
@
.
@
text
@d13 1
a13 1
   * [[HowToParticipate][How to participate]]
d23 1
@


1.56
log
@
.
@
text
@d14 1
a14 1
   * [[UsingGUIDWiki] - How to use this wiki (please read before adding new pages)
@


1.55
log
@
.
@
text
@d8 1
a8 1
   * [[GUID1Workshop][GUID-1 Workshop]] - Feb 1-3, 2006 at [[http://www.nescent.org/main/][NESCent]], Durham, NC, USA
@


1.54
log
@
.
@
text
@a7 1

a9 1

a10 1

a18 1

a22 1

@


1.53
log
@
.
@
text
@d7 6
a12 1
---+++ Contents
d17 1
a17 3
   * [[GUID1Workshop][GUID-1 Workshop]] - Feb 1-3, 2006 at [[http://www.nescent.org/main/ NESCent], Durham, NC, USA
   * [[Technologies][GUID Technologies]] - Candidate technologies under evaluation
   * [[Requirements]]
d21 5
a42 4
---+++ Using this Wiki
Please read UsingGUIDWiki for guidance on the use of this Wiki (particularly before adding new pages).

----
@


1.52
log
@
.
@
text
@d16 1
a16 1
   * [[Projects]]
@


1.51
log
@
.
@
text
@a28 18
---+++ How to participate
   1.   Provide input to the survey of requirements through one of the following:
      a.   Add comments or edit pages in this Wiki.
      b.   Subscribe to the mailing list [[TDWG-GUID@@listserv.nhm.ku.edu]] at http://listserv.nhm.ku.edu/archives/tdwg-guid.html - your comments may then be added to the Wiki.

   2.   Your input is particularly sought in the following areas:
      a.   If you are involved in a project that is experimenting with or using a GUID technology ([[LSID]], [[DOI]], etc.), please comment on strengths and weaknesses of the approach and your experience in deploying the solution (see ExistingProjects).
      b.   Describe ways in which GUIDs could be used to solve problems within your area of interest (provide a scenario that describes a problem for which GUIDs may be helpful, see GUIDUseCases).

   3.   Send an expression of interest to participate in the workshops.  Please send such applications to [[guids@@gbif.org]], providing the following information:
      a.   Name and contact details
      b.   Institutional affiliation
      c.   Specific area(s) of interest within biodiversity informatics
      d.   Reasons for interest in participation in GUID standards development
      e.   Would you be able to devote time to web-based discussions as part of a working group between the two workshops?
      f.   Would you require support for travel to attend the workshops?

----
@


1.50
log
@
.
@
text
@d7 1
a7 1
*Quick Links:*
@


1.49
log
@Rearranged the homepage
.
@
text
@d24 1
a25 25
---+++ Background
The Taxonomic Databases Working Group ([[http://www.tdwg.org][TDWG]]) and the Global Biodiversity Information Facility ([[http://www.gbif.org][GBIF]]) have received funding from the Gordon and Betty Moore Foundation ([[http://www.moore.org][GBMF]]) to review requirements for globally unique identifiers (GUIDs) for biodiversity informatics, and to establish infrastructure to support their use.

This review will consider the use of GUIDs across a wide range of application areas and for the benefit of all communities exchanging biodiversity data.  TDWG and GBIF are therefore seeking input from any institutions holding or using data relating to organismal biodiversity (including, but not limited to: natural history museums, herbaria, culture collections, gene banks, zoological and botanical gardens, and biological monitoring projects).

TDWG and GBIF recognise a particular and urgent need for GUIDs to improve exchange of data relating to the following:

   * Specimens
   * Biological collections
   * [[TaxonConcepts][Taxon concepts]]
   * Taxonomic publications 

GUIDs are also likely to prove important for other data items, such as biological images, morphological characters, field observations and ecological experiments.  Such areas will therefore also be considered to ensure that the proposed models and infrastructure are appropriate for wider use.  See GUIDUseCases for examples of how GUIDs may be useful within biodiversity informatics.

Recent discussions have centred on two possible GUID technologies:

   * [[LSID][Life Science Identifiers]] ([[LSID]]s)
   * [[DOI][Digital Object Identifiers]] ([[DOI]]s)

Other potential technologies include [[Handle]]s (which underlie the implementation of [[DOI]]s).  This review is however also open to considering any suitable alternative.  As far as is appropriate, the aim is to establish a common identifier framework for use throughout biodiversity informatics, but a flexible approach may be adopted if some classes of data (e.g. publications) are already supported by suitable models.

The following additional technologies have been suggested during the course of this review:

   * [[ARK][Archival Resource Key]] ([[ARK]]s)

a28 14
---+++ Process
The plan for the review process is as follows:

   * Survey of requirements: open call for input and requirements from all areas of biodiversity informatics, including:
      * Data objects requiring GUIDs (specimens; taxon concepts; publications; etc.)
      * Application scenarios (allocatíng GUIDs; discovering existing GUIDs; resolving GUIDs; etc.)
      * Issues relating to management of GUIDs within distributed databases (avoidance of duplicate GUIDs identifying different objects; handling of multiple GUIDs identifying the same object; persistence of data; etc.)
      * Potential GUID technologies, including advantages and disadvantages of LSIDs and DOIs
   * First workshop (3 days, 1-3 February 2006, at the National Evolutionary Synthesis Center (NESCent), Durham, North Carolina, USA) to review requirements and evaluate candidate technologies, and to establish working groups
   * Working groups to resolve outstanding issues (using mailing lists and/or Wikis to support public discussion) and provide recommendations
   * Second workshop (3 days, mid-2006 - location to be defined) to assess recommendations from working groups and to define models and processes for initial implementation
   * Publication of TDWG standards for GUIDs and initial implementation of any central services or software tools required to support them

----
@


1.48
log
@
.
@
text
@d1 19
a19 1
---++ TDWG Standards Development: Globally Unique Identifiers 
@


1.47
log
@
.
@
text
@d69 1
a69 1
   * [[http://circa.gbif.net/Public/irc/gbif/dadi/library?l=/architecture/globallyuniqueidentifier/_EN_1.0_&a=d][Globally Unique Identifiers for Biodiversity Informatics]] - PowerPoint presentation by Donald Hobern
@


1.46
log
@
.
@
text
@d68 1
a68 1
   * [[http://www.tdwg.org/2004meet/EV/TDWG_2004_Papers_Thau_1.zip][GUIDs and LSIDs]] - PowerPoint presentation by David Thau (TDWG meeting 2004)
@


1.45
log
@
.
@
text
@d32 2
@


1.44
log
@
.
@
text
@d4 1
a4 1
*Welcome to the TDWG Globally Unique Identifiers Wiki.  The following topics have been raised for discussion.  Please provide your comments.*  (See Topics for a full list of topics.)
@


1.43
log
@
.
@
text
@d2 4
a5 1

@


1.42
log
@
.
@
text
@d16 1
a16 1
GUIDs are also likely to prove important for other data items, such as biological images and morphological characters.  Such areas will therefore also be considered to ensure that the proposed models and infrastructure are appropriate for wider use.  See GUIDUseCases for examples of how GUIDs may be useful within biodiversity informatics.
@


1.41
log
@
.
@
text
@d25 4
@


1.40
log
@
.
@
text
@d13 1
a13 1
   * Taxon concepts
@


1.39
log
@
.
@
text
@d43 1
a43 1
      b.   Subscribe to the mailing list TDWG-GUID@@listserv.nhm.ku.edu at http://listserv.nhm.ku.edu/archives/tdwg-guid.html - your comments may then be added to the Wiki.
d49 1
a49 1
   3.   Send an expression of interest to participate in the workshops.  Please send such applications to guids@@gbif.org, providing the following information:
d69 1
a69 1
For further information, please send messages to guids@@gbif.org.
@


1.38
log
@
.
@
text
@d77 1
a77 1
   * Donald Hobern, Programmer Officer for Data Access and Database Interoperability ([[mailto:dhobern@@gbif.org][dhobern@@gbif.org]])
@


1.37
log
@
.
@
text
@d77 1
a77 1
   * Donald Hobern, Programmer Officer for Data Access and Database Interoperability (dhobern@@gbif.org)
@


1.36
log
@
.
@
text
@a71 1

a76 1

@


1.35
log
@
.
@
text
@d68 14
@


1.34
log
@
.
@
text
@d49 1
a49 1
   3.   Send an expression of interest to participate in the workshops.  Please send such applications to guidworkshops@@gbif.org, providing the following information:
@


1.33
log
@
.
@
text
@d27 1
a27 1
The review process will be as follows:
@


1.32
log
@
.
@
text
@d36 1
a36 1
   * Second workshop (3 days, ''Mid 2006'' - ''location to be defined'') to assess recommendations from working groups and to define models and processes for initial implementation
d54 1
a54 1
      e.   Would you be devote time to web-based discussions as part of a working group between the two workshops?
@


1.31
log
@
.
@
text
@d5 1
a5 1
The Taxonomic Databases Working Group ([[http://www.tdwg.org][TDWG]]) and the Global Biodiversity Information Facility ([[http://www.gbif.org][GBIF]]) have received funding from the Gordon and Betty Moore Foundation ([[http://www.moore.org]]) to review requirements for globally unique identifiers (GUIDs) for biodiversity informatics, and to establish infrastructure to support their use.
d34 1
a34 1
   * First workshop (3 days, January or February 2006, at the **National Evolutionary Synthesis Center (NESCent), Durham, North Carolina, USA**) to review requirements and evaluate candidate technologies, and to establish working groups
@


1.30
log
@
.
@
text
@d34 1
a34 1
   * First workshop (3 days, ''January or Febuary 2006'', at the **National Evolutionary Synthesis Center (NESCent), Durham, North Carolina, USA**) to review requirements and evaluate candidate technologies, and to establish working groups
@


1.29
log
@
.
@
text
@d23 1
a23 1
Other potential technologies include [[Handle]]s (which underlie the implementation of [[DOI]]s.  This review is however also open to considering any suitable alternative.  As far as is appropriate, the aim is to establish a common identifier framework for use throughout biodiversity informatics, but a flexible approach may be adopted if some classes of data (e.g. publications) are already supported by suitable models.
@


1.28
log
@
.
@
text
@d34 1
a34 1
   * First workshop (3 days, ''November 2005'', in ''Copenhagen, Denmark'') to review requirements and evaluate candidate technologies, and to establish working groups
d36 1
a36 1
   * Second workshop (3 days, ''March 2006'' in ''Durham, NC, USA'') to assess recommendations from working groups and to define models and processes for initial implementation
@


1.27
log
@
.
@
text
@d16 1
a16 3
GUIDs are also likely to prove important for other data items, such as biological images and morphological characters.  Such areas will therefore also be considered to ensure that the proposed models and infrastructure are appropriate for wider use.

See GUIDUseCases for examples of how GUIDs may be useful within biodiversity informatics.
d23 1
a23 5
Other potential technologies include:

   * [[Handle]]s (which underlie the implementation of [[DOI]]s

This review is however also open to considering other alternatives.  As far as is appropriate, the aim is to establish a common identifier framework for use throughout biodiversity informatics, but a flexible approach may be adopted if some classes of data (e.g. publications) are already supported by suitable models.
d34 1
a34 1
   * First workshop (3 days, ''August 2005'', in ''Copenhagen, Denmark'') to review requirements and evaluate candidate technologies, and to establish working groups
d36 1
a36 1
   * Second workshop (3 days, December 2005) to assess recommendations from working groups and to define models and processes for initial implementation
a39 6
---+++ Documents
   * [[http://www.tdwg.org/2004meet/EV/TDWG_2004_Papers_Thau_1.zip][GUIDs and LSIDs]] - PowerPoint presentation by David Thau (TDWG meeting 2004)
   * [[http://circa.gbif.net/Public/irc/gbif/dadi/library?l=/architecture/globallyuniqueidentifier/_EN_1.0_&a=d][Globally Unique Identifiers for Biodiversity Informatics]] - PowerPoint presentation by Donald Hobern
   * [[http://wiki.gbif.org/dadiwiki/wikka.php?wakka=DPSGloballyUniqueIdentifierServices][GBIF GUID Services Strategy]] - outline plan for development of GBIF GUID services from [[http://circa.gbif.net/Public/irc/gbif/dadi/library?l=/architecture/portal_strategy_1/][GBIF Data Portal Strategy]]
  
----
a41 1

a43 2
      c.   If you are involved in a project that is experimenting with or using a GUID technology, please comment on strengths and weaknesses of the approach and your experience in deploying the solution.
      d.   Describe ways in which GUIDs could be used to solve problems within your area of interest (provide a scenario that describes a problem for which GUIDs may be helpful, see GUIDUseCases).
d45 5
a49 1
   2.   Send an expression of interest to participate in the workshops.  Please send such applications to guidworkshops@@gbif.org, providing the following information:
d58 6
@


1.26
log
@
.
@
text
@d54 3
a56 2
      a.   Subscribe to the mailing list TDWG-GUID@@listserv.nhm.ku.edu at http://listserv.nhm.ku.edu/archives/tdwg-guid.html
      b.   Add comments or edit pages in this Wiki.
d58 1
a58 1
      d.   Describe ways in which GUIDs could be used to solve problems within your area of interest (provide a scenario that describes a problem for which GUIDs may be helpful).
@


1.25
log
@
.
@
text
@d47 2
a48 1
   * [[http://circa.gbif.net/Public/irc/gbif/dadi/library?l=/architecture/globallyuniqueidentifier/_EN_1.0_&a=d][Globally Unique Identifiers for Biodiversity Informatics]] - PowerPoint) presentation from TDWG meeting 2004
@


1.24
log
@
.
@
text
@d47 2
a48 2
[[http://circa.gbif.net/Public/irc/gbif/dadi/library?l=/architecture/globallyuniqueidentifier/_EN_1.0_&a=d][Globally Unique Identifiers for Biodiversity Informatics (PowerPoint)]]
[[http://wiki.gbif.org/dadiwiki/wikka.php?wakka=DPSGloballyUniqueIdentifierServices][GBIF GUID Services Strategy]] - outline plan for development of GBIF GUID services from [[http://circa.gbif.net/Public/irc/gbif/dadi/library?l=/architecture/portal_strategy_1/][GBIF Data Portal Strategy]]
@


1.23
log
@
.
@
text
@d46 1
a46 3
---+++ Documents---++++ =Globally Unique Identifier Services=

---++++ Documents
@


1.22
log
@
.
@
text
@d46 7
@


1.21
log
@
.
@
text
@d18 3
a20 1
Recent discussions have centred on two possible technologies:
d50 2
d53 1
a53 1
   2.   Send an expression of interest to participate in the workshops.  Please send such applications to ''whoever[AT]wherever.org'', providing the following information:
@


1.20
log
@
.
@
text
@d46 1
a46 2
      a.   Subscribe to the mailing list TDWG-GUID@@listserv.nhm.ku.edu by sending a message to listserv@@listserv.nhm.ku.edu with the following command in the body of the message (using your name):
      %%(email) SUBSCRIBE TDWG-GUID Firstname Lastname%%
@


1.19
log
@
.
@
text
@d46 2
a47 1
      a.   Subscribe to the mailing list ''tdwg_guids[AT]wherever.org'' by sending a message to ''tdwg_guids_admin[AT]wherever.org''.
@


1.18
log
@
.
@
text
@d23 4
@


1.17
log
@
.
@
text
@d21 1
a21 1
   * Digital Object Identifiers (DOIs), [[http://www.doi.org/]] (or more generally Handles, [[http://www.handle.net/]]) 
@


1.16
log
@
.
@
text
@d20 1
a20 1
   * Life Science Identifiers (LSIDs), [[http://lsid.sourceforge.net/]]
@


1.15
log
@
.
@
text
@d34 1
a34 1
   * First workshop (3 days, August 2005, in Copenhagen, Denmark) to review requirements and evaluate candidate technologies, and to establish working groups
d42 1
a42 1
      a.   Subscribe to the mailing list tdwg_guids[AT]wherever.org by sending a message to tdwg_guids_admin[AT]wherever.org.
d45 1
a45 1
   2.   Send an expression of interest to participate in the workshops.  Please send such applications to whoever[AT]wherever.org, providing the following information:
@


1.14
log
@
.
@
text
@d55 1
a55 1
Please read UsingGUIDWiki for guidance on the use of this Wiki (particularly before adding new pages) and on the use of Categories to classify pages.
@


1.13
log
@
.
@
text
@d7 1
a7 1
This review will consider the use of GUIDs across a wide range of application areas and for the benefit of all communities exchanging biodiversity data.  TDWG and GBIF are therefore seeking input from any institutions holding or using data relating to organismal biodiversity (including, but not limited to: natural history museums, herbaria, culture collections, zoological and botanical gardens, biological monitoring projects, others).
@


1.12
log
@
.
@
text
@d57 1
@


1.11
log
@
.
@
text
@a2 1

d4 1
a4 1
---++++ Background
d26 1
a26 1
---++++ Process
d40 1
a40 1
---++++ How to participate
d54 1
a54 1
---++++ Using this Wiki
@


1.10
log
@
.
@
text
@d3 2
d26 1
d40 1
d54 1
@


1.9
log
@
.
@
text
@d3 1
a3 1
---+++++ Background
d24 1
a24 1
---+++++ Process
d37 1
a37 1
---+++++ How to participate
d50 5
a54 1
Useful pages: FormattingRules, WikkaDocumentation, OrphanedPages, WantedPages, TextSearch.@


1.8
log
@
.
@
text
@d9 1
d18 1
d26 1
d41 1
@


1.7
log
@
.
@
text
@d35 10
a44 10
1.   Provide input to the survey of requirements through one of the following:
   a.   Subscribe to the mailing list tdwg_guids[AT]wherever.org by sending a message to tdwg_guids_admin[AT]wherever.org.
   b.   Add comments or edit pages in this Wiki.
2.   Send an expression of interest to participate in the workshops.  Please send such applications to whoever[AT]wherever.org, providing the following information:
   a.   Name and contact details
   b.   Institutional affiliation
   c.   Specific area(s) of interest within biodiversity informatics
   d.   Reasons for interest in participation in GUID standards development
   e.   Would you be devote time to web-based discussions as part of a working group between the two workshops?
   f.   Would you require support for travel to attend the workshops?
@


1.6
log
@
.
@
text
@d35 10
a44 10
   1.   Provide input to the survey of requirements through one of the following:
      a.   Subscribe to the mailing list tdwg_guids[AT]wherever.org by sending a message to tdwg_guids_admin[AT]wherever.org.
      b.   Add comments or edit pages in this Wiki.
   2.   Send an expression of interest to participate in the workshops.  Please send such applications to whoever[AT]wherever.org, providing the following information:
      a.   Name and contact details
      b.   Institutional affiliation
      c.   Specific area(s) of interest within biodiversity informatics
      d.   Reasons for interest in participation in GUID standards development
      e.   Would you be devote time to web-based discussions as part of a working group between the two workshops?
      f.   Would you require support for travel to attend the workshops?
@


1.5
log
@
.
@
text
@a24 1

@


1.4
log
@
.
@
text
@a8 1

a16 1

a23 1

a29 1

a30 1

a31 1

a32 1

a38 1
   
@


1.3
log
@
.
@
text
@a43 1
   
a47 1
   
@


1.2
log
@
.
@
text
@d46 1
a46 1
      b.   Add comments or edit pages at the TDWG GUID Wiki: http_//wherever.
@


1.1
log
@Initial revision
@
text
@d1 1
a1 1
---++ Welcome to your Wikka site! 
d3 2
a4 2
Thanks for installing [[Wikka:HomePage][WikkaWiki]]! This site is running on version {{wikkaversion}} (see WikkaReleaseNotes). 
Double-click on this page or click on the "Edit page" link at the bottom to get started. 
d6 50
a55 1
Also don't forget to visit the [[Wikka:HomePage][WikkaWiki website]]! 
@