<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.5730.11" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Hi all </DIV>
<DIV> </DIV>
<DIV>I have been thinking about the LSID resolvers that have been set up within the TDWG community so far. Some of these resolvers have evolved from the prototype/experimental stage of the GUID and TAG subgroups. </DIV>
<DIV> </DIV>
<DIV>There are also a variety of resolvers that no longer seem to be up and running, eg LSIDs at <A href="http://lsid.biopathways.org/authorities.shtml">http://lsid.biopathways.org/authorities.shtml</A> </DIV>
<DIV>Most of the example LSIDs at Rod Page's tester page fail to some degree - <A href="http://darwin.zoology.gla.ac.uk/~rpage/lsid/tester/">http://darwin.zoology.gla.ac.uk/~rpage/lsid/tester/</A></DIV>
<DIV> </DIV>
<DIV>Also, different metadata is being returned for each resolver.</DIV>
<DIV> </DIV>
<DIV>I have had comments that these LSID resolvers are not working, and "isn't the intention of LSIDs for them to persist forever and always be available".</DIV>
<DIV> </DIV>
<DIV>I wonder if one of our goals for the next year should be to look at these existing resolvers and decide on / announce / commit to their continued existence, metadata formats, etc.</DIV>
<DIV> </DIV>
<DIV>I think the following probably need to be addressed:</DIV>
<DIV>- decide if each resolver is experimental or permanent - perhaps we need some standard "metadata" about a resolver that describes the intention of that resolver (eg whether it is experimental or not)</DIV>
<DIV>- decide if the resolver should be taken offline to avoid confusion</DIV>
<DIV>- the metadata format for similar resolvers, eg resolvers dealing with Taxon Name objetcs, or Taxon Concepts, or Specimens, etc. Does this need to be the same for each resolver? always RDF? In some cases a single class of the LSID vocabularies have been implemented, in other cases a mixture of several classes and properties. Do wee need some guidelines, best practices for the "reccommended" fields? This obviously requires further work with associated ontologies.</DIV>
<DIV> </DIV>
<DIV>Any thoughts?</DIV>
<DIV> </DIV>
<DIV>Kevin</DIV></BODY></HTML>