- From: Kevin Richards <RichardsK@landcareresearch.co.nz>
- Date: Mon, 08 May 2006 08:39:13 +1200
- To: "swhclsig" <public-semweb-lifesci@w3.org>
- Message-Id: <s45f03b6.025@smtp.landcareresearch.co.nz>
Hi I have some questions from a related community. The community is a biodiversity inormatics group involved with creating data sharing and interoperability standards (TDWG Taxonomic Databases Working Group - www.tdwg.org). Questions: What GUIDs are you using within your community, or are intending to use to identify instances of your data (eg PURL, LSID)? Will you use the same GUID for all data objects, eg do RDF classes get the same sort of ID as an instance of that class? We are currently looking at several technologies including LSIDs, PURLs and DOIs. Does anyone have any thoughts on these options? At present we are leaning towards the LSID, and returning RDF as the metdata to allow sematntic web type functionality. However we have considered the problem of LSID resolution and wonder if the requirement for LSIDs to be resolved through LSID client software may be too restrictive when working with semantic web tools - eg an RDF/RDFS document with LSIDs throughout will not be automatically resolved by most semantic web tools as the tools do not "know" how to resolve these particular urns. Any thoughts? Thanks Kevin Richards ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments. The views expressed in this email are those of the sender and do not necessarily reflect the official views of Landcare Research. Landcare Research http://www.landcareresearch.co.nz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Received on Monday, 8 May 2006 17:08:53 UTC