steve
/
wiki-archive
mirror of https://github.com/tdwg/wiki-archive.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
wiki-archive/twiki/data/GUID/AbfLsidMeetingMinutes.txt,v

1046 lines
39 KiB
Plaintext
Raw Normal View History

Archive entire twiki setup from owl as of today
2016-02-24 10:46:01 +00:00
head 1.27;
access;
symbols;
locks; strict;
comment @# @;
1.27
date 2007.04.28.06.02.22; author AlexChapman; state Exp;
branches;
next 1.26;
1.26
date 2007.04.12.02.13.06; author BenRichardson; state Exp;
branches;
next 1.25;
1.25
date 2007.04.11.16.57.50; author AlexChapman; state Exp;
branches;
next 1.24;
1.24
date 2007.04.11.08.30.35; author AlexChapman; state Exp;
branches;
next 1.23;
1.23
date 2007.04.04.04.43.25; author JimCroft; state Exp;
branches;
next 1.22;
1.22
date 2007.04.04.04.41.01; author PiersHiggs; state Exp;
branches;
next 1.21;
1.21
date 2007.04.04.04.37.19; author AlexChapman; state Exp;
branches;
next 1.20;
1.20
date 2007.04.04.02.39.54; author BenRichardson; state Exp;
branches;
next 1.19;
1.19
date 2007.04.04.01.48.46; author AlexChapman; state Exp;
branches;
next 1.18;
1.18
date 2007.04.04.01.23.20; author PiersHiggs; state Exp;
branches;
next 1.17;
1.17
date 2007.04.04.01.04.11; author AlexChapman; state Exp;
branches;
next 1.16;
1.16
date 2007.04.04.00.25.46; author PiersHiggs; state Exp;
branches;
next 1.15;
1.15
date 2007.04.03.23.20.58; author BenRichardson; state Exp;
branches;
next 1.14;
1.14
date 2007.04.03.07.01.26; author BenRichardson; state Exp;
branches;
next 1.13;
1.13
date 2007.04.03.03.23.38; author RicardoPereira; state Exp;
branches;
next 1.12;
1.12
date 2007.04.03.02.45.26; author BenRichardson; state Exp;
branches;
next 1.11;
1.11
date 2007.04.02.23.28.09; author RicardoPereira; state Exp;
branches;
next 1.10;
1.10
date 2007.04.02.23.27.43; author BenRichardson; state Exp;
branches;
next 1.9;
1.9
date 2007.04.02.07.02.06; author BenRichardson; state Exp;
branches;
next 1.8;
1.8
date 2007.04.02.06.32.53; author KevinRichards; state Exp;
branches;
next 1.7;
1.7
date 2007.04.02.06.31.39; author BenRichardson; state Exp;
branches;
next 1.6;
1.6
date 2007.04.02.03.58.35; author RicardoPereira; state Exp;
branches;
next 1.5;
1.5
date 2007.04.02.03.54.50; author BenRichardson; state Exp;
branches;
next 1.4;
1.4
date 2007.04.02.02.39.16; author RicardoPereira; state Exp;
branches;
next 1.3;
1.3
date 2007.04.02.02.25.49; author BenRichardson; state Exp;
branches;
next 1.2;
1.2
date 2007.04.02.02.13.18; author PiersHiggs; state Exp;
branches;
next 1.1;
1.1
date 2007.04.02.01.38.32; author BenRichardson; state Exp;
branches;
next ;
desc
@none
@
1.27
log
@none
@
text
@%META:TOPICINFO{author="AlexChapman" date="1177740142" format="1.1" reprev="1.27" version="1.27"}%
%META:TOPICPARENT{name="AbfLsidPolicyCanberraMeeting2007Preparation"}%
---+!! Meeting Minutes -- An LSID Policy for the Australasian Biodiversity Federation
%TOC%
---++ Meeting Participants
* [[Main.BillBarker][Bill Barker]] (State Herbarium of South Australia; Department of Environment and Heritage; Adelaide)
* [[Main.LeeBelbin][Lee Belbin]] (TDWG Infrastructure Project)
* [[Main.PaulCoddington][Paul Coddington]] (South Australian Partnership for Advanced Computing; The University of Adelaide; Adelaide)
* [[Main.JimCroft][Jim Croft]] (Australian National Herbarium; Centre for Plant Biodiversity Research; Canberra)
* [[Main.AlexChapman][Alex Chapman]] (Western Australian Herbarium; Department of Environment and Conservation; Perth)
* [[Main.PaulFlemons][Paul Flemons]] (Australian Museum; Department of Communications, Information Technology and the Arts; Sydney)
* [[Main.PiersHiggs][Piers Higgs]] (Gaia Resources - representing Western Australian Museum; Department of Culture & the Arts; Perth)
* [[Main.RobynLawrence][Robyn Lawrence]] (Australian Biological Resources Study; Department of the Environment and Water Resources; Canberra)
* [[Main.RobertMorris][Robert Morris]] (South Australian Museum; Adelaide)
* [[Main.PeterNeish][Peter Neish]] (National Herbarium of Victoria; Royal Botanic Gardens Melbourne; Melbourne)
* [[Main.LaurencePaine][Laurence Paine]] (Manager Information Technology; Department of Tourism, Arts and the Environment; Hobart)
* [[Main.RicardoPereira][Ricardo Pereira]] (TDWG Infrastructure Project; Campinas; Brazil)
* [[Main.RobertRaven][Robert Raven]] (Queensland Museum; Department of Education, Training and the Arts)
* [[Main.KevinRichards][Kevin Richards]] (Allan Herbarium; Manaaki Whenua - Landcare Research; Christchurch)
* [[Main.BenRichardson][Ben Richardson]] (Western Australian Herbarium; Department of Environment and Conservation; Perth)
* [[Main.DanRosauer][Dan Rosauer]] (Department of the Environment and Water Resources; Canberra)
* [[Main.SteveShattuck][Steve Shattuck]] (Australian Biological Resources Study; Department of the Environment and Water Resources; Canberra)
* [[Main.CameronSlatyer][Cameron Slatyer]] (Australian Biological Resources Study; Department of the Environment and Water Resources; Canberra)
* [[Main.KevinThiele][Kevin Thiele]] (Western Australian Herbarium; Department of Environment and Conservation; Perth)
* [[Main.JeffTranter][Jeff Tranter]] (Environmental Resources Information Network; Department of the Environment and Water Resources; Canberra)
* [[Main.AaronWilton][Aaron Wilton]] (Allan Herbarium; Manaaki Whenua - Landcare Research; Christchurch)
* [[Main.GregWhitbread][Greg Whitbread]] (Australian National Herbarium; Centre for Plant Biodiversity Research; Canberra)
---++ Introduction
This meeting was convened to write an [[AustralasianBiodiversityFederationLsidPolicy][LSID Policy for the Australasian Biodiversity Federation]] and to use that policy to inform future LSID implementation policies globally. Jim Croft welcomed the participants to the meeting.
---++ Monday 2 April 2007
---+++ Life Science Identifiers and the TDWG Architecture
Ricardo Pereira ([[%ATTACHURL%/TDWG_Architecture.ppt][TDWG_Architecture.ppt]]) introduced the Life Science Identifiers architecture as being developed by TDWG.
LSIDs should provide:
* Truly distributed environment
* Identification of duplicates
* Annotation
* Determination of source
All three parts of the architecture are required:
1. Core Ontology
1. Globally Unique Identifiers
1. Exchange Protocols
LSIDs can be made to play nice with HTTP-based Semantic Web applications.
---+++ Introduction to LSIDs
Kevin Richards ([[%ATTACHURL%/LSIDs.ppt][LSIDs.ppt]]) introduced LSIDs, including the presentation of a background on GUIDs in general, e.g. UUID, DOI, Handles, LSIDs and PURLs.
* IBM implementation team has found that the use of the Revision-ID part of the LSID URN would be better implemented by creating a new LSID for a new revision and pointing to an old LSID
* In the biodiversity world, most "data" is metadata in the LSID framework
The [[http://sourceforge.net/projects/lsid][Firefox LSID Browser]] can be used to resolve LSIDs directly in the Firefox toolbar using the =lsidres= protocol prefix. For example: lsidres:urn:lsid:ubio.org:namebank:11815 (taken from http://lsid.tdwg.org/). (Download both [[http://sourceforge.net/project/showfiles.php?group_id=130827&package_id=169527][the XPI file]] and [[http://jslib.mozdev.org/installation.html][JSLib]] to get this to work.)
---+++ Discussion of the First Two Presentations
Reading suggestion by Lee Belbin: [[http://dx.doi.org/doi:10.1080/10635150500541680][D.J. Patterson, D. Remsen, W.A. Marino & C. Norton (2006) Taxonomic Indexing--Extending the Role of Taxonomy. Syst. Biol. 55(3):367-373]].
---++++ What Do LSIDs Look Like?
=urn:lsid:Authority:Namespace:Identifier=
See (and use) more examples at http://lsid.tdwg.org/.
---++++ What is the Difference between a URN and a URI (and a URL)?
URLs tend to be used in today's Internet usage, but URNs are more commonly used in the [[http://en.wikipedia.org/wiki/Semantic_Web][Semantic Web]].
---++++ Other
* Data versus Metadata
* Duplicate specimen versus duplicate LSID (different meaning for the same term)
* [[TdwgLsidApplicabilityStatement][TDWG LSID Applicability Statement]]
---+++ What Are We Here For?
* The idea was to come up with policy recommendations in our domain
* Why do we need a policy? Couldn't we just start implementing LSIDs in our institutions?
* What can't we do at the moment, or what would be more efficient in the LSID approach?
* What should the policy contain?
* Are we the right group to create a policy? Perhaps a set of recommendations is better?
Document Audience:
* Australian Biodiversity Information Facility (ABIF)
* Atlas of Living Australia Committee (ALA)
* Council of Heads of Australian Entomological Collections (CHAEC)
* Council of Heads of Australian Faunal Collections (CHAFC)
* Council of Heads of Australasian Herbaria (CHAH)
* E-paedia of Life (EOL)
* New Zealand National Herbarium Network (NZNHN)
* Biodiversity Information Standards (TDWG)
---+++ Map for Tuesday 3 April
http://www.anbg.gov.au/images/BG.mapscan/BG.mapscan.B.html
The Crossbie Morrison Building is in the top right corner of the above map.
---++ Tuesday 3 April 2007
---+++ Recap of Monday
LSIDs as adopted by TDWG is considered the right way to go, and we're planning to adopt this technology in Australia. How we do this, and the timeline for doing this is the subject of today's meeting. There needs to be as little need for rewriting databases and applications as possible. TDWG has spent some time determining the right way forward for GUIDs, including evaluating the other technologies and have chosen LSIDs based on that. DOIs and Handles would still be used (that is LSIDs aren't considered replacements for these) in the biodiversity data community.
---+++ Tuesday's Outline
Greg Whitbread outlined the proposed business for today and requested feedback on the order and type of sessions. Some time was spent discussing how LSIDs might be applied in cases raised by individual participants.
* What objects would we apply LSIDs to?
* There are a number of places in which LSIDs might be useful, but in order to link to other disparate databases, we need to put LSIDs on the same things
* On another level, what's in the metadata?
* A core [[http://en.wiktionary.org/wiki/ontology][ontology]] was developed (see [[TAG.LsidVocs][TDWG LSID Vocabulary]]) by the lead developers of the original TDWG standards to try and bring them closer together. This might be the basic set of objects to which LSIDs should be assigned.
---+++ What do we want?
What is the minimum set of core ontology objects that we all agree we should share? This might be the minimum set of things that need an LSID. Our domain contains the following:
* Lots (e.g. a jar of ants)
* Specimens
* Observations
* Names
* Taxa (Concepts)
* Places
* People
* Publications / Literature References
* Multimedia (Images, Audio, Video)
* Descriptions (of taxa)
* Keys
* Characters
* States
* Phylogenies
* Clades
* Vegetation Types
* Institutions (Herbaria, Museums)
* Collections (Assemblages)
* IP/Copyright
It shouldn't be assumed that these must all be implemented, just that they fall within our domain and we _may_ need to apply LSIDs to these at some point in future. The [[TAG.LsidVocs][TDWG LSID Vocabulary]] does not contain Descriptions, Multimedia, Places, Keys, Characters, States, Phylogenies, Clades or Vegetation Types which means we've defined a slightly wider core that the current core provides.
Names, Taxa (Concepts), Specimens, Multimedia (i.e. Images) and Descriptions were mentioned as a most likely initial set for participants to start implementing LSIDs for in their institutions.
---+++ Encyclopaedia of Life
David J. (Paddy) Patterson presented the [[http://www.eolproject.info/][Encyclopaedia of Life]] project. E.O. Wilson is thought to have been the instigator of the idea. On 9 May, funding will be made available to build the EOL. The funding is thought to be around US$40 million. Five cornerstone institutions (Smithsonian Institution, Field Museum of Natural History (Chicago), Harvard University, Woods Hole Marine Biological Laboratory, and the Biodiversity Heritage Library) are involved. It aims to be a communal project that serves any kind of audience.
Three page types:
* Front page
* For every species, a relatively static species page
* What's behind the front page for each species (dynamically created) -- a community environment.
EOL is using Names (9.5 million), Name Surrogates (labels attached to other objects) and Concepts. They will use the major nomenclator tools to get access to names. Misspellings, homonyms, and other duplication problems are addressed by taxonomic problem tools. Phylogenies, apomorphies and classifications are collected so they can be navigated. "Union" aims to put all these things into one classification hierarchy so problems with these can be resolved. The "Workbench" will have a need for LSIDs. Flickr, Google, del.icio.us and others will be getting involved. There is a duality in the "Workbench", there are web pages to deliver and there are also tools intended for public ownership.
---+++ Practice
* TAPIR.TapirLink contains an LSID resolver
---+++ Architecture
* LSID resolution should be done by the Data Provider
---++ Wednesday 4 April 2007
---+++ Review
Recommendations need to be less technical, fewer in number and targetting each level of an institution who might consider implementing LSIDs. The audience might comprise:
* Executive -- summary, costs, workload
* Technical -- revisit draft recommendations
* Implementation prerequisites -- technology needed from TDWG before LSIDs can be implemented fully
---+++ Draft Recommendations
1. LSIDs will be applied to the core (optimum set) of data objects
* Now
1. Specimens
1. Names
1. Taxa
1. Descriptions
1. Images
* Soon
* Later
1. [[TAG.LsidVocs][Core Ontology]]
* As funding becomes available
1. Data objects will "wear" their LSIDs (but for the interim, don't actually resolve them)
1. LSIDs will be resolvable
1. Data custodians will be responsible for LSID assignment
1. LSIDs will be treated as opaque (because this avoids problems where people start guessing at the significance of the components of your LSID URN)
1. Follow best practice in the creation of LSIDs to increase their longevity (aka LSID Guide for Dummies) -- this is being developed as part of the [[LSIDRoadmapOct2006][LSID Roadmap]]
1. Institution independent domain names should be used in the Authority. This should be a best-guess at a stable domain name
1. [[http://www-128.ibm.com/developerworks/opensource/library/os-lsidbp/][LSID Best Practices]]
1. Relationships within or between data objects will be exposed using LSIDs
We need to make sure that in our databases, where we have locally unique IDs, that they must contain no semantic content, otherwise they cannot be used as LSIDs. (This is effectively the same as saying "LSIDs will be opaque".) Additionally, if it is important in your domain, you should be tracking the relationships between your objects. An example would be when a single specimen (such as an alga, or a bird) is found to contain another specimen or specimens, those related specimens (epiphytes or parasites) are separated into two (or more) specimens.
Further recommendation: Where institutions are maintaining the relationship between data objects, that these relationships should be exposed as LSIDs. Additionally, where institutions are atomising data, those atomised blocks should be exposed as LSIDs.
Five institutions are exposing taxon descriptions, these could be given LSIDs as a test case. The term "Description" should not be confused. A Description is a block of text describing a lifeform, versus a Taxon Profile, which contains a Description plus the associated photos, maps and other content.
---+++ Breakout Group: Executive
[[AbfLsidMeetingExecSummary][Beginnings of an executive backgrounder and summary]]
---+++ Breakout Group: Implementation
1. Establish indicative generic processes
* use TDWG guidelines; alternative paths for assigning LSID's
* plans
* costs
1. Obtain commitment and funding
* institutional
* external projects (eg. ALA)
1. Apply LSID's to databases
* according to one of the identified paths
1. Install and configure Resolvers
* makes LSID's visible for exploration, retrieval, harvesting
1. Educate consumers and potential implementers via:
* TDWG Technical web site
* TWDG general language explanation of LSID's
* domain or institution-specific 'dummies guides'
* an outreach program to identify and 'recruit' data sources to using LSID's
1. Support
* TDWG 'Help Desk'
* web-based community forums
* onsite 'SWAT' teams of local experts
1. Data Use Agreements
* develop - include 'wearability' of the LSID
* apply
1. Keep up to date
* maintain your feed
* participate in standards bodies
* provide feedback for refining/extending vocabularies and ontologies
---+++ Breakout Group: Technical
As data custodians in federated information systems:
* We need to use GUIDs when sharing data
* We need to move to true GUIDS and will use LSIDs
* LSIDs use TDWG standards which will guarantee uniqueness using the format =urn:lsid:Authority:Namespace:Identifier=
* We will reference a range of best practice documents to support LSID Implementation, including
* [[http://wiki.gbif.org/guidwiki/wikka.php?wakka=TdwgLsidApplicabilityStatement][TDWG LSID Applicability Statement]]
* [[http://www-128.ibm.com/developerworks/opensource/library/os-lsidbp/][LSID Best Practices]]
* Proposed "LSID for Dummies" document will also refer to best practice (being written by Ricardo)
* The Authority component should be a domain name under control of the data provider
* We will actively participate in the development of TDWG Ontology, Protocols and GUIDs (the three legs of the stool in the TDWG documentation, see Ricardo's Powerpoint [[%ATTACHURL%/TDWG_Architecture.ppt][TDWG_Architecture.ppt]])
* We will use the available tools to implement TDWG standards, such as pywrapper and TAPIRlink
* We will treat LSIDs as opaque (because this avoids problems where people start guessing at the significance of the components of your LSID URN)
* We will ensure that data objects will always include their LSID (data objects need to have the LSIDs stored with them, and it should remain with them at all times)
* We will apply LSIDs to the "core set" of data objects using LSID vocabularies:
* Specimens - some organisations and projects are currently sharing these now, but moving to a GUID standard - LSIDs - is important for globally sharing the data objects (TDWG vocabulary exists - TAG.SpecimenLsidVoc)
* Names - some organisations are currently sharing these now, but LSIDs will enable linkages and meet the current demands of name resolution nationally and globally (TDWG vocabulary exists - TAG.TaxonNameLsidVoc)
* Concepts - because we can't share concepts now (locally or globally), LSIDs will help us to do this (although we have undertake both philosophical and technical upgrades of our own thinking/systems to enable this) - TDWG vocabulary exists - TAG.TaxonConceptLsidVoc
* Descriptions - projects such as ALA and ABIF would like us to deliver descriptions, and LSIDs will enable us to do this (globally) - no vocabulary developed yet by TDWG
* Images - again, projects will also require images, and again LSIDs will enable us to do this (globally) - no vocabulary developed yet by TDWG
* We will work towards applying LSIDs to the remaining objects identified (the "optimum set") and will assist in the development of LSID Vocabularies:
* Lots
* Observations
* Places
* People
* Publications / Literature References
* Keys
* Characters
* States
* Phylogenies
* Clades
* Vegetation Types
* Institutions (Herbaria, Museums)
* Collections (Assemblages)
* IP/Copyright
* We, as Data custodians, will be responsible for LSID assignment
* We will ensure that all LSIDs will be resolvable
* We recommend that data custodians/providers should also be LSID resolvers, but LSID resolvers may also be provided by other organisations/projects (eg. AVH, TDWG)
* We will expose relationships within or between data objects using LSIDs
* We recommend that TDWG generates some tools for managing and reporting upon the development of particular vocabularies and tools to the wider community
---+++ Proposed Roadmap
A draft set of goals and milestones was identified by the workshop participants.
| *Task* | *Description* | *Date* |
| |Policy recommendations completed and circulated to the management committees|May 2007|
| |Recommendation to CHAH/CHAFC to formalize high level collaboration|May 2007|
| |Setup TDWG Oceania Interest Group - OIG |May 2007|
| |Ratification by CHAH, CHAFC at next quarterly meetings|June 2007|
| |Report and covering letter from these two groups to ALA Steering Committee|July 2007|
| |Formalize collaboration between HISCOM and CHAFC equivalent - consider ad hoc issue specific meetings|July 2007|
| |OIG group meet (workshop or e-conference) to handle regional issues outside the remit of the current project-focussed groups|July 2007|
| |TAPIRLink Resolver release (some data services reliant upon this)|July 2007|
| |Project management tools adopted -- TDWG wiki, Issue tracking| August 2007|
| |Implementation Planning -- Approved recommendations implemented -- in time for TDWG meeting|August 2007|
| |NZ Landcare (names, concepts, references) data |available now|
| |CANB data available - will include names, taxa, specimens, images|June 2007|
| |ABRS data available|September 2007|
| |Progress reports to CHAH, CHAFC, TDWG|September 2007|
| |TDWG 2007 - demonstration of LSID's to include Australian data|September 2007|
| |ALA prototype project from partnership with 'early adopters'|October 2007|
| | |
---++ Meeting close
Ranks thinned after lunch and at 3pm participants thanked the hosts and organisers for their efforts and hospitality and looked forward to further collaboration in coming months.
%META:FILEATTACHMENT{name="LSIDs.ppt" attachment="LSIDs.ppt" attr="" comment="LSID presentation" date="1175495572" path="C:\TDWG\LSIDs.ppt" size="91136" stream="C:\TDWG\LSIDs.ppt" user="Main.KevinRichards" version="1"}%
%META:FILEATTACHMENT{name="TDWG_Architecture.ppt" attachment="TDWG_Architecture.ppt" attr="" comment="TDWG Architecture Presentation" date="1175570555" path="TDWG_Architecture.ppt" size="590336" stream="TDWG_Architecture.ppt" user="Main.RicardoPereira" version="1"}%
@
1.26
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BenRichardson" date="1176343986" format="1.1" version="1.26"}%
d109 1
a109 1
The Crosby Morrison Building is in the top right corner of the above map.
d294 2
a295 2
| |Policy recommendations completed and circulated to the management committees|20 April 2007|
| |Recommendation to CHAH/CHAFC to formalize high level collaboration||
@
1.25
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="AlexChapman" date="1176310670" format="1.1" reprev="1.25" version="1.25"}%
d64 1
a64 1
The [[http://sourceforge.net/projects/lsid][Firefox LSID Browser]] can be used to resolve LSIDs directly in the Firefox toolbar using the =lsidres= protocol prefix. For example: lsidres:urn:lsid:ubio.org:namebank:11815 (taken from http://lsid.tdwg.org/). (Download both [[http://sourceforge.net/project/showfiles.php?group_id=130827&package_id=169527][the XPI file] and [[http://jslib.mozdev.org/installation.html][JSLib]] to get this to work.)
@
1.24
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="AlexChapman" date="1176280235" format="1.1" version="1.24"}%
d156 1
a156 1
David J. (Paddy) Patterson presented the [[http://www.eolproject.info/][Encyclopaedia of Life]] project. E.O. Wilson is thought to have been the instigator of the idea. On 9 May, funding will be made available to build the EOL. The funding is thought to be around US$40 million. Five cornerstone institutions (Smithsonian Institution, Field Museum of Natural History (Chicago), Harvard University, Marine Biological Laboratory, and Biodiversity Heritage Library) are involved. It aims to be a communal project that serves any kind of audience.
d162 1
a162 1
* What's behind the front page for each species (dynamically created) -- a community environment
d182 1
a182 1
* Prerequisites -- technology needed from TDWG before LSIDs can be implemented fully
d216 30
d289 3
a291 1
---+++ Breakout Group: Implementation
d293 2
a294 41
1. Establish indicative generic processes
* use TDWG guidelines; alternative paths for assigning LSID's
* plans
* costs
2. Obtain commitment and funding
* institutional
* external projects (eg. ALA)
3. Apply LSID's to databases
* according to one of the identified paths
4. Install and configure Resolvers
* makes LSID's visible for exploration, retrieval, harvesting
5. Educate consumers and potential implementers via:
* TDWG Technical web site
* TWDG general language explanation of LSID's
* domain or institution-specific 'dummies guides'
* an outreach program to identify and 'recruit' data sources to using LSID's
6. Support
* TDWG 'Help Desk'
* web-based community forums
* onsite 'SWAT' teams of local experts
7. Data Use Agreements
* develop - include 'wearability' of the LSID
* apply
8. Keep up to date
* maintain your feed
* participate in standards bodies
* provide feedback for refining/extending vocabularies and ontologies
---+++ Roadmap
| |Policy recommendations will be completed and circulated to the management committees noted earlier |20 April 2007|
| |Ratification by CHAH, CHAFC at next quarterly meetings||
| |Report and covering letter from these two groups to ALA Steering Committee||
| |Setup TDWG Oceania Interest Group - OIG |4 May 2007|
d296 8
a303 4
| |Formalize collaboration between HISCOM and CHAFC equivalent - consider ad hoc issue specific meetings||
| |Implementation Planning -- Approved recommendations implemented |31 August (in time for TDWG 2007)|
| |OIG group meet on an as-needs basis to handle regional issues outside the remit of the current project-focussed groups||
| |Project Management tools -- TDWG wiki (now); Issue tracking (later)
d305 2
a306 4
| |CANB data available|1 June 2007|
|^|will include names, taxa, specimens, images|^|
| |ABRS data available|21 September 2007|
| |TAPIRLink Resolver release (some data services reliant upon this)|? 1 June 2007|
d309 1
a309 1
| |ALA prototype project from partnership with 'early adopters'|?October 2007|
d312 2
a313 19
Previously:
* Policy recommendations will be completed and circulated to the management committees noted earlier (two weeks)
* Ratification by CHAH, CHAFC at next quarterly meetings
* Report and covering letter from these two groups to ALA Steering Committee
* Setup TDWG Oceania Interest Group - OIG (4 weeks)
* Recommendation to CHAH/CHAFC to formalize high level collaboration
* Formalize collaboration between HISCOM and CHAFC equivalent - consider ad hoc issue specific meetings
* Implementation Planning -- Approved recommendations implemented by the end of August (in time for TDWG 2007)
* OIG group meet on an as-needs basis to handle regional issues outside the remit of the current project-focussed groups.
* Project Management tools -- TDWG wiki (now); Issue tracking (later)
* NZ Landcare (names, concepts, references) data available now
* CANB data available (8 weeks)
* will include names, taxa, specimens, images
* ABRS data available (16 weeks)
* TAPIRLink Resolver release (some data services reliant upon this)
* Progress reports to CHAH, CHAFC, TDWG
* TDWG 2007 - demonstration of LSID's to include Australian data
* ALA prototype project from partnership with 'early adopters'
@
1.23
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="JimCroft" date="1175661805" format="1.1" version="1.23"}%
d298 20
@
1.22
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="PiersHiggs" date="1175661661" format="1.1" version="1.22"}%
d302 2
d309 1
@
1.21
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="AlexChapman" date="1175661439" format="1.1" reprev="1.21" version="1.21"}%
d299 3
a301 3
* ratification by CHAH, CHAFC at next quarterly meetings
* report and covering letter from these two groups to ALA Steering Committee
* setup TDWG Oceania Interest Group - OIG (4 weeks)
d308 1
a308 1
* TAPIR release
@
1.20
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BenRichardson" date="1175654394" format="1.1" reprev="1.20" version="1.20"}%
d298 4
a301 1
* Policy recommendations will be completed in two weeks and circulated to the management committees noted earlier
d303 1
a303 1
* New Ad-hoc Meetings -- The TDWG Oceania Secretary (Alex Chapman) could convene a new group that met on an ad-hoc basis to handle regional issues outside the remit of the current project-focussed groups. This could be formulated as a TDWG Interest Group.
d305 8
@
1.19
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="AlexChapman" date="1175651326" format="1.1" version="1.19"}%
d233 3
a235 3
* Specimens - some organisations and projects are currently sharing these now, but moving to a GUID standard - LSIDs - is important for globally sharing the data objects (TDWG vocabulary exists - SpecimenLSIDVoc)
* Names - some organisations are currently sharing these now, but LSIDs will enable linkages and meet the current demands of name resolution nationally and globally (TDWG vocabulary exists - TaxonNameLSIDVoc)
* Concepts - because we can't share concepts now (locally or globally), LSIDs will help us to do this (although we have undertake both philosophical and technical upgrades of our own thinking/systems to enable this) - TDWG vocabulary exists - TaxonConceptLSIDVoc
d296 7
@
1.18
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="PiersHiggs" date="1175649800" format="1.1" reprev="1.18" version="1.18"}%
a264 1
* commitments
d266 1
a266 1
2. Obtain funding
@
1.17
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="AlexChapman" date="1175648651" format="1.1" reprev="1.17" version="1.17"}%
d214 2
d222 1
a222 1
* LSIDs are TDWG standards which will guarantee uniqueness
d227 1
d232 7
a238 7
* We will apply LSIDs to the "core set" of data objects:
* Specimens - some organisations are currently are serving them now, but moving to a GUID standard - LSIDs
* Names - some organisations are currently are serving them now, but LSIDs will enable linkages and meet the current demands of name resolution nationally and globally
* Concepts - because we can't share concepts now (locally or globally), LSIDs will help us to do this (although we have undertake both philosophical and technical upgrades of our own thinking/systems to enable this)
* Descriptions - projects such as ALA and ABIF would like us to deliver descriptions, and LSIDs will enable us to do this (globally)
* Images - again, projects will also require images, and again LSIDs will enable us to do this (globally)
* We will work towards applying LSIDs to the remaining objects identified (the "optimum set"):
d257 1
@
1.16
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="PiersHiggs" date="1175646346" format="1.1" reprev="1.16" version="1.16"}%
d257 35
a291 2
@
1.15
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BenRichardson" date="1175642458" format="1.1" reprev="1.15" version="1.15"}%
d212 48
@
1.14
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BenRichardson" date="1175583686" format="1.1" reprev="1.14" version="1.14"}%
d20 1
a20 1
* [[Main.RicardoPereira][Ricardo Pereira]] (TDWG Infrastructure Project; Campinas, Brazil)
d62 1
a62 1
* In the biodiversity world, most "data" is LSID metadata
d89 2
a90 2
* Why do we need a policy? Couldn't we just start implementing LSIDs in our institutions
* What can't we do at the moment, or what would be more efficient in the LSID approach
d174 10
@
1.13
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RicardoPereira" date="1175570618" format="1.1" reprev="1.13" version="1.13"}%
d5 2
d21 1
a21 1
* [[Main.RobertRaven][Robert Raven]] (Queensland Museum)
a153 13
---+++ Draft Recommendations
1. LSIDs will be applied to the core (optimum set) of data objects
1. Data objects will "wear" their LSIDs
1. LSIDs will be resolvable
1. Data custodians will be responsible for LSID assignment
1. LSIDs will be opaque
1. How to avoid pitfalls in the creation of LSIDs
We need to make sure that in our databases, where we have locally unique IDs, that they must contain no semantic content, otherwise they cannot be used as LSIDs. (This is effectively the same as saying "LSIDs will be opaque.) Additionally, if it is important in your domain, you should be tracking the relationships between your objects, such as when a single specimen (such as an alga, or a bird) is found to contain another specimen or specimens, those related specimens (epiphytes or parasites) is separated into two (or more) specimens.
Where institutions are maintaining the relationship between data objects, that these relationships should be exposed LSIDs.
d166 36
@
1.12
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BenRichardson" date="1175568326" format="1.1" reprev="1.12" version="1.12"}%
d38 1
a38 1
Ricardo Pereira ([[%ATTACHURL%/LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt][LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt]]) introduced the Life Science Identifiers architecture as being developed by TDWG.
a176 1
%META:FILEATTACHMENT{name="LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt" attachment="LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt" attr="" comment="Ricardo Pereira's presentation about the TDWG Architecture" date="1175556487" path="LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt" size="544768" stream="LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt" user="Main.RicardoPereira" version="1"}%
d178 1
@
1.11
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RicardoPereira" date="1175556489" format="1.1" version="1.11"}%
d34 3
a36 1
---++ Life Science Identifiers and the TDWG Architecture
d55 1
a55 1
---++ Introduction to LSIDs
d62 1
a62 1
The [[http://sourceforge.net/projects/lsid][Firefox LSID Browser]] can be used to resolve LSIDs directly in the Firefox toolbar using the =lsidres= protocol prefix. For example: lsidres:ncbi.nlm.nih.gov:pubmed:12571434. (Download both [[http://sourceforge.net/project/showfiles.php?group_id=130827&package_id=169527][the XPI file] and [[http://jslib.mozdev.org/installation.html][JSLib]] to get this to work.)
d64 1
a64 1
---++ Discussion of the First Two Presentations
d68 1
a68 1
---+++ What Do LSIDs Look Like?
d74 1
a74 1
---+++ What is the Difference between a URN and a URI (and a URL)?
d78 1
a78 1
---+++ Other
d84 1
a84 1
---++ What Are We Here For?
d99 1
a99 1
* Encyclopaedia of Life (EOL)?
d103 1
a103 1
---++ Map for Tuesday 3 April
d109 65
a173 1
-- Main.BenRichardson - 02 Apr 2007
d175 1
a175 1
* [[%ATTACHURL%/LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt][LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt]]: Ricardo Pereira's presentation about the TDWG Architecture
@
1.10
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BenRichardson" date="1175556463" format="1.1" reprev="1.10" version="1.10"}%
d109 3
a111 1
%META:FILEATTACHMENT{name="LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt" attachment="LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt" attr="" comment="Ricardo Pereira's presentation about the TDWG Architecture" date="1175486313" path="LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt" size="544768" stream="LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt" user="Main.RicardoPereira" version="1"}%
@
1.9
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BenRichardson" date="1175497326" format="1.1" reprev="1.9" version="1.9"}%
d98 2
a99 2
* NZMHN
* TDWG
d101 1
a101 1
---++ Map for Tomorrow
@
1.8
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="KevinRichards" date="1175495573" format="1.1" version="1.8"}%
d36 1
a36 1
Ricardo Pereira introduced the Life Science Identifiers architecture as being developed by TDWG. ([[%ATTACHURL%/LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt][LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt]].)
d55 1
a55 1
Kevin Richards introduced LSIDs, including the presentation of a background on GUIDs in general, e.g. UUID, DOI, Handles, LSIDs and PURLs.
d88 18
@
1.7
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BenRichardson" date="1175495499" format="1.1" reprev="1.7" version="1.7"}%
d92 1
@
1.6
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RicardoPereira" date="1175486315" format="1.1" version="1.6"}%
d36 1
a36 1
Ricardo Pereira introduced the Life Science Identifiers architecture as being developed by TDWG.
d60 29
a89 1
* [[%ATTACHURL%/LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt][LSIDWorkshop_TDWGArchitecture_RicardoPereira.ppt]]: Ricardo Pereira's presentation about the TDWG Architecture
@
1.5
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BenRichardson" date="1175486090" format="1.1" reprev="1.5" version="1.5"}%
d61 3
@
1.4
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="RicardoPereira" date="1175481556" format="1.1" version="1.4"}%
d9 1
a9 1
* [[Main.PaulCoddington][Paul Coddington]] (South Australian Partnership for Advanced Computing; The University of Adelaide)
d19 1
d26 1
d32 1
a32 1
This meeting was convened to write an [[AustralasianBiodiversityFederationLsidPolicy][LSID Policy for the Australasian Biodiversity Federation]] and to use that policy to inform future LSID implementation policies globally.
d34 27
a60 1
-- Main.BenRichardson - 02 Apr 2007@
1.3
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BenRichardson" date="1175480749" format="1.1" reprev="1.3" version="1.3"}%
d18 1
a18 1
* [[Main.RicardoPereira][Ricardo Pereira]] (TDWG Infrastructure Project; San Paulo)
d32 1
a32 1
-- Main.BenRichardson - 02 Apr 2007
@
1.2
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="PiersHiggs" date="1175479998" format="1.1" version="1.2"}%
d7 20
a26 15
* Main.BillBarker (Plant Biodiversity Centre; Department of Environment and Heritage; South Australia)
* Main.LeeBelbin (TDWG Infrastructure Project)
* Main.PaulCoddington (South Australian Partnership for Advanced Computing; The University of Adelaide)
* Main.AlexChapman (Western Australian Herbarium; Department of Environment and Conservation)
* Main.PiersHiggs (Gaia Resources - representing Western Australian Museum; Department of Culture & the Arts)
* Main.RobertMorris (South Australian Museum)
* Main.PeterNeish (National Herbarium of Victoria; Royal Botanic Gardens Melbourne; Victoria)
* Main.LaurencePaine (Manager Information Technology; Department of Tourism, Arts and the Environment; Tasmania)
* Main.RicardoPereira (TDWG Infrastructure Project)
* Main.KevinRichards (Allan Herbarium; Manaaki Whenua - Landcare Research; New Zealand)
* Main.BenRichardson (Western Australian Herbarium; Department of Environment and Conservation)
* Main.SteveShattuck (Australian Biological Resources Study; Department of the Environment and Heritage; Canberra)
* Main.KevinThiele (Western Australian Herbarium; Department of Environment and Conservation)
* Main.AaronWilton (Allan Herbarium; Manaaki Whenua - Landcare Research; New Zealand)
* Main.GregWhitbread (Australian National Herbarium; Centre for Plant Biodiversity Research; Australian Capital Territory)
d32 1
a32 1
-- Main.BenRichardson - 02 Apr 2007@
1.1
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BenRichardson" date="1175477912" format="1.1" reprev="1.1" version="1.1"}%
d11 1
a11 1
* Main.PiersHiggs (Western Australian Museum; Department of Art and Culture)
d27 1
a27 1
-- Main.BenRichardson - 02 Apr 2007
@