LSID Software Gap Analysis
Bob Morris
morris.bob at GMAIL.COM
Tue Apr 4 17:56:06 CEST 2006
Ricardo. I need to make plans for June. When will I know if I am invited to
GUID2?
Thanks
Bob
On 4/4/06, Ricardo Scachetti Pereira <ricardo at tdwg.org> wrote:
>
> 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
>
------=_Part_1926_30889065.1144187766971
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Ricardo. I need to make plans for June. When will I know if I am invited to GUID2? <br>Thanks<br>Bob<br><br><br><div><span class="gmail_quote">On 4/4/06, <b class="gmail_sendername">Ricardo Scachetti Pereira</b> <<a href="mailto:ricardo at tdwg.org">
ricardo at tdwg.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> 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>LSIDSoftwareGapAnalysis.<br>(<a href="http://wiki.gbif.org/guidwiki/wikka.php?wakka=LSIDSoftwareGapAnalysis">http://wiki.gbif.org/guidwiki/wikka.php?wakka=LSIDSoftwareGapAnalysis
</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> * To describe and evaluate existing LSID software;<br> * To identify missing components, or components that need to be
<br>rewritten 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> * 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="http://wiki.gbif.org/guidwiki/wikka.php?wakka=LSIDSoftwareGapAnalysis">http://wiki.gbif.org/guidwiki/wikka.php?wakka=LSIDSoftwareGapAnalysis</a>).<br><br> Also, as part of the gap analysis, I started an inventory of LSID
<br>software at<br><a href="http://wiki.gbif.org/guidwiki/wikka.php?wakka=LsidSoftwareInventory">http://wiki.gbif.org/guidwiki/wikka.php?wakka=LsidSoftwareInventory</a>.<br>Feel free to make chances and additions.<br><br>
Thanks a lot,<br><br>Ricardo<br></blockquote></div><br>
More information about the tdwg-tag
mailing list