tag:blogger.com,1999:blog-16081779.post4199161528943628611..comments2023-10-28T09:24:38.420+01:00Comments on iPhylo: Rethinking LSIDs versus HTTP URIRoderic Pagehttp://www.blogger.com/profile/00269598293846172649noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-16081779.post-89797335703665070332007-07-25T14:13:00.000+01:002007-07-25T14:13:00.000+01:00Hi Rod,As usually I agree with nearly everything y...Hi Rod,<BR/><BR/>As usually I agree with nearly everything you say but...<BR/><BR/>I think you say that it is OK for there to be a URL and a sw-unresolvable URN like a DOI or LSID for an object. I agree fully with this.<BR/><BR/>Now as all these identifiers are opaque to the client the fact that the URL may embed the LSID/DOI doesn't matter. The client should not be able to differentiate between a URL that is a proxied LSID and a URL that isn't. It is just an http URL.<BR/><BR/>So I don't see how you can logically criticize the use of LSID proxies and simultaneously support multiple GUIDs. They are functionally indistinguishable from the client side.<BR/><BR/>[BTW: As we (TDWG) also advocate a minimum HTTP GET binding for LSIDs there is an interesting 'feature'. Any LSID will also have an associated, impermanent URL type GUID for its metadata i.e. the URL the getMetadata() method is bound to. There would be nothing to stop people using this in their metadata to differentiate between assertions made about the metadata itself and the object in question c.f. W3C HttpRange 14 debate. I think this is actually something to be encouraged]<BR/><BR/>All the best,<BR/><BR/>RogerRoger Hyamhttps://www.blogger.com/profile/02878923877501463025noreply@blogger.comtag:blogger.com,1999:blog-16081779.post-37424893570735467492007-07-12T12:35:00.000+01:002007-07-12T12:35:00.000+01:00"This means that if two Connotea users bookmark th..."This means that if two Connotea users bookmark the same paper, we could deduce that they are the same paper by comparing the embedded GUIDs."<BR/><BR/>Hi Rod, I've been asking connotea to do this, I call it <A HREF="http://www.nodalpoint.org/2006/12/15/buggotea_redundant_links_in_connotea" REL="nofollow">buggotea</A>. They don't seem to be too keen though...Anonymousnoreply@blogger.com