Thoughts
Donald Hobern
dhobern at GBIF.ORG
Mon Feb 13 12:37:12 CET 2006
Bob,
I'm sorry that the conclusions of the meeting still seem so unclear. I'll
try to summarise a few points of importance. Please come back with your
thoughts/exasperation on any or all of these.
1. The general conclusion of the meeting was that an RDF-based model
was desirable for content as well as description (recognising that in most
of our existing standards the distinction is blurred). However we expect to
use the next few months to clarify what will work for our needs and I can
still foresee several possible variant solutions if we are not satisfied
with a full RDF-based approach (e.g. RDF Dublin Core for metadata and
tighter formalization of how we provide the rest of the information as data,
including use of versions; or, metadata containing a URL to retrieve our
content data from a DiGIR/BioCASe/TAPIR provider etc.; or, working with IBM
to introduce a modification to the LSID specification; etc.).
2. We recognised that a recast of TDWG standards into an RDF-based
representation was not trivial, but a change at least somewhat like this
(from large document-based models to reusable data objects) is in any case
needed for many other reasons (better re-use, less churn from versioning;
simpler extensibility, etc.).
3. The GUID workshop is not a totally isolated activity. The new TDWG
Architecture Group (TAG) will be meeting separately to consider how to
standardise our data modeling and integrate better with other standards
(such as WFS and RDF). It would be a major step forward for us to model our
standards in a framework that makes our OO-model explicit (rather than
relying on unstated implications of structure) and where it is also easy for
us to extend it with additional concepts/properties as required. I hope
that we can agree our actual approach through the TAG discussions.
<personalAside>For what it's worth, my own vision up to now had been for
something like UML modeling followed by simultaneous generation of OWL-Lite
and XML Schema definitions for each data class (the XML Schema
representation being regarded as a convenience tool for generating a
document that - I hope - would perfectly correspond to the more semantically
clear OWL-Lite document). The advantage of leap-frogging RDF to some form
of OWL is that we could have the semantic foundation to our models but still
retain something that has a familiar structure.</personalAside>
4. It is important to note that the suggested prototype activities are
prefixed, "The potential prototypes.". Right now I would expect several of
these only to test out the assignment of LSIDs to data objects and their use
for retrieving the objects independently of full LSID resolution or RDF
mapping. I believe that the first real LSID-resolver test is likely to be
with Darwin Core (which is just about RDF-ready immediately). We want to
use the next few months to play around with LSIDs in whatever areas we can.
Part of the purpose is to allow us to understand what software we need to
develop before trying it on a larger scale. It will be part of my job to
find ways to get such software developed.
By the way, the GUID wiki is open for comments. You can add pages to the
wiki, or use the comments link at the bottom of the page (these are
WikkaWakka comments that are shown like a set of footnotes). As an
alternative I have added a new page for comments on this report:
http://wiki.gbif.org/guidwiki/wikka.php?wakka=GUID1ReportComments
Thanks as ever for your input,
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 Bob Morris
Sent: 13 February 2006 05:09
To: TDWG-GUID at LISTSERV.NHM.KU.EDU
Subject: Re: Thoughts
I'm quite confused from the meeting reports whether there was some argument
accepted that LSID metadata in RDF should represent the \content/ of the
current concerns of TDWG, including TCS, DC, ABCD, SDD, and the impending
new groups, or merely \describe/ the databases against which answers are
rendered in those content standards. For example, if a taxon concept is
given an LSID, is the metadata returned expected to be a replacement for the
current XML constrained by TCS? RDF certainly can encode a taxon concept
and address the relations it encodes, but I'm unaware of applications of
LSID metadata of objects in a database where the datum is encoded, though in
many cases RDF could rationally make a claim to do so. I agree with
Sally:Where's the robust, widely accepted killer app?
I hate long email posts, and the present rules of the GUID wiki don't yet
permit comment, so I have posted something on the SDD Wiki. I'll move it
when the GUID wiki is open.
http://wiki.cs.umb.edu/twiki/bin/view/SDD/RDFConsideredHarmful
Depending on the resolutiuon to my cofusion expressed in the first
paragraph, I am somewhere been vigorously opposed and neutral on RDF, for
reasons in the above linked RDFConsideredHarmful.
I'm also amazed that a whole crew of volunteers seem to be persuaded (or
appointed) to drop everything they are doing and take on what may or may not
be a substantial piece of software engineering to in the next three months.
Either there were a lot of persuasive arguments that I couldn't see in what
I've been through so far in the report, or somewhere there is sitting an
LSID resolver package that just needs a little configuration. mod_LSID??? I
guess I'll learn which from Greg Riccardi. I sure hope it's the latter.
Bob
On 2/12/06, Roderic Page <r.page at bio.gla.ac.uk> wrote:
For my take on McCool's articles see
http://iphylo.blogspot.com/2006/02/rob-mccool-on-rethinking-semantic-
web.html
Regards
Rod
On 11 Feb 2006, at 20:44, Bob Morris wrote:
>
> Rethinking the semantic Web. Part I
> McCool, R.;
> Internet Computing, IEEE
> Volume 9, Issue 6, Nov.-Dec. 2005 Page(s):88, 86 - 87
> Abstract:
>
> The semantic Web is a compelling vision, in which the World Wide Web
> will include a notion of meaning in data and services. Intelligent
> agents will exchange information and rules for how to interact with
> that information, with or without human intervention; appointments
> will be automatically scheduled; and automated agents will select and
> invoke services. Information will be easy to find without depending
> solely on keywords. In part one of this column, the author propose
> several reasons that this vision hasn't yet been adopted despite
> substantial research funding in the US and European Union (EU). These
> reasons will provide the foundation for a new approach, which propose
> in part two.
>
> McCool is one of the architects of a number of RDF and RDF related
> systems. This doesn't bear very much on LSID vs. something else, but
> it does argue that RDF is burdened by its weight and hasn't achieved
> certain of its aims. A question arises about whether this has
> implications for other applications that have ontological overtones,
> including many of TDWGs.
>
> The second columm is in the January issue of the same journal.
>
>
>
>
> On 2/10/06, Sally Hinchcliffe < S.Hinchcliffe at kew.org> wrote:Hi Rod,
>> Your comment facility is down or I would have added this to the blog
>> ...
>> I think that most of the talk re serving XML from LSIDs was by way of
>> an upgrade path rather than as a final goal. As you say (rightly or
>> wrongly) the community has put a lot of effort into XML schemas and
>> it worried me (and others) that tying LSIDs to RDF might mean that
>> the LSID baby got thrown out with the RDF bathwater as the community
>> rejected it wholesale. But I was persuaded this wouldn't happen and
>> now I face some scepticism here at Kew about the benefits of RDF so a
>> killer app would be good...
>>
>> On the meeting itself, yes it was frustrating (and interesting and
>> useful as well) and it struck me on my return that we might have got
>> further had we had some professional (and neutral) facilitators - not
>> to say that the chairs didn't do a good job getting us all to a
>> decision in the end, but that we are all (me included) so parti pris
>> and bound up in the subject that herding cats didn't even come close
>> ... For the next meeting the decisions will be harder and more
>> concrete and there will be a lot to decide. It might help having
>> people who know how to facilitate useful debate and close off some of
>> the blind alleys and circular pathways we have a tendency to wander
>> into
>> Sally
>>
>>
>>
>> > For those at the workshop, it was great to meet you and to discuss
>> > GUIDs. I've posted a personal view on proceedings on one of my
>> blogs:
>> > http://iphylo.blogspot.com/2006/02/globally-unique-identifiers.html
>> .
>> > Comments are welcome.
>> >
>> > Regards
>> >
>> > Rod
>> >
>> >
>> ----------------------------------------------------------------------
>> --
>> > ----------------------------------------
>> > Professor Roderic D. M. Page
>> > Editor, Systematic Biology
>> > DEEB, IBLS
>> > Graham Kerr Building
>> > University of Glasgow
>> > Glasgow G12 8QP
>> > United Kingdom
>> >
>> > Phone:+44 141 330 4778
>> > Fax:+44 141 330 2792
>> > email: r.page at bio.gla.ac.uk
>> > web: http://taxonomy.zoology.gla.ac.uk/rod/rod.html
>> > reprints: http://taxonomy.zoology.gla.ac.uk/rod/pubs.html
>> >
>> > Subscribe to Systematic Biology through the Society of Systematic
>> > Biologists Website: <http://systematicbiology.org>
http://systematicbiology.org
>> > Search for taxon names at
>> http://darwin.zoology.gla.ac.uk/~rpage/portal/
>> > Find out what we know about a species at http://ispecies.org
>>
>> *** Sally Hinchcliffe
>> *** Computer section, Royal Botanic Gardens, Kew
>> *** tel: +44 (0)20 8332 5708
>> *** S.Hinchcliffe at rbgkew.org.uk
>>
------------------------------------------------------------------------
----------------------------------------
Professor Roderic D. M. Page
Editor, Systematic Biology
DEEB, IBLS
Graham Kerr Building
University of Glasgow
Glasgow G12 8QP
United Kingdom
Phone: +44 141 330 4778
Fax: +44 141 330 2792
email: r.page at bio.gla.ac.uk
web: http://taxonomy.zoology.gla.ac.uk/rod/rod.html
reprints: http://taxonomy.zoology.gla.ac.uk/rod/pubs.html
Subscribe to Systematic Biology through the Society of Systematic
Biologists Website: http://systematicbiology.org
Search for taxon names at http://darwin.zoology.gla.ac.uk/~rpage/portal/
Find out what we know about a species at http://ispecies.org
___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo!
Security Centre. http://uk.security.yahoo.com
------=_NextPart_000_001A_01C6309A.36C53AF0
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]--><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"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"place"/>
<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;}
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;}
/* List Definitions */
@list l0
{mso-list-id:1291596021;
mso-list-type:hybrid;
mso-list-template-ids:-1097852164 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 l0:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</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'>Bob,<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'>I’m sorry that the =
conclusions of
the meeting still seem so unclear. I’ll try to summarise a =
few
points of importance. Please come back with your =
thoughts/exasperation on
any or all of these.<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>
<ol style=3D'margin-top:0cm' start=3D1 type=3D1>
<li class=3DMsoNormal style=3D'color:navy;mso-list:l0 level1 =
lfo1'><font size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>The
general conclusion of the meeting was that an RDF-based model was
desirable for content as well as description (recognising that in =
most of
our existing standards the distinction is blurred). However =
we
expect to use the next few months to clarify what will work for our =
needs
and I can still foresee several possible variant solutions if we =
are not
satisfied with a full RDF-based approach (e.g. RDF Dublin Core for
metadata and tighter formalization of how we provide the rest of =
the
information as data, including use of versions; or, metadata =
containing a
URL to retrieve our content data from a DiGIR/BioCASe/TAPIR =
provider etc.;
or, working with IBM to introduce a modification to the LSID
specification; etc.).</span></font> <font size=3D2 =
face=3DArial><span
=
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></l=
i>
<li class=3DMsoNormal style=3D'color:navy;mso-list:l0 level1 =
lfo1'><font size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>We
recognised that a recast of TDWG standards into an RDF-based
representation was not trivial, but a change at least somewhat like =
this
(from large document-based models to reusable data objects) is in =
any case
needed for many other reasons (better re-use, less churn from =
versioning;
simpler extensibility, etc.).</span></font> <font size=3D2 =
face=3DArial><span
=
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></l=
i>
<li class=3DMsoNormal style=3D'color:navy;mso-list:l0 level1 =
lfo1'><font size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>The
GUID workshop is not a totally isolated activity. The new =
TDWG
Architecture Group (TAG) will be meeting separately to consider how =
to
standardise our data modeling and integrate better with other =
standards
(such as WFS and RDF). It would be a major step forward for =
us to
model our standards in a framework that makes our OO-model explicit
(rather than relying on unstated implications of structure) and =
where it
is also easy for us to extend it with additional =
concepts/properties as
required. I hope that we can agree our actual approach =
through the
TAG discussions. <personalAside>For what it’s =
worth, my
own vision up to now had been for something like UML modeling =
followed by
simultaneous generation of OWL-Lite and XML Schema definitions for =
each data
class (the XML Schema representation being regarded as a =
convenience tool
for generating a document that – I hope – would =
perfectly
correspond to the more semantically clear OWL-Lite document). =
The
advantage of leap-frogging RDF to some form of OWL is that we could =
have
the semantic foundation to our models but still retain something =
that has
a familiar structure.</personalAside></span></font> <font =
size=3D2
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></l=
i>
<li class=3DMsoNormal style=3D'color:navy;mso-list:l0 level1 =
lfo1'><font size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>It
is important to note that the suggested prototype activities are =
prefixed,
“The <i><span =
style=3D'font-style:italic'>potential</span></i>
prototypes…”. Right now I would expect several of =
these
only to test out the assignment of LSIDs to data objects and their =
use for
retrieving the objects independently of full LSID resolution or RDF
mapping. I believe that the first real LSID-resolver test is =
likely
to be with Darwin Core (which is just about RDF-ready immediately).
We want to use the next few months to play around with LSIDs =
in
whatever areas we can. Part of the purpose is to allow us to
understand what software we need to develop before trying it on a =
larger
scale. It will be part of my job to find ways to get such =
software
developed.</span></font> <font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p></o:p></span></font></li>
</ol>
<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'>By the way, the GUID wiki is open =
for
comments. You can add pages to the wiki, or use the comments link =
at the
bottom of the page (these are WikkaWakka comments that are shown like a =
set of
footnotes). As an alternative I have added a new page for comments =
on
this report:<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'><a
href=3D"http://wiki.gbif.org/guidwiki/wikka.php?wakka=3DGUID1ReportCommen=
ts"
title=3D"http://wiki.gbif.org/guidwiki/wikka.php?wakka=3DGUID1ReportComme=
nts">http://wiki.gbif.org/guidwiki/wikka.php?wakka=3DGUID1ReportComments<=
/a><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'>Thanks as ever for your =
input,<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'>Donald</span></font><o:p></o:p></p>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'> <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 Copenhagen, Denmark<br>
Tel: +45-35321483 Mobile: +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><st1:PersonName w:st=3D"on">Bob =
Morris</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 13 February 2006 =
05:09<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: =
Thoughts</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 class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>I'm =
quite confused
from the meeting reports whether there was some argument accepted that =
LSID
metadata in RDF should represent the \content/ of the current concerns =
of TDWG,
including TCS, DC, ABCD, SDD, and the impending new groups, or merely =
\describe/
the databases against which answers are rendered in those content =
standards.
For example, if a taxon concept is given an LSID, is the metadata =
returned
expected to be a replacement for the current XML constrained by TCS? =
RDF
certainly can encode a taxon concept and address the relations it =
encodes, but
I'm unaware of applications of LSID metadata of objects in a database =
where the
datum is encoded, though in many cases RDF could rationally make a claim =
to do
so. I agree with Sally:Where's the robust, widely accepted killer app? =
<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>I hate long =
email posts,
and the present rules of the GUID wiki don't yet permit comment, so I =
have
posted something on the SDD Wiki. I'll move it when the GUID wiki is =
open. <a
href=3D"http://wiki.cs.umb.edu/twiki/bin/view/SDD/RDFConsideredHarmful">h=
ttp://wiki.cs.umb.edu/twiki/bin/view/SDD/RDFConsideredHarmful</a><br>
<br>
Depending on the resolutiuon to my cofusion expressed in the first =
paragraph, I
am somewhere been vigorously opposed and neutral on RDF, for reasons in =
the
above linked RDFConsideredHarmful. <br>
<br>
I'm also amazed that a whole crew of volunteers seem to be persuaded (or
appointed) to drop everything they are doing and take on what may or may =
not be
a substantial piece of software engineering to in the next three months. =
Either
there were a lot of persuasive arguments that I couldn't see in what =
I've been
through so far in the report, or somewhere there is sitting an LSID =
resolver
package that just needs a little configuration. mod_LSID??? I guess I'll =
learn
which from Greg Riccardi. I sure hope it's the latter. <br>
<br>
Bob<o:p></o:p></span></font></p>
<div>
<p class=3DMsoNormal><span class=3Dgmailquote><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>On 2/12/06, <b><span =
style=3D'font-weight:bold'>Roderic
Page</span></b> <<a =
href=3D"mailto:r.page at bio.gla.ac.uk">r.page at bio.gla.ac.uk</a>>
wrote:</span></font></span><o:p></o:p></p>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>For my take on McCool's articles see<br>
<a =
href=3D"http://iphylo.blogspot.com/2006/02/rob-mccool-on-rethinking-seman=
tic-">http://iphylo.blogspot.com/2006/02/rob-mccool-on-rethinking-semanti=
c-</a><br>
web.html<br>
<br>
<br>
Regards <br>
<br>
Rod<br>
<br>
On 11 Feb 2006, at 20:44, <st1:PersonName w:st=3D"on">Bob =
Morris</st1:PersonName>
wrote:<br>
<br>
><br>
> Rethinking the semantic Web. Part I<br>
> McCool, R.;<br>
> Internet Computing, IEEE<br>
> Volume 9, Issue 6, Nov.-Dec. 2005 Page(s):88, =
86 -
87 <br>
> Abstract:<br>
><br>
> The semantic Web is a compelling vision, in which the =
World
Wide Web<br>
> will include a notion of meaning in data and services. =
Intelligent<br>
> agents will exchange information and rules for how to interact with =
<br>
> that information, with or without human intervention; =
appointments<br>
> will be automatically scheduled; and automated agents will select =
and<br>
> invoke services. Information will be easy to find without depending =
<br>
> solely on keywords. In part one of this column, the author =
propose<br>
> several reasons that this vision hasn't yet been adopted =
despite<br>
> substantial research funding in the <st1:country-region =
w:st=3D"on"><st1:place
w:st=3D"on">US</st1:place></st1:country-region> and European Union =
(EU). These <br>
> reasons will provide the foundation for a new approach, which =
propose<br>
> in part two.<br>
><br>
> McCool is one of the architects of a number of RDF and RDF =
related<br>
> systems. This doesn't bear very much on LSID vs. something else, =
but <br>
> it does argue that RDF is burdened by its weight and hasn't =
achieved<br>
> certain of its aims. A question arises about whether this has<br>
> implications for other applications that have ontological =
overtones, <br>
> including many of TDWGs.<br>
><br>
> The second columm is in the January issue of the same journal.<br>
><br>
><br>
><br>
><br>
> On 2/10/06, Sally Hinchcliffe < <a =
href=3D"mailto:S.Hinchcliffe at kew.org">S.Hinchcliffe at kew.org</a>>
wrote:Hi Rod,<br>
>> Your comment facility is down or I would have added this to the =
blog<br>
>> ...<br>
>> I think that most of the talk re serving XML from LSIDs was by =
way of <br>
>> an upgrade path rather than as a final goal. As you say =
(rightly or<br>
>> wrongly) the community has put a lot of effort into XML schemas =
and<br>
>> it worried me (and others) that tying LSIDs to RDF might mean =
that <br>
>> the LSID baby got thrown out with the RDF bathwater as the =
community<br>
>> rejected it wholesale. But I was persuaded this wouldn't happen =
and<br>
>> now I face some scepticism here at <st1:place =
w:st=3D"on">Kew</st1:place>
about the benefits of RDF so a <br>
>> killer app would be good...<br>
>><br>
>> On the meeting itself, yes it was frustrating (and interesting =
and<br>
>> useful as well) and it struck me on my return that we might =
have got<br>
>> further had we had some professional (and neutral) facilitators =
- not <br>
>> to say that the chairs didn't do a good job getting us all to =
a<br>
>> decision in the end, but that we are all (me included) so parti =
pris<br>
>> and bound up in the subject that herding cats didn't even come =
close <br>
>> ... For the next meeting the decisions will be harder and =
more<br>
>> concrete and there will be a lot to decide. It might help =
having<br>
>> people who know how to facilitate useful debate and close off =
some of <br>
>> the blind alleys and circular pathways we have a tendency to =
wander<br>
>> into<br>
>> Sally<br>
>><br>
>><br>
>><br>
>> > For those at the workshop, it was great to meet you and to
discuss <br>
>> > GUIDs. I've posted a personal view on proceedings on one =
of my<br>
>> blogs:<br>
>> > <a
href=3D"http://iphylo.blogspot.com/2006/02/globally-unique-identifiers.ht=
ml">http://iphylo.blogspot.com/2006/02/globally-unique-identifiers.html
</a><br>
>> .<br>
>> > Comments are welcome.<br>
>> ><br>
>> > Regards<br>
>> ><br>
>> > Rod<br>
>> ><br>
>> ><br>
>> =
----------------------------------------------------------------------
<br>
>> --<br>
>> > ----------------------------------------<br>
>> > Professor Roderic D. M. Page<br>
>> > Editor, Systematic Biology<br>
>> > DEEB, IBLS<br>
>> > <st1:PlaceName w:st=3D"on">Graham</st1:PlaceName> =
<st1:PlaceName
w:st=3D"on">Kerr</st1:PlaceName> <st1:PlaceType =
w:st=3D"on">Building</st1:PlaceType>
<br>
>> > <st1:place w:st=3D"on"><st1:PlaceType =
w:st=3D"on">University</st1:PlaceType>
of <st1:PlaceName w:st=3D"on">Glasgow</st1:PlaceName></st1:place><br>
>> > <st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Glasgow</st1:place></st1:City>
G12 8QP<br>
>> > <st1:country-region w:st=3D"on"><st1:place =
w:st=3D"on">United Kingdom</st1:place></st1:country-region><br>
>> ><br>
>> > Phone:+44 141 330 4778<br>
>> > Fax:+44 141 330 2792<br>
>> > email: <a =
href=3D"mailto:r.page at bio.gla.ac.uk">r.page at bio.gla.ac.uk</a><br>
>> > web: <a =
href=3D"http://taxonomy.zoology.gla.ac.uk/rod/rod.html">http://taxonomy.z=
oology.gla.ac.uk/rod/rod.html</a><br>
>> > reprints: <a
href=3D"http://taxonomy.zoology.gla.ac.uk/rod/pubs.html">http://taxonomy.=
zoology.gla.ac.uk/rod/pubs.html</a><br>
>> ><br>
>> > Subscribe to Systematic Biology through the Society of =
Systematic<br>
>> > Biologists Website:<a =
href=3D"http://systematicbiology.org">
http://systematicbiology.org</a><br>
>> > Search for taxon names at<br>
>> <a =
href=3D"http://darwin.zoology.gla.ac.uk/~rpage/portal/">http://darwin.zoo=
logy.gla.ac.uk/~rpage/portal/</a><br>
>> > Find out what we know about a species at <a
href=3D"http://ispecies.org">http://ispecies.org</a><br>
>><br>
>> *** Sally Hinchcliffe<br>
>> *** Computer section, <st1:PlaceName =
w:st=3D"on">Royal</st1:PlaceName> <st1:PlaceType
w:st=3D"on">Botanic Gardens</st1:PlaceType>, <st1:place =
w:st=3D"on">Kew</st1:place><br>
>> *** tel: +44 (0)20 8332 5708<br>
>> *** <a =
href=3D"mailto:S.Hinchcliffe at rbgkew.org.uk">S.Hinchcliffe at rbgkew.org.uk</=
a><br>
>><br>
------------------------------------------------------------------------<=
br>
----------------------------------------<br>
Professor Roderic D. M. Page<br>
Editor, Systematic Biology <br>
DEEB, IBLS<br>
<st1:place w:st=3D"on"><st1:PlaceName w:st=3D"on">Graham</st1:PlaceName> =
<st1:PlaceName
w:st=3D"on">Kerr</st1:PlaceName> <st1:PlaceType =
w:st=3D"on">Building</st1:PlaceType></st1:place><br>
<st1:place w:st=3D"on"><st1:PlaceType =
w:st=3D"on">University</st1:PlaceType> of <st1:PlaceName
w:st=3D"on">Glasgow</st1:PlaceName></st1:place><br>
<st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Glasgow</st1:place></st1:City> G12 8QP<br>
<st1:country-region w:st=3D"on"><st1:place w:st=3D"on">United =
Kingdom</st1:place></st1:country-region><br>
<br>
Phone: +44 141 330 4778<br>
Fax: +44 141 330 2792<br>
email: <a =
href=3D"mailto:r.page at bio.gla.ac.uk">r.page at bio.gla.ac.uk
</a><br>
web: <a
href=3D"http://taxonomy.zoology.gla.ac.uk/rod/rod.html">http://taxonomy.z=
oology.gla.ac.uk/rod/rod.html</a><br>
reprints: <a =
href=3D"http://taxonomy.zoology.gla.ac.uk/rod/pubs.html">http://taxonomy.=
zoology.gla.ac.uk/rod/pubs.html
</a><br>
<br>
Subscribe to Systematic Biology through the Society of Systematic<br>
Biologists Website: <a =
href=3D"http://systematicbiology.org">http://systematicbiology.org</a><br=
>
Search for taxon names at <a
href=3D"http://darwin.zoology.gla.ac.uk/~rpage/portal/">http://darwin.zoo=
logy.gla.ac.uk/~rpage/portal/</a><br>
Find out what we know about a species at <a =
href=3D"http://ispecies.org">http://ispecies.org</a><br>
<br>
<br>
<br>
<br>
___________________________________________________________ <br>
To help you stay safe and secure online, we've developed the all new =
Yahoo!
Security Centre. <a =
href=3D"http://uk.security.yahoo.com">http://uk.security.yahoo.com</a><o:=
p></o:p></span></font></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>
</div>
</body>
</html>
More information about the tdwg-tag
mailing list