RE: HTML5 proposes introduction of new family of URI schemes

web+x:y could also instead be coded


that is, use/register a new mime type instead of a new url scheme.

-----Original message-----
From: Larry Masinter <>
To: "" <>, "Martin J. Dürst" <>
Cc: David Booth <>, Robin Berjon <>, " List" <>, Paul Cotton <>, Maciej Stachowiak <>, Sam Ruby <>
Sent: Sat, Jan 21, 2012 05:55:25 GMT+00:00
Subject: RE: HTML5 proposes introduction of new family of URI schemes

>> I'm not sure what the difference would be between having e.g.,
>> "web+acme:hello" and "web:acme:hello", except for a multi-level
>> structure where potential inventors of a new protocol/scheme get more
>> confused than necessary.
> ...

> The difference is mainly process: "web+" needs coordination with and approval
> by the IETF IRI WG, while "web:" is simply one additional new URI scheme.

The process is mainly irrelevant (sure, you might have to update the RFC twice, but in the IETF, decisions are made by rough consensus of the internet community, the "working group" doesn't approve.)

The issue mainly is whether you follow the generic hierarchical syntax and can use all URI parsing libraries if there's an 'authority' that you want to process differently than the path.

a is authority, path is /b/c

but for
there is no authority, path is blah://a/b/c


   scheme         = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." )

Received on Sunday, 22 January 2012 09:36:28 UTC