February 2006 - tdwg-tag - lists.tdwg.org

PublicationBank, Policy/Best Practice
by Robert Huber 20 Feb '06

20 Feb '06

Dear all, Sorry for my late reply.. I just visited the WIKI today and found that there are a lot more working groups or task items listed there, very good.. One of the tasks is the Publication Bank. I can imagine that this is something some of the GUID group members already have discussed earlier? At least during the workshop my impression was that the common 'management' of publication/ citations is a rather old TDWG problem? Have there been any earlier attempts to solve this? Another thing I would like to propose is something like a 'policy' or 'best practice' group. A lot of the discussions during the workshop dealed with problems like e.g. 'when exactly do I have to assign a new GUID to a taxon name'. A lot of solutions and agrement surely have been proposed in the break out groups and should be documented in the WIKI? best regards, Robert > -----Ursprüngliche Nachricht----- > Von: Taxonomic Databases Working Group GUID Project > [mailto:TDWG-GUID@LISTSERV.NHM.KU.EDU]Im Auftrag von Ricardo Scachetti > Pereira > Gesendet: Dienstag, 14. Februar 2006 15:10 > An: TDWG-GUID(a)LISTSERV.NHM.KU.EDU > Betreff: New GUID working groups and work plan > > > Hi all, > > Now that the first GUID workshop is over, we would like to lay down > a work plan to move forward with GUID work and to prepare for our next > meeting later this year. > > As you may have seen in the workshop report, we have created two > main follow-up areas or working groups to carry on the tasks and address > the issues identified by the group. These two groups are the direct > result of the break-out groups formed during the last day of the GUID-1 > workshop. The groups are: > > * The Infrastructure Working Group - will address the key issues > regarding the deployment of LSID as the GUID technology for biodiversity > informatics. > * The Prototyping Working Group - will develop prototypes of test > cases to test aspects of a GUID infrastructure. > > Due to some overlap between the groups and to simplify our work a > little, we have collapsed the 4 original workshop break-out groups into > the main working groups above. The groups convened by Richard Pyle > (Conceptual vs. Digital LSIDs) and me (LSID spec review and software gap > analysis) are now listed as activities under the Infrastructure Working > Group. These changes are organizational only and are not supposed to > change the mission and mandate of those break-out groups in any way. > > I have made changes to the GUID wiki to reflect and support this > structure. There are links to the two working groups from the home page. > Each working group page has links to individual activities/prototype > pages that will be used to record the respective discussions, > developments, conclusions, and recommendations. These pages are only > placeholders for now. > > In the coming days we will be trying to identify coordinators and > participants to get each of those activities/prototypes started. > Volunteers are most welcome. > > I would like to ask you to please look at these new wiki sections > and make yourself familiar with the tasks and page templates. Please > feel free to make comments and suggestions. > > More on this later. > > Best regards, > > Ricardo

1 0

[tdwg-tapir] Schema modification: r448 - trunk/protocol/examples
by tdwg-tapir＠lists.tdwg.org 17 Feb '06

17 Feb '06

Author: javier Date: 2006-02-17 17:02:30 +0100 (Fri, 17 Feb 2006) New Revision: 448 Modified: trunk/protocol/examples/wfs_gcp_output.xml Log: added targetnamespaces to all elements defined in the structure schema as a hack to not have to support imports in the XML schema. Testing, testing! Modified: trunk/protocol/examples/wfs_gcp_output.xml =================================================================== --- trunk/protocol/examples/wfs_gcp_output.xml 2006-02-17 15:51:28 UTC (rev 447) +++ trunk/protocol/examples/wfs_gcp_output.xml 2006-02-17 16:02:30 UTC (rev 448) @@ -7,37 +7,41 @@ http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema.xsd "> <structure> -  - <xs:schema targetNamespace="http://www.ipgri.org/schemas/gcp_passport_gml/1.0"> -  - <xs:element name="FeatureCollection"> +  + <xs:schema> + <xs:element name="FeatureCollection" targetNamespace="http://www.opengis.net/wfs"> <xs:complexType> <xs:sequence> - <xs:element maxOccurs="unbounded" name="featureMember"> + <xs:element maxOccurs="unbounded" name="featureMember" targetNamespace="http://www.opengis.net/gml"> <xs:complexType> <xs:sequence> - <xs:element name="accession"> + <xs:element name="accession" targetNamespace="http://www.ipgri.org/schemas/gcp_passport_gml/1.0"> <xs:complexType> <xs:sequence> - <xs:element name="GermplasmID" type="xs:string" /> - <xs:element name="FAOInstituteCode" type="xs:string" /> - <xs:element name="CollectionName" type="xs:string" /> - <xs:element name="FullScientificName" type="xs:string" /> - <xs:element name="Genus" type="xs:string" /> - <xs:element name="Species" type="xs:string" /> - <xs:element name="CollectingPlace" type="xs:string" /> - <xs:element name="CountryCode" type="xs:string" /> - <xs:element name="LocationGML"> + <xs:element name="GermplasmID" type="xs:string" targetNamespace="http://www.ipgri.org/schemas/gcp_passport_gml/1.0"/> + <xs:element name="FAOInstituteCode" type="xs:string" targetNamespace="http://www.ipgri.org/schemas/gcp_passport_gml/1.0" /> + <xs:element name="CollectionName" type="xs:string" targetNamespace="http://www.ipgri.org/schemas/gcp_passport_gml/1.0" /> + <xs:element name="FullScientificName" type="xs:string" targetNamespace="http://www.ipgri.org/schemas/gcp_passport_gml/1.0" /> + <xs:element name="Genus" type="xs:string" targetNamespace="http://www.ipgri.org/schemas/gcp_passport_gml/1.0" /> + <xs:element name="Species" type="xs:string" targetNamespace="http://www.ipgri.org/schemas/gcp_passport_gml/1.0" /> + <xs:element name="CollectingPlace" type="xs:string" targetNamespace="http://www.ipgri.org/schemas/gcp_passport_gml/1.0" /> + <xs:element name="CountryCode" type="xs:string" targetNamespace="http://www.ipgri.org/schemas/gcp_passport_gml/1.0" /> + <xs:element name="LocationGML" targetNamespace="http://www.ipgri.org/schemas/gcp_passport_gml/1.0"> <xs:complexType> <xs:sequence> - <xs:element name="Point"> + <xs:element name="Point" targetNamespace="http://www.opengis.net/gml"> <xs:complexType> <xs:sequence> - <xs:element name="coordinates"> + <xs:element name="coordinates" targetNamespace="http://www.opengis.net/gml"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:string">

1 0

[tdwg-tapir] Schema modification: r447 - trunk/protocol/examples
by tdwg-tapir＠lists.tdwg.org 17 Feb '06

17 Feb '06

Author: javier Date: 2006-02-17 16:51:28 +0100 (Fri, 17 Feb 2006) New Revision: 447 Added: trunk/protocol/examples/wfs_gcp_output.xml Log: small change Added: trunk/protocol/examples/wfs_gcp_output.xml =================================================================== --- trunk/protocol/examples/wfs_gcp_output.xml 2006-02-17 15:05:08 UTC (rev 446) +++ trunk/protocol/examples/wfs_gcp_output.xml 2006-02-17 15:51:28 UTC (rev 447) @@ -0,0 +1,103 @@ +<?xml version="1.0" encoding="UTF-8"?> +<outputModel xmlns="http://www.tdwg.org/schemas/tapir/datasource/1.0" + xmlns:xs="http://www.w3.org/2001/XMLSchema" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation=" + http://www.tdwg.org/schemas/tapir/datasource/1.0 http://ww2.biocase.org/svn/tapir/trunk/protocol/tapir.xsd + http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema.xsd + "> + <structure> +  + <xs:schema targetNamespace="http://www.ipgri.org/schemas/gcp_passport_gml/1.0"> +  + <xs:element name="FeatureCollection"> + <xs:complexType> + <xs:sequence> + <xs:element maxOccurs="unbounded" name="featureMember"> + <xs:complexType> + <xs:sequence> + <xs:element name="accession"> + <xs:complexType> + <xs:sequence> + <xs:element name="GermplasmID" type="xs:string" /> + <xs:element name="FAOInstituteCode" type="xs:string" /> + <xs:element name="CollectionName" type="xs:string" /> + <xs:element name="FullScientificName" type="xs:string" /> + <xs:element name="Genus" type="xs:string" /> + <xs:element name="Species" type="xs:string" /> + <xs:element name="CollectingPlace" type="xs:string" /> + <xs:element name="CountryCode" type="xs:string" /> + <xs:element name="LocationGML"> + <xs:complexType> + <xs:sequence> + <xs:element name="Point"> + <xs:complexType> + <xs:sequence> + <xs:element name="coordinates"> + <xs:complexType> + <xs:simpleContent> + <xs:extension base="xs:string"> + <xs:attribute name="decimal" type="xs:string" use="required" /> + <xs:attribute name="cs" type="xs:string" use="required" /> + <xs:attribute name="ts" type="xs:string" use="required" /> + </xs:extension> + </xs:simpleContent> + </xs:complexType> + </xs:element> + </xs:sequence> + <xs:attribute name="srsName" type="xs:string" use="required" /> + </xs:complexType> + </xs:element> + </xs:sequence> + </xs:complexType> + </xs:element> + </xs:sequence> + <xs:attribute name="fid" type="xs:string" use="required" /> + </xs:complexType> + </xs:element> + </xs:sequence> + </xs:complexType> + </xs:element> + </xs:sequence> + </xs:complexType> + </xs:element> + </xs:schema> + </structure> + <indexingElement path="/FeatureCollection/featureMember"/> + <mapping> + <node path="/FeatureCollection/featureMember@fid"> + <concept id="dwc:/CatalogNumber"/> + </node> + <node path="/FeatureCollection/featureMember/GermplasmID"> + <concept id="dwc:/CatalogNumber"/> + </node> + <node path="/FeatureCollection/featureMember/FullScientificName"> + <concept id="dwc:/ScientificName"/> + </node> + <node path="/FeatureCollection/featureMember/Genus"> + <concept id="dwc:/Genus"/> + </node> + <node path="/FeatureCollection/featureMember/LocationGML/Point@srsName"> + <literal value="http://www.opengis.net/gml/srs/epsg.xml#4326"/> + </node> + <node path="/FeatureCollection/featureMember/LocationGML/Point/coordinates@decimal"> + <literal value="."/> + </node> + <node path="/FeatureCollection/featureMember/LocationGML/Point/coordinates@cs"> + <literal value=","/> + </node> + <node path="/FeatureCollection/featureMember/LocationGML/Point/coordinates@ts"> + <literal value=" "/> + </node> + <node path="/FeatureCollection/featureMember/LocationGML/Point/coordinates"> + <concept id="dwc:/Longitude"/> + <literal value=","/> + <concept id="dwc:/Latitude"/> + </node> + </mapping> +</outputModel> +

1 0

[tdwg-tapir] Capabilities
by Javier de la Torre 17 Feb '06

17 Feb '06

Ups, Sorry, I did not realize that the capabilities document has changed but it is still not updated in pywrapper... Javier.

1 0

Re: [tdwg-tapir] cherrypy2.2
by Javier de la Torre 17 Feb '06

17 Feb '06

Hi, Pufff... the capabilities get horrible big... Now I undertand why WFS has an operation called DescribeFeatureType that reaturns an XML schema. Instead of including the view description in the capabilities we could have created a new operation called DescribeView that would return the schema. In WFS it is nice that when you do a search and you want a certain FeatureType you get the XML document with a schema location that is a DescribeFeatureType operation itself to the same provider. I actaully don't know the implications of this, but I certainly think is neat :) Javier.

1 0

Re: New GUID working groups and work plan [ Scanned for viruses ]
by Paul Kirk 14 Feb '06

14 Feb '06

OK, Kevin is the person to give you the details (currently 2:55am Wednesday in NZ). Cheers, Paul -----Original Message----- From: Taxonomic Databases Working Group GUID Project [mailto:TDWG-GUID@LISTSERV.NHM.KU.EDU]On Behalf Of Ricardo Scachetti Pereira Sent: 14 February 2006 14:53 To: TDWG-GUID(a)LISTSERV.NHM.KU.EDU Subject: Re: New GUID working groups and work plan [ Scanned for viruses ] Paul, Thanks for letting me know. I am very interested in following closely the development of LSID prototype resolvers such as yours, specially regarding missing LSID software components, limitations of current LSID specifications, or any other roadblocks you may find in LSID software setup and development. So, could you (or Kevin) please fill me in on the details of your prototype? I've added a new wiki page specially for that. You can use to record the relevant information. The page is at: http://wiki.gbif.org/guidwiki/wikka.php?wakka=LSIDResolverForTaxonNamesIF Please, feel free to edit that page and add the required details. We intend to record similar information about the development of the other prototypes and use that information as input in various others GUID activities. If you provide such information I can offer to help in your development activities. This applies to any other groups that are planning on developing LSID prototype resolvers. Just add your details to the GUID wiki and let me (us) know. Cheers, Ricardo Paul Kirk wrote: >Ricardo, > >The Index Fungorum Partnership has already started to set up an LSID resolver demo based on the Index Fungorum database (using the existing Web Service running there). CABI is providing the server, Kevin Richards (Landcare Research New Zealand) is doing the install. > >Donald, Lee and Roger already know, > >In haste, > >Paul > >-----Original Message----- >From: Taxonomic Databases Working Group GUID Project >[mailto:TDWG-GUID@LISTSERV.NHM.KU.EDU]On Behalf Of Ricardo Scachetti >Pereira >Sent: 14 February 2006 14:10 >To: TDWG-GUID(a)LISTSERV.NHM.KU.EDU >Subject: New GUID working groups and work plan [ Scanned for viruses ] > > > Hi all, > > Now that the first GUID workshop is over, we would like to lay down >a work plan to move forward with GUID work and to prepare for our next >meeting later this year. > > As you may have seen in the workshop report, we have created two >main follow-up areas or working groups to carry on the tasks and address >the issues identified by the group. These two groups are the direct >result of the break-out groups formed during the last day of the GUID-1 >workshop. The groups are: > > * The Infrastructure Working Group - will address the key issues >regarding the deployment of LSID as the GUID technology for biodiversity >informatics. > * The Prototyping Working Group - will develop prototypes of test >cases to test aspects of a GUID infrastructure. > > Due to some overlap between the groups and to simplify our work a >little, we have collapsed the 4 original workshop break-out groups into >the main working groups above. The groups convened by Richard Pyle >(Conceptual vs. Digital LSIDs) and me (LSID spec review and software gap >analysis) are now listed as activities under the Infrastructure Working >Group. These changes are organizational only and are not supposed to >change the mission and mandate of those break-out groups in any way. > > I have made changes to the GUID wiki to reflect and support this >structure. There are links to the two working groups from the home page. >Each working group page has links to individual activities/prototype >pages that will be used to record the respective discussions, >developments, conclusions, and recommendations. These pages are only >placeholders for now. > > In the coming days we will be trying to identify coordinators and >participants to get each of those activities/prototypes started. >Volunteers are most welcome. > > I would like to ask you to please look at these new wiki sections >and make yourself familiar with the tasks and page templates. Please >feel free to make comments and suggestions. > > More on this later. > > Best regards, > >Ricardo > > >

1 0

Re: New GUID working groups and work plan [ Scanned for viruses ]
by Paul Kirk 14 Feb '06

14 Feb '06

Ricardo, The Index Fungorum Partnership has already started to set up an LSID resolver demo based on the Index Fungorum database (using the existing Web Service running there). CABI is providing the server, Kevin Richards (Landcare Research New Zealand) is doing the install. Donald, Lee and Roger already know, In haste, Paul -----Original Message----- From: Taxonomic Databases Working Group GUID Project [mailto:TDWG-GUID@LISTSERV.NHM.KU.EDU]On Behalf Of Ricardo Scachetti Pereira Sent: 14 February 2006 14:10 To: TDWG-GUID(a)LISTSERV.NHM.KU.EDU Subject: New GUID working groups and work plan [ Scanned for viruses ] Hi all, Now that the first GUID workshop is over, we would like to lay down a work plan to move forward with GUID work and to prepare for our next meeting later this year. As you may have seen in the workshop report, we have created two main follow-up areas or working groups to carry on the tasks and address the issues identified by the group. These two groups are the direct result of the break-out groups formed during the last day of the GUID-1 workshop. The groups are: * The Infrastructure Working Group - will address the key issues regarding the deployment of LSID as the GUID technology for biodiversity informatics. * The Prototyping Working Group - will develop prototypes of test cases to test aspects of a GUID infrastructure. Due to some overlap between the groups and to simplify our work a little, we have collapsed the 4 original workshop break-out groups into the main working groups above. The groups convened by Richard Pyle (Conceptual vs. Digital LSIDs) and me (LSID spec review and software gap analysis) are now listed as activities under the Infrastructure Working Group. These changes are organizational only and are not supposed to change the mission and mandate of those break-out groups in any way. I have made changes to the GUID wiki to reflect and support this structure. There are links to the two working groups from the home page. Each working group page has links to individual activities/prototype pages that will be used to record the respective discussions, developments, conclusions, and recommendations. These pages are only placeholders for now. In the coming days we will be trying to identify coordinators and participants to get each of those activities/prototypes started. Volunteers are most welcome. I would like to ask you to please look at these new wiki sections and make yourself familiar with the tasks and page templates. Please feel free to make comments and suggestions. More on this later. Best regards, Ricardo

1 0

Re: New GUID working groups and work plan [ Scanned for viruses ]
by Ricardo Scachetti Pereira 14 Feb '06

14 Feb '06

Paul, Thanks for letting me know. I am very interested in following closely the development of LSID prototype resolvers such as yours, specially regarding missing LSID software components, limitations of current LSID specifications, or any other roadblocks you may find in LSID software setup and development. So, could you (or Kevin) please fill me in on the details of your prototype? I've added a new wiki page specially for that. You can use to record the relevant information. The page is at: http://wiki.gbif.org/guidwiki/wikka.php?wakka=LSIDResolverForTaxonNamesIF Please, feel free to edit that page and add the required details. We intend to record similar information about the development of the other prototypes and use that information as input in various others GUID activities. If you provide such information I can offer to help in your development activities. This applies to any other groups that are planning on developing LSID prototype resolvers. Just add your details to the GUID wiki and let me (us) know. Cheers, Ricardo Paul Kirk wrote: >Ricardo, > >The Index Fungorum Partnership has already started to set up an LSID resolver demo based on the Index Fungorum database (using the existing Web Service running there). CABI is providing the server, Kevin Richards (Landcare Research New Zealand) is doing the install. > >Donald, Lee and Roger already know, > >In haste, > >Paul > >-----Original Message----- >From: Taxonomic Databases Working Group GUID Project >[mailto:TDWG-GUID@LISTSERV.NHM.KU.EDU]On Behalf Of Ricardo Scachetti >Pereira >Sent: 14 February 2006 14:10 >To: TDWG-GUID(a)LISTSERV.NHM.KU.EDU >Subject: New GUID working groups and work plan [ Scanned for viruses ] > > > Hi all, > > Now that the first GUID workshop is over, we would like to lay down >a work plan to move forward with GUID work and to prepare for our next >meeting later this year. > > As you may have seen in the workshop report, we have created two >main follow-up areas or working groups to carry on the tasks and address >the issues identified by the group. These two groups are the direct >result of the break-out groups formed during the last day of the GUID-1 >workshop. The groups are: > > * The Infrastructure Working Group - will address the key issues >regarding the deployment of LSID as the GUID technology for biodiversity >informatics. > * The Prototyping Working Group - will develop prototypes of test >cases to test aspects of a GUID infrastructure. > > Due to some overlap between the groups and to simplify our work a >little, we have collapsed the 4 original workshop break-out groups into >the main working groups above. The groups convened by Richard Pyle >(Conceptual vs. Digital LSIDs) and me (LSID spec review and software gap >analysis) are now listed as activities under the Infrastructure Working >Group. These changes are organizational only and are not supposed to >change the mission and mandate of those break-out groups in any way. > > I have made changes to the GUID wiki to reflect and support this >structure. There are links to the two working groups from the home page. >Each working group page has links to individual activities/prototype >pages that will be used to record the respective discussions, >developments, conclusions, and recommendations. These pages are only >placeholders for now. > > In the coming days we will be trying to identify coordinators and >participants to get each of those activities/prototypes started. >Volunteers are most welcome. > > I would like to ask you to please look at these new wiki sections >and make yourself familiar with the tasks and page templates. Please >feel free to make comments and suggestions. > > More on this later. > > Best regards, > >Ricardo > > >

1 0

New GUID working groups and work plan
by Ricardo Scachetti Pereira 14 Feb '06

14 Feb '06

Hi all, Now that the first GUID workshop is over, we would like to lay down a work plan to move forward with GUID work and to prepare for our next meeting later this year. As you may have seen in the workshop report, we have created two main follow-up areas or working groups to carry on the tasks and address the issues identified by the group. These two groups are the direct result of the break-out groups formed during the last day of the GUID-1 workshop. The groups are: * The Infrastructure Working Group - will address the key issues regarding the deployment of LSID as the GUID technology for biodiversity informatics. * The Prototyping Working Group - will develop prototypes of test cases to test aspects of a GUID infrastructure. Due to some overlap between the groups and to simplify our work a little, we have collapsed the 4 original workshop break-out groups into the main working groups above. The groups convened by Richard Pyle (Conceptual vs. Digital LSIDs) and me (LSID spec review and software gap analysis) are now listed as activities under the Infrastructure Working Group. These changes are organizational only and are not supposed to change the mission and mandate of those break-out groups in any way. I have made changes to the GUID wiki to reflect and support this structure. There are links to the two working groups from the home page. Each working group page has links to individual activities/prototype pages that will be used to record the respective discussions, developments, conclusions, and recommendations. These pages are only placeholders for now. In the coming days we will be trying to identify coordinators and participants to get each of those activities/prototypes started. Volunteers are most welcome. I would like to ask you to please look at these new wiki sections and make yourself familiar with the tasks and page templates. Please feel free to make comments and suggestions. More on this later. Best regards, Ricardo

1 0

TDWG/GBIF GUID-1 Workshop Report
by Ricardo Scachetti Pereira 14 Feb '06

14 Feb '06

Hi all, Here is a short(er) version of the GUID-1 workshop report. Just for the records. ------------------------- Introduction ============ The Taxonomic Databases Working Group (TDWG) and the Global Biodiversity Information Facility (GBIF) completed their first Workshop on Globally Unique Identifiers for Biodiversity Informatics (GUID-1) at the National Center for Evolutionary Synthesis (NESCent), Durham, NC, USA on Feb 1-3, 2006. Motivation ========== A GUID framework is foundational in facilitating systems interoperability in biodiversity informatics. It meets the need for a universally adopted system for assigning and recognizing identifiers in the domain. A GUID system will help to manage and cross-link the many different types of entities that are manipulated analytically in biodiversity informatics and will improve interoperability with other related life sciences domains, such as bioinformatics and ecology. The Group ========= The workshop delegates consisted of a representative cross-section of domain experts from around the world (see http://wiki.gbif.org/guidwiki/wikka.php?wakka=GUID1Participants) Goals ===== The goals of the workshop were to: * Discuss the requirements for globally unique identifiers for biodiversity informatics * Select an optimal GUID technology (LSID, DOI, Handles or other) * Begin to identify key parameters for implementing an effective system * Investigate the use of a RDF-based metadata architecture for GUIDs * Form working groups to address key identified issues before the GUID-2 workshop Outcomes ======== * Life Science Identifiers (LSID) seem the most appropriate GUID strategy in biodiversity informatics. * The use of LSIDs does not preclude the use of other technologies where appropriate. * LSID authorities must use the Domain Name Service (DNS) to support identifier resolution. (The LSID specification allows for other resolution mechanisms, but DNS is currently the only mechanism in use.) * Although it is not possible to prevent multiple data providers from issuing alternate identifiers resolving to the same data record, the community should develop processes and tools to coordinate issuing of single identifiers for some classes of data (e.g. taxon names). * Metadata should be provided as RDF serialized as XML and should exploit existing vocabularies such as Dublin Core wherever these are in wide use. * The LSID getData method should be used only where it is possible and appropriate to return an unchanging series of bytes. In other cases only the LSID getMetadata method should be used. (This reflects the use of the terms “data” and “metadata” in connection with LSIDs.) Justifications ============== The main criteria leading to the selection of LSID technology were: * The cost-model of DOI. That technology is predicated on the idea that a revenue stream can be constructed for the identified objects, typically sufficient to defray the cost. That this is not the case for most, if not all, of the objects that are likely to be identified in our systems. * The more dynamic nature of LSIDs, which does not require prior registration of every individual identifier before use. * The open nature of the LSID protocol and software stack, and the ease of implementing LSIDs on different platforms. See http://wiki.gbif.org/guidwiki/wikka.php?wakka=GUID1Report for a more detailed comparison of GUID technologies. Work Plan ========= There are still many issues to address before our community can fully implement an identifier system based on LSIDs. The workshop addressed a number of specific issues and developed working groups to address the following issues: * Developing white papers to address best practices and key infrastructure questions. * Prototyping activities. The Infrastructure Working Group ================================ This group was formed to address the key issues regarding the deployment of LSID as the GUID technology for biodiversity informatics. The mandate of this working group is to identify required or desirable policies and infrastructure components to ensure robust, long-term operation of shared GUIDs. The following activities were identified: 1. Specify minimal standards (including tools and services) for GUID issuance. 2. Investigate long-term archival of LSIDs and associated data and metadata. 3. Investigate establishing (optional) central registration authority. 4. Investigate establishing repository for data and (orphan) datasets with GUIDs 5. Investigate the feasibility, existing actors and requirements for a ”Publication Bank” (a resource to act as a central registry of taxonomic literature and its digital representations, including assigning GUIDs to each publication. 6. Clarify the distinction between GUIDs assigned to data objects and to conceptual entities. 7. Investigate 3rd-party annotation and link-out mechanisms. 8. Develop materials to communicate with wider community. 9. Develop best practices for assigning resolver namespaces for LSIDs. 10. Perform review of LSID specification to identify possible enhancements. 11. Perform gap analysis of LSID software.. The outcomes of this group will be a series of white papers addressing the key infrastructure issues. Those will be reviewed during the second GUID meeting later this year. The Prototyping Working Group ============================= Our community must experiment with LSID technology and Ontology Engineering if we are to implement a production quality LSID system, The working group will develop prototypes of test cases to test aspects of a GUID infrastructure. The group will develop test LSID resolvers using data objects provided by each domain, such as names, specimens, and concepts. This activity will also help involve (and train) the community in developing appropriate RDF ontologies, leading to concrete recommendations and implementations. The potential prototypes to be developed and respective Conveners are: 1. LSID resolver for taxon names – developed by nomenclators using IPNI database and an RDF version of TCS-Names – Group responsible: Roger Hyam, Sally Hinchcliffe, Paul Kirk 2. LSID resolver for specimens using DarwinCore (also ABCD?) - Steve Perry. 3. LSID resolver for taxon concepts by SEEK using TCS. 4. LSID resolver for observations by SEEK using EML. 5. LSID resolver for character data by Damian Barnier, Kevin Thiele 6. LSID resolver for images: Greg Riccardi (MorphBank), Bob Morris The taxon names resolver has the highest priority. Prototypes will address one or more of the following (but may not be full implementations of an LSID resolution service): * Hardware and software (including LSID stack) * RDFS/OWL vocabulary for domain * Data mapping between local data store scheme and shared ontology Other important tasks identified by this group are: * Development of ontologies to represent metadata for the various domains. Coordinated by TDWG TAG with help of experienced ontology engineers. * To set up a real live LSID server to perform scalability testing. * A project to demonstrate the potential from LSID-based integration of data for a particular group (Ants) – LSIDs, taxonomic lit, specimen, images, names, sequences from Genbank – Rod Page * To use SEEK Taxon resolution server (alpha) for testing. This group will have 3 months to work on the specified tasks before preparing for the second GUID workshop. Next Workshop: GUID-2 ===================== The TDWG Infrastructure Project is planning a second GUID workshop in late May or early June, 2006. At the time of writing a venue has not been decided. The second workshop should cover the following: * Review of the material produced between the workshops by both working groups (prototypes and white papers). * Summary of the lessons learned in the process. * Identify open issues and devise specific work plans to address them. * Draft concrete recommendations on GUIDs for production systems – in general and for each specific domain (names, specimens, concepts, images, etc). Information about GUID-2 will be distributed as soon as possible. Other Resources =============== * See http://wiki.gbif.org/guidwiki for more on the TDWG GUID effort. * See http://wiki.gbif.org/guidwiki/wikka.php?wakka=GUID1Minutes for the workshop minutes and presentations. * See http://wiki.gbif.org/guidwiki/wikka.php?wakka=GUID1Report for a full report, or download it in pdf format from the following link: http://wiki.gbif.org/guidwiki/images/GUID-1Report.pdf

1 0