LSID Annotation and Link-out
Roger Hyam
roger at TDWG.ORG
Wed Apr 26 09:31:50 CEST 2006
At the TAG-1 meeting we discussed a base level provider having GUID
resolution plus a harvest API (perhaps based on OAI though we need to
look into it) with search/query as the next level of services.
Roger
Kevin Richards wrote:
> 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:
>
>
>
> 1. 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
--
-------------------------------------
Roger Hyam
Technical Architect
Taxonomic Databases Working Group
-------------------------------------
http://www.tdwg.org
roger at tdwg.org
+44 1578 722782
-------------------------------------
--------------010803050301060302000200
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
At the TAG-1 meeting we discussed a base level provider having GUID
resolution plus a harvest API (perhaps based on OAI though we need to
look into it) with search/query as the next level of services.<br>
<br>
Roger<br>
<br>
Kevin Richards wrote:
<blockquote cite="mids44f3b27.001 at smtp.landcareresearch.co.nz"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<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>
<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 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 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.</div>
<div>Kevin<br>
<br>
>>> <a class="moz-txt-link-abbreviated" href="mailto:dhobern at GBIF.ORG">dhobern at GBIF.ORG</a> 21/04/2006 9:15 p.m. >>><br>
</div>
<div style="color: rgb(0, 0, 0);">
<div class="Section1">
<p class="MsoNormal"></p>
<p class="MsoNormal"><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB"><o:p></o:p></span></font></p>
<font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB">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 class="MsoNormal"><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB"><o:p> </o:p></span></font></p>
<ol style="margin-top: 0cm;" type="1">
<li class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB">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.<o:p></o:p></span></font> </li>
</ol>
</div>
</div>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<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>
<a class="moz-txt-link-freetext" href="http://www.landcareresearch.co.nz">http://www.landcareresearch.co.nz</a><br>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>
<br>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
-------------------------------------
Roger Hyam
Technical Architect
Taxonomic Databases Working Group
-------------------------------------
<a class="moz-txt-link-freetext" href="http://www.tdwg.org">http://www.tdwg.org</a>
<a class="moz-txt-link-abbreviated" href="mailto:roger at tdwg.org">roger at tdwg.org</a>
+44 1578 722782
-------------------------------------
</pre>
</body>
</html>
More information about the tdwg-tag
mailing list