On 12/12/05, C. Hudley <<a href="mailto:chudley@gmail.com">chudley@gmail.com</a>> wrote:<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On 12/9/05, David Osolkowski <<a href="mailto:qidydl@gmail.com">qidydl@gmail.com</a>> wrote: > > The tag: URI scheme[1] provides a fairly effective way to generate unique > ID's.  I believe it is the recommended way to generate GUIDs for Atom[2]. > Thus, it seems likely it could be re-used here. > > [1] <a href="http://www.taguri.org/">http://www.taguri.org/</a> Has the tag URI scheme been registered successfully?  I don't see an update on its status on that page. If not, the info URI scheme (as was mentioned here recently), with the "sid" namespace, could be used the same way, and it has been registered. <a href="http://info-uri.info/registry/OAIHandler?verb=GetRecord&metadataPrefix=reg&identifier=info:sid/"> http://info-uri.info/registry/OAIHandler?verb=GetRecord&metadataPrefix=reg&identifier=info:sid/</a></blockquote><div> The tag scheme is RFC 4151: <a href="http://ietf.org/rfc/rfc4151">http://ietf.org/rfc/rfc4151 </a>  </div>The sid namespace appears to be for identifying collections of information ("The sid namespace facilitates the identification of collections of information assets. A collection of information assets could be an organization, a website, a publisher, or a database.").  The point here is to identify a specific event.  The tag scheme is similarly used to identify specific entries, as opposed to collections.  I suggest that tag is a better match than sid ("more semantic", just to tie this back to microformats). - David Osolkowski </div>