LSID Software Gap Analysis
Kevin Richards
RichardsK at LANDCARERESEARCH.CO.NZ
Wed Apr 5 09:16:14 CEST 2006
Ricardo
Do you think this analysis should include a gap analysis of RDF
software as well , or would it be best to keep this separate?
I think this is probably a more contentious issue - ie some doubts
about RDF over XML. I have found setting up an LSID resolver/authority
reasonably straight forward but trying to implement the services using
RDF has been a steep learning curve (and limited software/tools to
help).
I'll add more later.
Kevin
>>> ricardo at TDWG.ORG 5/04/2006 6:49 a.m. >>>
Hi all,
I wanted to invite you to help with the discussion and outcomes of
one of the task groups formed during GUID-1 workshop, the
LSIDSoftwareGapAnalysis.
(http://wiki.gbif.org/guidwiki/wikka.php?wakka=LSIDSoftwareGapAnalysis).
The goal of this group is to perform a gap analysis of LSID
software. That is, we want to evaluate what the current situation in
terms of available LSID software is, what would be an ideal situation
and how to get from former to the later.
In more simple terms, we are interested in performing the
following
tasks:
* To describe and evaluate existing LSID software;
* To identify missing components, or components that need to be
rewritten or refactored; and
* To devise a plan to implement, rewrite or refactor these
components;
We then plan on execute that plan above, probably after
GUID2Workshop.
I believe now is a good time to start this process because many
other GUID task groups have gained invaluable experience in
implemented
LSID resolvers or are in the process of setting one up. We would like
to
tap into that experience to identify limitations on the current LSID
software packages and identify new components that need to be
developed.
If you have set up an LSID resolver or have experience with the
matter, we would like to know from you:
* Besides the existing LSID software, what components did you have
to develop to make your LSID resolver work?
* What tasks were more time consuming in setting up your LSID
resolver?
* Have you identified any new components that would have helped
you
to set up your LSID resolver? Please describe it.
* Have you found any components that were hard or ackward to use?
What modifications would you propose?
* Have you found any problems or bugs in the existing components?
Please report them.
Please, respond either directly to me, to the list, or add your
comments to the respective wiki page
(http://wiki.gbif.org/guidwiki/wikka.php?wakka=LSIDSoftwareGapAnalysis).
Also, as part of the gap analysis, I started an inventory of LSID
software at
http://wiki.gbif.org/guidwiki/wikka.php?wakka=LsidSoftwareInventory.
Feel free to make chances and additions.
Thanks a lot,
Ricardo
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
--=__PartF2D7890E.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Description: HTML
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2800.1522" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Ricardo</DIV>
<DIV> </DIV>
<DIV>Do you think this analysis should include a gap analysis of RDF =
software as well , or would it be best to keep this separate?</DIV>
<DIV>I think this is probably a more contentious issue - ie some doubts =
about RDF over XML. I have found setting up an LSID resolver/authorit=
y reasonably straight forward but trying to implement the services using =
RDF has been a steep learning curve (and limited software/tools to =
help).</DIV>
<DIV>I'll add more later.</DIV>
<DIV> </DIV>
<DIV>Kevin</DIV>
<DIV><BR>>>> ricardo at TDWG.ORG 5/04/2006 6:49 a.m. >>><BR>=
</DIV>
<DIV style=3D"COLOR: #000000"> Hi all,<BR><BR>  =
; I wanted to invite you to help with the discussion and outcomes =
of<BR>one of the task groups formed during GUID-1 workshop, the<BR>LSIDSoft=
wareGapAnalysis.<BR>(<A href=3D"http://wiki.gbif.org/guidwiki/wikka.php?wak=
ka=3DLSIDSoftwareGapAnalysis).">http://wiki.gbif.org/guidwiki/wikka.php?wak=
ka=3DLSIDSoftwareGapAnalysis).</A><BR><BR> The goal of =
this group is to perform a gap analysis of LSID<BR>software. That is, we =
want to evaluate what the current situation in<BR>terms of available LSID =
software is, what would be an ideal situation<BR>and how to get from =
former to the later.<BR><BR> In more simple terms, we =
are interested in performing the following<BR>tasks:<BR><BR> &nb=
sp; * To describe and evaluate existing LSID software;<BR>  =
; * To identify missing components, or components that need to be<BR>rewrit=
ten or refactored; and<BR> * To devise a plan to =
implement, rewrite or refactor these components;<BR><BR> =
We then plan on execute that plan above, probably after GUID2Workshop.<BR><=
BR> I believe now is a good time to start this process =
because many<BR>other GUID task groups have gained invaluable experience =
in implemented<BR>LSID resolvers or are in the process of setting one up. =
We would like to<BR>tap into that experience to identify limitations on =
the current LSID<BR>software packages and identify new components that =
need to be developed.<BR><BR> If you have set up an LSID =
resolver or have experience with the<BR>matter, we would like to know from =
you:<BR><BR> * Besides the existing LSID software, what =
components did you have<BR>to develop to make your LSID resolver work?<BR>&=
nbsp; * What tasks were more time consuming in setting up your =
LSID resolver?<BR> * Have you identified any new =
components that would have helped you<BR>to set up your LSID resolver? =
Please describe it.<BR> * Have you found any components =
that were hard or ackward to use?<BR>What modifications would you =
propose?<BR> * Have you found any problems or bugs in =
the existing components?<BR>Please report them.<BR><BR> =
Please, respond either directly to me, to the list, or add your<BR>comments=
to the respective wiki page<BR>(<A href=3D"http://wiki.gbif.org/guidwiki/w=
ikka.php?wakka=3DLSIDSoftwareGapAnalysis).">http://wiki.gbif.org/guidwiki/w=
ikka.php?wakka=3DLSIDSoftwareGapAnalysis).</A><BR><BR> =
Also, as part of the gap analysis, I started an inventory of LSID<BR>softwa=
re at<BR><A href=3D"http://wiki.gbif.org/guidwiki/wikka.php?wakka=3DLsidSof=
twareInventory.">http://wiki.gbif.org/guidwiki/wikka.php?wakka=3DLsidSoftwa=
reInventory.</A><BR>Feel free to make chances and additions.<BR><BR> &=
nbsp; Thanks a lot,<BR><BR>Ricardo<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