<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Julien,<div><br></div><div><div><div>On 18 Jun 2012, at 15:51, Julien Cigar wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi Roderic,<br><br>Thanks for your reply.<br><br>But I've almost the same feeling. The more I read about LSIDs, the more I feel that there are no real huge benefits over URLs, .. although it looks like different concept to me: I see more an URL as the location of the resource, and the LSID the identifier of that resource.<br></div></blockquote><div><br></div><div>DOI can do the same thing, or we can design URLs to act much the same way (e.g., by using consistent "slugs" across domains, such as Wikipedia topics or ISBNs).</div><br><blockquote type="cite"><div><br>It's frustrating because at first glances all the models and the "to be compliant you must ..." rules that come with the spec seemed pretty<br><br>Some advantages I see compared to URLs:<br>- the separation of data and metadata (through the .getData / .getMetadata methods and the WSDL files), .. although you could achieve more or less the same by playing on the Accept header of the HTTP request<br></div></blockquote><div><br></div><div>The metadata/data distinction is often messy. What is metadata and what is data? Is the metadata about the data, or about the LSID itself, etc.? Cue much metaphysical discussion (sigh)</div><br><blockquote type="cite"><div>- the versioning<br></div></blockquote><div><br></div><div>To a first approximation nobody uses versions. I have never seen anyone use a version of a GenBank sequences, for example. In general people people want the latest version. One can also create versioned identifiers using other schemes if you really must. </div><br><blockquote type="cite"><div>- the resolution services/discovery services.. although there are a lot of "assuming that..." in the spec<br></div></blockquote><div><br></div><div>They didn't happen...</div><br><blockquote type="cite"><div>- protocol independent<br></div></blockquote><div><br></div><div>I think HTTP pretty much won that argument...</div><div><br></div><br><blockquote type="cite"><div>- other things ... ?<br></div></blockquote><div><br></div><div>LSIDs do have some nice features, but if we step back we see that it's got zero traction outside our community. It's either URLs or DOIs (the later are gaining traction in the data citation world, and are obviously already established in academic publishing). There's a bunch of reasons LSIDs failed to take off, partly technical (they are too hard for most people to get working properly), partly social (pretty much no LSID serves content we can actually do something useful with).</div><div><br></div><div>I'm being a little flippant, but personally I think the last thing we'd want to do as a community is continue to flog a technology that has zero uptake outside biodiversity informatics. it was a nice idea, we tried it, didn't work out too well, let's move on...</div><div><br></div><div>Regards</div><div><br></div><div>Rod</div><div><br></div><div><br></div><div><br></div><br><blockquote type="cite"><div><br>Best regards,<br>Julien<br><br>On 06/18/2012 15:15, Roderic Page wrote:<br><blockquote type="cite">Hi Julien,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Firstly, let me say "run, run away now". Unless you need to support resolving existing LSIDs (e.g., Index Fungorum, IPNI) then I can see no reason to use LSIDs. The future landscape of identifiers is essentially URLs and DOIs. The difference between the two boils down to whether you want your identifiers to have a degree of management or not (you can add management to URLs but the DOI infrastructure for this seems more established).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">My understanding has been that querying the DNS for the SRV record is enough. This is what my LSID tester <a href="http://darwin.zoology.gla.ac.uk/~rpage/lsid/tester/">http://darwin.zoology.gla.ac.uk/~rpage/lsid/tester/</a> <<a href="http://darwin.zoology.gla.ac.uk/%7Erpage/lsid/tester/">http://darwin.zoology.gla.ac.uk/%7Erpage/lsid/tester/</a>> does. Reading the LSID spec I get the sense that, had it been more widely adopted, there was a mechanism to resolve LSID authorities centrally at a server "<a href="http://lsidauthority.org">lsidauthority.org</a> <<a href="http://lsidauthority.org">http://lsidauthority.org</a>>" (option [a]). If this mechanism didn't exist, we would do a regular DNS lookup of the domain in the LSID we were trying to resolve (option [b]). Option (a) was never implemented, so it's option (b).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">That said,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Regards<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Rod<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 18 Jun 2012, at 13:04, Julien Cigar wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Hello,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I'm reading the LSID spec and there are some things that are some things that are a little cloudy to me.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">The spec says that the client should query the DNS for NAPTR records for the domain name "lsid.urn.arpa", but it seems that the URN NID part "lsid" has not been established at IANA (lsid.urn.arpa is unresolvable) ? Why ?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I wondered if it's enough to query the DNS of the "authority identification" part of the LSID (domain name) for a _lsid._tcp SRV record and assume that this entry is a valid resolution service for the given LSID ? If not, what's the proper way to find a resolution service for, let's say, "urn:lsid:blah.my.domain:foo:12345" ?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Thank you<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Best regards,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Julien<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">-- <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">No trees were killed in the creation of this message.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">However, many electrons were terribly inconvenienced.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><jcigar.vcf>_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">tdwg-content mailing list<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a> <<a href="mailto:tdwg-content@lists.tdwg.org">mailto:tdwg-content@lists.tdwg.org</a>><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">---------------------------------------------------------<br></blockquote><blockquote type="cite">Roderic Page<br></blockquote><blockquote type="cite">Professor of Taxonomy<br></blockquote><blockquote type="cite">Institute of Biodiversity, Animal Health and Comparative Medicine<br></blockquote><blockquote type="cite">College of Medical, Veterinary and Life Sciences<br></blockquote><blockquote type="cite">Graham Kerr Building<br></blockquote><blockquote type="cite">University of Glasgow<br></blockquote><blockquote type="cite">Glasgow G12 8QQ, UK<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Email: <a href="mailto:r.page@bio.gla.ac.uk">r.page@bio.gla.ac.uk</a> <<a href="mailto:r.page@bio.gla.ac.uk">mailto:r.page@bio.gla.ac.uk</a>><br></blockquote><blockquote type="cite">Tel: +44 141 330 4778<br></blockquote><blockquote type="cite">Fax: +44 141 330 2792<br></blockquote><blockquote type="cite">Skype: rdmpage<br></blockquote><blockquote type="cite">AIM: <a href="mailto:rodpage1962@aim.com">rodpage1962@aim.com</a> <<a href="mailto:rodpage1962@aim.com">mailto:rodpage1962@aim.com</a>><br></blockquote><blockquote type="cite">Facebook: <a href="http://www.facebook.com/profile.php?id=1112517192">http://www.facebook.com/profile.php?id=1112517192</a><br></blockquote><blockquote type="cite">Twitter: <a href="http://twitter.com/rdmpage">http://twitter.com/rdmpage</a><br></blockquote><blockquote type="cite">Blog: <a href="http://iphylo.blogspot.com">http://iphylo.blogspot.com</a><br></blockquote><blockquote type="cite">Home page: <a href="http://taxonomy.zoology.gla.ac.uk/rod/rod.html">http://taxonomy.zoology.gla.ac.uk/rod/rod.html</a><br></blockquote><blockquote type="cite"><br></blockquote><br><br>-- <br>No trees were killed in the creation of this message.<br>However, many electrons were terribly inconvenienced.<br><br><span><jcigar.vcf></span></div></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">---------------------------------------------------------<br>Roderic Page<br>Professor of Taxonomy<br>Institute of Biodiversity, Animal Health and Comparative Medicine<br>College of Medical, Veterinary and Life Sciences<br>Graham Kerr Building<br>University of Glasgow<br>Glasgow G12 8QQ, UK<br><br>Email: <a href="mailto:r.page@bio.gla.ac.uk">r.page@bio.gla.ac.uk</a><br>Tel: +44 141 330 4778<br>Fax: +44 141 330 2792</div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Skype: rdmpage<br>AIM: <a href="mailto:rodpage1962@aim.com">rodpage1962@aim.com</a><br>Facebook: <a href="http://www.facebook.com/profile.php?id=1112517192">http://www.facebook.com/profile.php?id=1112517192</a><br>Twitter: <a href="http://twitter.com/rdmpage">http://twitter.com/rdmpage</a><br>Blog: <a href="http://iphylo.blogspot.com">http://iphylo.blogspot.com</a><br>Home page: <a href="http://taxonomy.zoology.gla.ac.uk/rod/rod.html">http://taxonomy.zoology.gla.ac.uk/rod/rod.html</a></div></span></span>
</div>
<br></div></body></html>