Topic 3: GUIDs for Taxon Names and Taxon Concepts
Kevin Richards
RichardsK at LANDCARERESEARCH.CO.NZ
Fri Nov 4 13:58:21 CET 2005
Rich
>> For practical reasons I think the starting point for assigning
>> GUIDs should be basically nomenclatural.
>I completely agree -- but again, what gets a "Name" GUID? (as opposed to a
>"usage" GUID or a "concept" GUID) Only basionyms? (I hope!) Or also
>different combinations? (I hope not!) Or also spelling variants? (I *really*
>hope not!!) There is also a problem of how to deal with autonyms
>(=nominotypical names in zoology). One GUID, or two? Logically, only one --
>but most people don't do it that way.
I am trying to understand how you imagine a name guid system will work. When you say "what gets a name guid?", what data/database do you think will get the guid - a central name repository? Are you thinking that all records in various databases around the world that are referring to the "same" name will have the same "Name Guid"? For resolvable GUIDs this will mean the name will always resolve to the central repository data.
Kevin
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
--=__PartCEECEA3D.0__Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Description: HTML
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1522" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">Rich<BR><BR>
<DIV style="COLOR: #000000"> </DIV>
<DIV style="COLOR: #000000">>> For practical reasons I think the starting point for assigning<BR>>> GUIDs should be basically nomenclatural.<BR><BR>>I completely agree -- but again, what gets a "Name" GUID? (as opposed to a<BR>>"usage" GUID or a "concept" GUID) Only basionyms? (I hope!) Or also<BR>>different combinations? (I hope not!) Or also spelling variants? (I *really*<BR>>hope not!!) There is also a problem of how to deal with autonyms<BR>>(=nominotypical names in zoology). One GUID, or two? Logically, only one --<BR>>but most people don't do it that way.</DIV>
<DIV style="COLOR: #000000"> </DIV>
<DIV style="COLOR: #000000">I am trying to understand how you imagine a name guid system will work. When you say "what gets a name guid?", what data/database do you think will get the guid - a central name repository? Are you thinking that all records in various databases around the world that are referring to the "same" name will have the same "Name Guid"? For resolvable GUIDs this will mean the name will always resolve to the central repository data.</DIV>
<DIV style="COLOR: #000000"> </DIV>
<DIV style="COLOR: #000000">Kevin<BR></DIV></BODY></HTML>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<BR>
WARNING: This email and any attachments may be confidential and/or<BR>
privileged. They are intended for the addressee only and are not to be read,<BR>
used, copied or disseminated by anyone receiving them in error. If you are<BR>
not the intended recipient, please notify the sender by return email and<BR>
delete this message and any attachments.<BR>
<BR>
The views expressed in this email are those of the sender and do not<BR>
necessarily reflect the official views of Landcare Research. <BR>
<BR>
Landcare Research<BR>
http://www.landcareresearch.co.nz<BR>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<BR>
<BR>
</BODY></HTML>
More information about the tdwg-tag
mailing list