PublicationBank - requirements evaluation
Donald Hobern
dhobern at GBIF.ORG
Fri Mar 24 16:51:16 CET 2006
Thanks, Chuck. I agree that this is the best approach and that our goal
should simply be to find the right communities with whom to align this
activity.
Best wishes,
Donald
---------------------------------------------------------------
Donald Hobern (dhobern at gbif.org)
Programme Officer for Data Access and Database Interoperability
Global Biodiversity Information Facility Secretariat
Universitetsparken 15, DK-2100 Copenhagen, Denmark
Tel: +45-35321483 Mobile: +45-28751483 Fax: +45-35321480
---------------------------------------------------------------
_____
From: Taxonomic Databases Working Group GUID Project
[mailto:TDWG-GUID at LISTSERV.NHM.KU.EDU] On Behalf Of Chuck Miller
Sent: 24 March 2006 16:43
To: TDWG-GUID at LISTSERV.NHM.KU.EDU
Subject: Re: PublicationBank - requirements evaluation
Roger and Donald,
Roger's list gets even worse because there are multiple editions and formats
(eg. quartile) for many books/journals. The same information may thus occur
on different pages across the different editions. Librarians maintain the
publication records at this detailed level - ie. which editions and formats
are in the library and where.
I agree with Roger. This area of publication information belongs to the
library community. In our Botanicus project we are digitizing 18th and 19th
center botanical references. For the higher level coding information we
have looked to our library management system and engaged our librarians to
supply the correct information. There are existing standards and standards
bodies for book/journal codification. We should not reinvent the wheel. I
think this says we need to engage some library professionals into
biodiversity informatics and TDWG, like we have engaged the geographical
information professionals.
Chuck
-----Original Message-----
From: Roger Hyam
To: TDWG-GUID at LISTSERV.NHM.KU.EDU
Sent: 3/24/2006 4:54 AM
Subject: Re: [TDWG-GUID] PublicationBank - requirements evaluation
Hi Donald,
This makes perfect sense to me but I'd like to introduce one comment
that might muddy the waters or help clear them.
We need an understanding of the granularity of a publication in any such
publication bank as I think 'publication' means different things to
different people. Looking at a monograph I have in front of me:
A Revision of Rhododendron VI subgenus Pentanthera (Sections
Sciadorhodion, Rhodora and Viscidula) W.S. Judd and K.A. Kron (1995)
Edinburgh Journal of Botany (ISSN 0960-4286), Volume 52, Number 1, Pages
1-54. On page 15 we have a good description of Rhododendron
schlippenbachii (a TaxonConcept as this is not a sp nov or comb nov).
The scope of publication bank could be at several levels:
1. LSID for the Journal/Book
2. LSID for the volume
3. LSID for the part
4. LSID for the article
5. LSID for the actual description on page 15.
I would argue quite strongly that taking it beyond level 1 is moderately
pointless as we can have a simple vocabulary of fields that can contain
nice integers to uniquely identify a place within a Journal (or book).
Taking it beyond 1 is also incredibly difficult. An analogy is the use
of postal or zip codes. The postal code refers to a block not a single
address and must be qualified by house and flat number (in the UK).
Perhaps PublicationBank should really be BookAndJournalBank but
identifying books and journals definitely feels to me like it is outside
the scope of TDWG and firmly in the scope of the library community.
I don't want to preempt the outcome of any white paper on the subject
but it may be that a simple applicability statement is required on how
to cite references electronically using existing numbering systems
accompanied by several integer fields (year, volume, part etc). i.e. not
relying on titles or author names. The above references is uniquely
identified by ISSN:0960-4286:52:1:1-54. It may be accompanied by the
text as well of course - for humans!
Just my 2 cents.
Roger
Donald Hobern wrote:
Dear Anna,
Thank you for making the connection between these two groups. I think
it would help if I explained (particularly for the TDWG-LIT group) what
questions are being addressed by the TDWG-GUID work under the general
heading of "PublicationBank".
During the first GUID workshop, we recognized that different classes of
information require (for want of a better term) different strengths of
GUIDs. It is a great help for us to be able to recognise that two
references are to the same piece of data because they use the same GUID
to reference it. Let me give some examples.
If I state that my taxon concept includes a specimen with LSID
urn:lsid:my.org:specimen:123 and someone else also includes the same
LSID in the list of specimens examined as part of their revision, it
helps us to make some firm deductions about shared material. It seems
reasonable that we will be able to associate identifiers with specimens
in a way that ensures that the vast majority of specimens can receive a
single identifier, meaning that all references to that identifier refer
to that specimen and that all references to that specimen use that
identifier. This second part is what I mean when I speak of a strong
identifier.
Now consider the situation with taxon names. Many people are going to
wish to refer to the same names (or nomenclatural acts). It will
clearly be really valuable if we can work towards having a single GUID
for each validly published name, so that we can maximize the
interconnectedness of our data. If I say that refer to the name with
the LSID urn:lsid:my.org:names:xyz and that LSID has data or metadata
indicating that it relates to Aus bus Jones, 2004, and you use the LSID
urn:lsid:another.org:names.abc to refer to the same Aus bus Jones, 2004,
then we are still left with the same string matching problems we have
right now with names. It therefore seems sensible to work with the
nomenclators as the "preferred" issuers of LSIDs for taxon names
(recognising the gaps we have today for zoological names) and to
encourage a move to using those identifiers whenever we wish to provide
a secure reference to each name. (Of course this implies an urgent need
for tools and services to make this easy.)
Turning to taxon concepts, we had a long debate as to whether it was
plausible to try to enforce the same degree of preferred issuers for
LSIDs for taxon concepts. If I publish the first LSID-enabled revision
of a group, I may need to assign LSIDs to refer to many different taxon
concepts. Someone else databasing the taxonomy of the group will have a
similar task. Unless we manage a central easy-to-search registry for
people quickly to find out whether someone has already assigned an LSID
to Aus bus Jones, 2004 sensu Smith, 2006, we will never be able to make
any assumptions based on the fact that I have used
urn:lsid:my.org:concepts:123.1 and you have used
urn:lsid:my.org:concepts:abc.001. Even though the two identifiers are
different there is still a good chance that they may refer to the same
concept (expressed as name-according to-publication). It seems much
more reasonable instead to tackle the problem of getting really strong
LSIDs for names (through the nomenclators) and doing the same thing for
the taxonomic literature (through someone for whom we used the
placeholder name "PublicationBank"). Any concept LSID can resolve
through its metadata to two LSIDs, one for a name and one for a
publication. Comparing concept LSIDs can therefore be based on the
comparisons between these two more fundamental objects.
So, from the standpoint of the GUID group, the requirement here is a
very specific one. We need to find a way to manage assigning LSIDs to
the publications that make up the taxonomic literature, so that we can
all have what would amount to a master list of relevant publications.
>>>From this angle, "all" that is needed is a secure registry into which
the bibliographic data can be stored, cleaned and assigned identifiers.
Of course such a resource could also be an excellent place to register
the location of online digital versions of each publication. At that
point it becomes something even more valuable. On the other hand,
considering it this way suggests that it may already naturally be
addressed as part of the BHL or a similar effort, and part of what we
would like to do is to identify any existing initiatives which may serve
as a part or all of what is required for the LSID work.
As I see it, the TDWG-LIT work gives a framework for the exchange of
these bibliographic data, but we also need to understand the best way to
get the kind of integrated biodiversity bibliography we would like to
have.
Does that all make sense?
Best wishes,
Donald
---------------------------------------------------------------
Donald Hobern ( dhobern at gbif.org <mailto:dhobern at gbif.org> )
Programme Officer for Data Access and Database Interoperability
Global Biodiversity Information Facility Secretariat
Universitetsparken 15, DK-2100 Copenhagen, Denmark
Tel: +45-35321483 Mobile: +45-28751483 Fax: +45-35321480
---------------------------------------------------------------
_____
From: Taxonomic Databases Working Group GUID Project [
mailto:TDWG-GUID at LISTSERV.NHM.KU.EDU
<mailto:TDWG-GUID at LISTSERV.NHM.KU.EDU> ] On Behalf Of Anna Weitzman
Sent: 21 March 2006 20:10
To: TDWG-GUID at LISTSERV.NHM.KU.EDU <mailto:TDWG-GUID at LISTSERV.NHM.KU.EDU>
Subject: Re: PublicationBank - requirements evaluation
Dear Robert,
You may not be aware that TDWG has a list devoted to taxonomic
literature standards. It would be great if you (and anyone else
interested) would join in that discussion ( TDWG Literature standards
mailing list tdwg-lit at lists.tdwg.org <mailto:tdwg-lit at lists.tdwg.org> ;
sign up at
http://lists.tdwg.org/mailman/listinfo/tdwg-lit_lists.tdwg.org/general
<http://lists.tdwg.org/mailman/listinfo/tdwg-lit_lists.tdwg.org/general>
) and add your expertise. The list has only been active since early
February, and the complete correspondence is in the archives (
http://lists.tdwg.org/pipermail/tdwg-lit_lists.tdwg.org/
<http://lists.tdwg.org/pipermail/tdwg-lit_lists.tdwg.org/> ).
Anna L. Weitzman, Ph.D.
Informatics Branch Chief, National Museum of Natural History
Smithsonian Institution, PO Box 37012
Natural History Building, Room W-623, MRC 136
Washington, DC 20013-7012 U.S.A.
phone: (202) 633-0846
fax: (202) 786-3180
email: weitzman at si.edu <mailto:weitzman at si.edu>
INOTAXA - http://www.sil.si.edu/digitalcollections/bca/status.cfm
<http://www.sil.si.edu/digitalcollections/bca/status.cfm>
electronic Biologia Centrali-Americana -
http://www.sil.si.edu/digitalcollections/bca/
<http://www.sil.si.edu/digitalcollections/bca/>
>>> rhuber at WDC-MARE.ORG <mailto:rhuber at WDC-MARE.ORG> 21-Mar-2006
5:06:30 AM >>>
Dear all,
Below is a short 'survey' which hopefully can help to get an overview
on how bibliographic information currently is stored in your databases.
If you don't like to fill such forms, any other info on your current
literature db is also welcome, just send it to me by email!
The list maybe incomplete, if you think important questions are missing
there just let me and the others know.
I will try to sumarize the results on the wiki later.
best regards, Robert
1) How is your literature database/module organised?
- [ ]Database structure completely normalized
- [ ]Database structure not/incomplete normalized
2) How do you hold your bibliographic information?
- [ ]Complete set of Bib info (Author, Title,Source, Volume, Pages)
- [ ]Incomplete set of Bib info
- [ ]Abbreviations (e.g. Stafleu&Cowan)
- [ ]Bib Info and Abbreviations
- Specify which bibliographic fields you hold in your db:
--[ ]Author(s)
--[ ]Title
--[ ]Source (Journal/Book)
--[ ]Pages
--[ ]Date(s)
--[ ]Volume
--[ ]Issue
--[ ]Series
--[ ]URL/GUID
--[ ]Source Editors
--[ ]Series Editors
--[ ]Other:
3) How do you store author names:
- [ ]Abbreviations (e.g. Brummitt & Powell)
- [ ]Complete Name as String, one author per string
- [ ]Complete Name as String, all authors in one string
- [ ]Last Name, First Name separated
4) How do you store journal names/ other sources
- [ ]Complete Name
- [ ]Abbreviation
- [ ]Both
- [ ]If you hold abbreviations acc. to which standard?
Dr. Robert Huber
WDC-MARE / PANGAEA - www.pangaea.de <http://www.pangaea.de/> ,
www.wdc-mare.org <http://www.wdc-mare.org/>
Stratigraphy.net - www.stratigraphy.net <http://www.stratigraphy.net/>
_____________________________________________
MARUM - Institute for Marine Environmental Sciences (location)
University Bremen
Leobener Strasse
POP 330 440
28359 Bremen
Phone ++49 421 218-65593, Fax ++49 421 218-65505
e-mail rhuber@@wdc-mare.org <mailto:rhuber@@wdc-mare.org> ,
robert.huber at stratigraphy.net <mailto:robert.huber at stratigraphy.net>
--
-------------------------------------
Roger Hyam
Technical Architect
Taxonomic Databases Working Group
-------------------------------------
http://www.tdwg.org <http://www.tdwg.org>
roger at tdwg.org <mailto:roger at tdwg.org>
+44 1578 722782
-------------------------------------
------=_NextPart_000_0144_01C64F63.2B0321E0
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>RE: [TDWG-GUID] PublicationBank - requirements evaluation</title>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"PostalCode"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"Street"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"PlaceType"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"PlaceName" downloadurl=3D"http://www.5iantlavalamp.com/"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"address"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"country-region" downloadurl=3D"http://www.5iantlavalamp.com/"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"City" =
downloadurl=3D"http://www.5iamas-microsoft-com:office:smarttags"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"place" downloadurl=3D"http://www.5iantlavalamp.com/"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dblue>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks, Chuck. I agree that =
this is the
best approach and that our goal should simply be to find the right =
communities
with whom to align this activity.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Best =
wishes,<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Donald<br>
<br>
---------------------------------------------------------------<br>
Donald Hobern (<a =
href=3D"mailto:dhobern at gbif.org">dhobern at gbif.org</a>)<br>
Programme Officer for Data Access and Database Interoperability <br>
Global Biodiversity Information Facility Secretariat <br>
Universitetsparken 15, DK-2100 <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Copenhagen</st1:City>,
<st1:country-region =
w:st=3D"on">Denmark</st1:country-region></st1:place><br>
Tel: +45-35321483 <st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Mobile</st1:place></st1:City>:
+45-28751483 Fax: +45-35321480<br>
---------------------------------------------------------------</span></f=
ont><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>
</div>
<div>
<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>
<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>
</span></font></div>
<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
<st1:PersonName
w:st=3D"on">Taxonomic Databases Working Group GUID =
Project</st1:PersonName>
[mailto:TDWG-GUID at LISTSERV.NHM.KU.EDU] <b><span =
style=3D'font-weight:bold'>On
Behalf Of </span></b>Chuck Miller<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 24 March 2006 =
16:43<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
TDWG-GUID at LISTSERV.NHM.KU.EDU<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: =
PublicationBank -
requirements evaluation</span></font><o:p></o:p></p>
</div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>Roger and
Donald,<br>
Roger's list gets even worse because there are multiple editions and =
formats
(eg. quartile) for many books/journals. The same information may =
thus
occur on different pages across the different editions. Librarians =
maintain the
publication records at this detailed level - ie. which editions and =
formats are
in the library and where. <br>
<br>
I agree with Roger. This area of publication information belongs =
to the
library community. In our Botanicus project we are digitizing 18th =
and
19th center botanical references. For the higher level coding =
information
we have looked to our library management system and engaged our =
librarians to
supply the correct information. There are existing standards and
standards bodies for book/journal codification. We should not =
reinvent
the wheel. I think this says we need to engage some library =
professionals
into biodiversity informatics and TDWG, like we have engaged the =
geographical
information professionals.<br>
<br>
Chuck <br>
<br>
-----Original Message-----<br>
From: Roger Hyam<br>
To: TDWG-GUID at LISTSERV.NHM.KU.EDU<br>
Sent: 3/24/2006 4:54 AM<br>
Subject: Re: [TDWG-GUID] PublicationBank - requirements evaluation<br>
<br>
<br>
Hi Donald,<br>
<br>
This makes perfect sense to me but I'd like to introduce one comment<br>
that might muddy the waters or help clear them.<br>
<br>
We need an understanding of the granularity of a publication in any =
such<br>
publication bank as I think 'publication' means different things to<br>
different people. Looking at a monograph I have in front of me:<br>
<br>
A Revision of Rhododendron VI subgenus Pentanthera (Sections<br>
Sciadorhodion, Rhodora and Viscidula) W.S. Judd and K.A. Kron (1995)<br>
<st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Edinburgh</st1:place></st1:City>
Journal of Botany (ISSN 0960-4286), Volume 52, Number 1, Pages<br>
1-54. On page 15 we have a good description of Rhododendron<br>
schlippenbachii (a TaxonConcept as this is not a sp nov or comb =
nov).<br>
<br>
The scope of publication bank could be at several levels:<br>
<br>
<br>
1. LSID for the Journal/Book<br>
<br>
2. LSID for the volume<br>
3. LSID for the part<br>
4. LSID for the article<br>
5. LSID for the actual description on page =
15.<br>
<br>
I would argue quite strongly that taking it beyond level 1 is =
moderately<br>
pointless as we can have a simple vocabulary of fields that can =
contain<br>
nice integers to uniquely identify a place within a Journal (or =
book).<br>
Taking it beyond 1 is also incredibly difficult. An analogy is the =
use<br>
of postal or zip codes. The postal code refers to a block not a =
single<br>
address and must be qualified by house and flat number (in the =
<st1:country-region
w:st=3D"on"><st1:place =
w:st=3D"on">UK</st1:place></st1:country-region>). <br>
<br>
Perhaps PublicationBank should really be BookAndJournalBank but<br>
identifying books and journals definitely feels to me like it is =
outside<br>
the scope of TDWG and firmly in the scope of the library community.<br>
<br>
I don't want to preempt the outcome of any white paper on the =
subject<br>
but it may be that a simple applicability statement is required on =
how<br>
to cite references electronically using existing numbering systems<br>
accompanied by several integer fields (year, volume, part etc). i.e. =
not<br>
relying on titles or author names. The above references is uniquely<br>
identified by ISSN:0960-4286:52:1:1-54. It may be accompanied by the<br>
text as well of course - for humans!<br>
<br>
Just my 2 cents.<br>
<br>
Roger<br>
<br>
<br>
<br>
<br>
<br>
<br>
Donald Hobern wrote:<br>
<br>
Dear Anna,<br>
<br>
Thank you for making the connection between these two groups. I =
think<br>
it would help if I explained (particularly for the TDWG-LIT group) =
what<br>
questions are being addressed by the TDWG-GUID work under the =
general<br>
heading of “PublicationBank”.<br>
<br>
During the first GUID workshop, we recognized that different classes =
of<br>
information require (for want of a better term) different strengths =
of<br>
GUIDs. It is a great help for us to be able to recognise that =
two<br>
references are to the same piece of data because they use the same =
GUID<br>
to reference it. Let me give some examples.<br>
<br>
If I state that my taxon concept includes a specimen with LSID<br>
urn:lsid:my.org:specimen:123 and someone else also includes the same<br>
LSID in the list of specimens examined as part of their revision, it<br>
helps us to make some firm deductions about shared material. It =
seems<br>
reasonable that we will be able to associate identifiers with =
specimens<br>
in a way that ensures that the vast majority of specimens can receive =
a<br>
single identifier, meaning that all references to that identifier =
refer<br>
to that specimen and that all references to that specimen use that<br>
identifier. This second part is what I mean when I speak of a =
strong<br>
identifier.<br>
<br>
Now consider the situation with taxon names. Many people are going =
to<br>
wish to refer to the same names (or nomenclatural acts). It =
will<br>
clearly be really valuable if we can work towards having a single =
GUID<br>
for each validly published name, so that we can maximize the<br>
interconnectedness of our data. If I say that refer to the name =
with<br>
the LSID urn:lsid:my.org:names:xyz and that LSID has data or =
metadata<br>
indicating that it relates to Aus bus Jones, 2004, and you use the =
LSID<br>
urn:lsid:another.org:names.abc to refer to the same Aus bus Jones, =
2004,<br>
then we are still left with the same string matching problems we =
have<br>
right now with names. It therefore seems sensible to work with =
the<br>
nomenclators as the “preferred” issuers of LSIDs for taxon =
names<br>
(recognising the gaps we have today for zoological names) and to<br>
encourage a move to using those identifiers whenever we wish to =
provide<br>
a secure reference to each name. (Of course this implies an urgent =
need<br>
for tools and services to make this easy.)<br>
<br>
Turning to taxon concepts, we had a long debate as to whether it was<br>
plausible to try to enforce the same degree of preferred issuers for<br>
LSIDs for taxon concepts. If I publish the first LSID-enabled =
revision<br>
of a group, I may need to assign LSIDs to refer to many different =
taxon<br>
concepts. Someone else databasing the taxonomy of the group will =
have a<br>
similar task. Unless we manage a central easy-to-search registry =
for<br>
people quickly to find out whether someone has already assigned an =
LSID<br>
to Aus bus Jones, 2004 sensu Smith, 2006, we will never be able to =
make<br>
any assumptions based on the fact that I have used<br>
urn:lsid:my.org:concepts:123.1 and you have used<br>
urn:lsid:my.org:concepts:abc.001. Even though the two identifiers =
are<br>
different there is still a good chance that they may refer to the =
same<br>
concept (expressed as name-according to-publication). It seems =
much<br>
more reasonable instead to tackle the problem of getting really =
strong<br>
LSIDs for names (through the nomenclators) and doing the same thing =
for<br>
the taxonomic literature (through someone for whom we used the<br>
placeholder name “PublicationBank”). Any concept LSID =
can
resolve<br>
through its metadata to two LSIDs, one for a name and one for a<br>
publication. Comparing concept LSIDs can therefore be based on =
the<br>
comparisons between these two more fundamental objects.<br>
<br>
So, from the standpoint of the GUID group, the requirement here is a<br>
very specific one. We need to find a way to manage assigning LSIDs =
to<br>
the publications that make up the taxonomic literature, so that we =
can<br>
all have what would amount to a master list of relevant =
publications.<br>
>>>From this angle, “all” that is needed is a secure registry =
into
which<br>
the bibliographic data can be stored, cleaned and assigned =
identifiers.<br>
Of course such a resource could also be an excellent place to =
register<br>
the location of online digital versions of each publication. At =
that<br>
point it becomes something even more valuable. On the other =
hand,<br>
considering it this way suggests that it may already naturally be<br>
addressed as part of the BHL or a similar effort, and part of what =
we<br>
would like to do is to identify any existing initiatives which may =
serve<br>
as a part or all of what is required for the LSID work.<br>
<br>
As I see it, the TDWG-LIT work gives a framework for the exchange of<br>
these bibliographic data, but we also need to understand the best way =
to<br>
get the kind of integrated biodiversity bibliography we would like =
to<br>
have.<br>
<br>
Does that all make sense?<br>
<br>
Best wishes,<br>
<br>
Donald<br>
<br>
---------------------------------------------------------------<br>
Donald Hobern ( dhobern at gbif.org <<a =
href=3D"mailto:dhobern at gbif.org">mailto:dhobern at gbif.org</a>>
)<br>
Programme Officer for Data Access and Database Interoperability<br>
Global Biodiversity Information Facility Secretariat<br>
Universitetsparken 15, DK-2100 <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Copenhagen</st1:City>,
<st1:country-region =
w:st=3D"on">Denmark</st1:country-region></st1:place><br>
Tel: +45-35321483 <st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Mobile</st1:place></st1:City>:
+45-28751483 Fax: +45-35321480<br>
---------------------------------------------------------------<br>
<br>
<br>
_____ <br>
<br>
<br>
From: <st1:PersonName w:st=3D"on">Taxonomic Databases Working Group GUID =
Project</st1:PersonName>
[<br>
<a =
href=3D"mailto:TDWG-GUID at LISTSERV.NHM.KU.EDU">mailto:TDWG-GUID at LISTSERV.N=
HM.KU.EDU</a><br>
<<a =
href=3D"mailto:TDWG-GUID at LISTSERV.NHM.KU.EDU">mailto:TDWG-GUID at LISTSERV.N=
HM.KU.EDU</a>>
] On Behalf Of Anna Weitzman<br>
Sent: 21 March 2006 20:10<br>
To: TDWG-GUID at LISTSERV.NHM.KU.EDU <<a
href=3D"mailto:TDWG-GUID at LISTSERV.NHM.KU.EDU">mailto:TDWG-GUID at LISTSERV.N=
HM.KU.EDU</a>><br>
<br>
Subject: Re: PublicationBank - requirements evaluation<br>
<br>
<br>
<br>
Dear Robert,<br>
<br>
You may not be aware that TDWG has a list devoted to taxonomic<br>
literature standards. It would be great if you (and anyone =
else<br>
interested) would join in that discussion ( TDWG Literature =
standards<br>
mailing list tdwg-lit at lists.tdwg.org <<a
href=3D"mailto:tdwg-lit at lists.tdwg.org">mailto:tdwg-lit at lists.tdwg.org</a=
>> ;<br>
sign up at<br>
<a =
href=3D"http://lists.tdwg.org/mailman/listinfo/tdwg-lit_lists.tdwg.org/ge=
neral">http://lists.tdwg.org/mailman/listinfo/tdwg-lit_lists.tdwg.org/gen=
eral</a><br>
<<a
href=3D"http://lists.tdwg.org/mailman/listinfo/tdwg-lit_lists.tdwg.org/ge=
neral">http://lists.tdwg.org/mailman/listinfo/tdwg-lit_lists.tdwg.org/gen=
eral</a>><br>
) and add your expertise. The list has only been active since =
early<br>
February, and the complete correspondence is in the archives (<br>
<a =
href=3D"http://lists.tdwg.org/pipermail/tdwg-lit_lists.tdwg.org/">http://=
lists.tdwg.org/pipermail/tdwg-lit_lists.tdwg.org/</a><br>
<<a =
href=3D"http://lists.tdwg.org/pipermail/tdwg-lit_lists.tdwg.org/">http://=
lists.tdwg.org/pipermail/tdwg-lit_lists.tdwg.org/</a>>
).<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
Anna L. Weitzman, Ph.D.<br>
Informatics Branch Chief, <st1:place w:st=3D"on"><st1:PlaceName =
w:st=3D"on">National</st1:PlaceName>
<st1:PlaceType w:st=3D"on">Museum</st1:PlaceType></st1:place> of =
Natural History<br>
Smithsonian Institution, <st1:address w:st=3D"on"><st1:Street =
w:st=3D"on">PO Box</st1:Street>
37012</st1:address><br>
<st1:place w:st=3D"on"><st1:PlaceName =
w:st=3D"on">Natural</st1:PlaceName> <st1:PlaceName
w:st=3D"on">History</st1:PlaceName> <st1:PlaceType =
w:st=3D"on">Building</st1:PlaceType></st1:place>,
Room W-623, MRC 136<br>
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Washington</st1:City>, =
<st1:State
w:st=3D"on">DC</st1:State> <st1:PostalCode =
w:st=3D"on">20013-7012</st1:PostalCode>
<st1:country-region =
w:st=3D"on">U.S.A.</st1:country-region></st1:place><br>
<br>
phone: (202) 633-0846<br>
fax: (202) 786-3180<br>
email: weitzman at si.edu <<a =
href=3D"mailto:weitzman at si.edu">mailto:weitzman at si.edu</a>><br>
INOTAXA - <a =
href=3D"http://www.sil.si.edu/digitalcollections/bca/status.cfm">http://w=
ww.sil.si.edu/digitalcollections/bca/status.cfm</a><br>
<<a =
href=3D"http://www.sil.si.edu/digitalcollections/bca/status.cfm">http://w=
ww.sil.si.edu/digitalcollections/bca/status.cfm</a>><br>
electronic Biologia Centrali-Americana -<br>
<a =
href=3D"http://www.sil.si.edu/digitalcollections/bca/">http://www.sil.si.=
edu/digitalcollections/bca/</a><br>
<<a =
href=3D"http://www.sil.si.edu/digitalcollections/bca/">http://www.sil.si.=
edu/digitalcollections/bca/</a>><br>
<br>
<br>
>>> rhuber at WDC-MARE.ORG <<a =
href=3D"mailto:rhuber at WDC-MARE.ORG">mailto:rhuber at WDC-MARE.ORG</a>>&nb=
sp;
21-Mar-2006<br>
5:06:30 AM >>><br>
Dear all,<br>
<br>
Below is a short 'survey' which hopefully can help to get an =
overview<br>
on how bibliographic information currently is stored in your =
databases.<br>
If you don't like to fill such forms, any other info on your current<br>
literature db is also welcome, just send it to me by email!<br>
<br>
The list maybe incomplete, if you think important questions are =
missing<br>
there just let me and the others know.<br>
<br>
I will try to sumarize the results on the wiki later.<br>
<br>
best regards, Robert<br>
<br>
1) How is your literature database/module organised?<br>
- [ ]Database structure completely normalized<br>
- [ ]Database structure not/incomplete normalized<br>
<br>
2) How do you hold your bibliographic information?<br>
- [ ]Complete set of Bib info (Author, Title,Source, Volume, Pages)<br>
- [ ]Incomplete set of Bib info<br>
- [ ]Abbreviations (e.g. Stafleu&Cowan)<br>
- [ ]Bib Info and Abbreviations<br>
<br>
- Specify which bibliographic fields you hold in your db:<br>
--[ ]Author(s)<br>
--[ ]Title<br>
--[ ]Source (Journal/Book)<br>
--[ ]Pages<br>
--[ ]Date(s)<br>
--[ ]Volume<br>
--[ ]Issue<br>
--[ ]Series<br>
--[ ]URL/GUID<br>
--[ ]Source Editors<br>
--[ ]Series Editors<br>
--[ ]Other:<br>
<br>
3) How do you store author names:<br>
- [ ]Abbreviations (e.g. Brummitt & Powell)<br>
- [ ]Complete Name as String, one author per string<br>
- [ ]Complete Name as String, all authors in one string<br>
- [ ]Last Name, First Name separated<br>
<br>
4) How do you store journal names/ other sources<br>
- [ ]Complete Name<br>
- [ ]Abbreviation<br>
- [ ]Both<br>
- [ ]If you hold abbreviations acc. to which standard?<br>
<br>
Dr. Robert Huber<br>
WDC-MARE / PANGAEA - www.pangaea.de <<a =
href=3D"http://www.pangaea.de/">http://www.pangaea.de/</a>>
,<br>
www.wdc-mare.org <<a =
href=3D"http://www.wdc-mare.org/">http://www.wdc-mare.org/</a>> <=
br>
Stratigraphy.net - www.stratigraphy.net <<a
href=3D"http://www.stratigraphy.net/">http://www.stratigraphy.net/</a>>=
; <br>
_____________________________________________<br>
MARUM - Institute for Marine Environmental Sciences (location)<br>
University <st1:State w:st=3D"on"><st1:place =
w:st=3D"on">Bremen</st1:place></st1:State><br>
Leobener Strasse<br>
POP 330 440<br>
28359 <st1:State w:st=3D"on"><st1:place =
w:st=3D"on">Bremen</st1:place></st1:State><br>
Phone ++49 421 218-65593, Fax ++49 421 218-65505<br>
e-mail rhuber@@wdc-mare.org <<a =
href=3D"mailto:rhuber@@wdc-mare.org">mailto:rhuber@@wdc-mare.org</a>>&=
nbsp;
,<br>
robert.huber at stratigraphy.net <<a =
href=3D"mailto:robert.huber at stratigraphy.net">mailto:robert.huber at stratig=
raphy.net</a>> <br>
<br>
<br>
<br>
--<br>
<br>
<br>
<br>
-------------------------------------<br>
<br>
Roger Hyam<br>
<br>
Technical Architect<br>
<br>
Taxonomic Databases Working Group<br>
<br>
-------------------------------------<br>
<br>
<a href=3D"http://www.tdwg.org">http://www.tdwg.org</a> <<a
href=3D"http://www.tdwg.org">http://www.tdwg.org</a>><br>
<br>
roger at tdwg.org <<a =
href=3D"mailto:roger at tdwg.org">mailto:roger at tdwg.org</a>><br>
<br>
+44 1578 722782<br>
<br>
-------------------------------------</span></font><o:p></o:p></p>
</div>
</body>
</html>
More information about the tdwg-tag
mailing list