- From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
- Date: Tue, 19 Apr 2011 20:45:02 +0200
On 2011-04-19 20:29, Tab Atkins Jr. wrote: > On Tue, Apr 19, 2011 at 11:11 AM, Lachlan Hunt<lachlan.hunt at lachy.id.au> wrote: >> I'm also curious how we could handle ISBN URNs, like: >> >> urn:isbn:0-395-36341-1 >> >> That would be useful to have a web service that could look up the ISBN and >> direct users to information about the book, or to an online store. >> >> As currently specified, services have to register a handler for "urn", even >> if they only handle ISBN URNs. The other alternative would be to mint a new >> web+isbn scheme, which seems suboptimal. > > Presumably we can specifically whitelist "urn:isbn" as a scheme to > support (and adjust the algorithm sufficiently to make this do what's > intended)? Are there other nested urn: schemes that we could expose? > If so, we could just make the whole class of "urn:*" protocols > available. http://en.wikipedia.org/wiki/Uniform_Resource_Name#Examples http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xml -- Lachlan Hunt - Opera Software http://lachy.id.au/ http://www.opera.com/
Received on Tuesday, 19 April 2011 11:45:02 UTC