LSID Annotation and Link-out

Kevin Richards RichardsK at LANDCARERESEARCH.CO.NZ
Wed Apr 26 09:19:23 CEST 2006


Relying on crwalers is not always going to get all the relevant information for a particular query, especially if that relevant data that is hidden deep inside some organisation's database, and hence cannot be found via crawlers.
To get the best functionality for the system I think we need to strongly reccommend a required set of services that all of our data providers need to provide (ie including the LSID FAN services that allow thrid party 'annotations' of LSID objects).  For those who cannot provide all services, then tools like crawlers could attempt to fill the gap.
Kevin

>>> dhobern at GBIF.ORG 21/04/2006 9:15 p.m. >>>

There would seem to be two other fairly obvious approaches we could follow to manage external annotation of LSIDs: We could rely simply on passive discovery of the links by crawler applications such as the GBIF data indexer * when indexing the third-party data, it would be possible to store a reference to the relationship between the objects and to offer a service allowing users to check for "additional information" on any LSID.  This relies on good coverage by the crawler tools * in particular it assumes that the data objects offered by the third-party data provider belong to classes which are themselves of interest to the crawler. 



++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


--=__PartBB9EBC4B.0__Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Description: HTML

<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word" xmlns:st1 = "urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1522" name=GENERATOR><o:SmartTagType downloadurl="http://www.5iantlavalamp.com/" name="country-region" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType downloadurl="http://www.5iantlavalamp.com/" name="place" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType downloadurl="http://www.5iamas-microsoft-com:office:smarttags" name="City" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType>
<STYLE>
st1\:*{behavior:url(#default#ieooui) }
</STYLE>

<STYLE>
<!--
 /* 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:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:Arial;
        color:windowtext;}
@page Section1
        {size:612.0pt 792.0pt;
        margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
        {page:Section1;}
 /* List Definitions */
 @list l0
        {mso-list-id:33578878;
        mso-list-type:hybrid;
        mso-list-template-ids:1461087856 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {mso-level-tab-stop:36.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l1
        {mso-list-id:651298010;
        mso-list-type:hybrid;
        mso-list-template-ids:-1349079592 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
        {mso-level-tab-stop:36.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
ol
        {margin-bottom:0cm;}
ul
        {margin-bottom:0cm;}
-->
</STYLE>
</HEAD>
<BODY lang=EN-US style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma" vLink=purple link=blue>
<DIV>Relying on crwalers is not always going to get all the relevant information for a particular query, especially if that relevant data that is hidden deep inside some organisation's database, and hence&nbsp;cannot be found via crawlers.</DIV>
<DIV>To get the best functionality for the system I think we need to strongly reccommend a required set of services&nbsp;that all of our data providers need to provide (ie including the LSID FAN services that allow thrid party 'annotations' of LSID objects).&nbsp; For those who cannot provide all services, then tools like crawlers could attempt to fill the gap.</DIV>
<DIV>Kevin<BR><BR>&gt;&gt;&gt; dhobern at GBIF.ORG 21/04/2006 9:15 p.m. &gt;&gt;&gt;<BR></DIV>
<DIV style="COLOR: #000000">
<DIV class=Section1>
<P class=MsoNormal>
<P class=MsoNormal><FONT face=Arial size=2><SPAN lang=EN-GB style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p></o:p></SPAN></FONT></P><FONT face=Arial size=2><SPAN lang=EN-GB style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">There would seem to be two other fairly obvious approaches we could follow to manage external annotation of LSIDs:<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN lang=EN-GB style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<OL style="MARGIN-TOP: 0cm" type=1>
<LI class=MsoNormal style="mso-list: l0 level1 lfo1"><FONT face=Arial size=2><SPAN lang=EN-GB style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">We could rely simply on passive discovery of the links by crawler applications such as the GBIF data indexer – when indexing the third-party data, it would be possible to store a reference to the relationship between the objects and to offer a service allowing users to check for “additional information” on any LSID.&nbsp; This relies on good coverage by the crawler tools – in particular it assumes that the data objects offered by the third-party data provider belong to classes which are themselves of interest to the crawler.<o:p></o:p></SPAN></FONT> </LI></OL></DIV></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