- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 14 Aug 2009 09:22:42 +0200
- To: Ian Hickson <ian@hixie.ch>
- CC: uri-review@ietf.org, hybi@ietf.org, uri@w3.org
Julian Reschke wrote: > Julian Reschke wrote: >> ... >>> URI scheme syntax. >>> "ws" ":" hier-part [ "?" query ] >> >> I assume you are using ABNF syntax (RFC5234) and terminology from the >> URI spec, but you really need to state that. >> ... > > Furthermore I see no mention at all of these URI schemes in the > remainder of the spec. So is the IANA registration template supposed to > *be* the definition? > > In particular: > > 1) What does a "ws" URI identify? > > 2) What is the semantics of "hier-part" and "query"? > ... There's a new draft: <http://www.ietf.org/id/draft-hixie-thewebsocketprotocol-32.txt> (BTW: just because publishing I-Ds is so simple doesn't mean that every single change needs to be published right away; it's a distraction and also confuses people about when they are supposed to review). Anyway, it now says: > URI scheme syntax. > In ABNF terms using the terminals from the IRI specifications: > [RFC5238] [RFC3987] > > "ws" ":" ihier-part [ "?" iquery ] That is even worse than before, because it now uses productions from the IRI spec defining *URI* syntax. Furthermore, it still doesn't answer what the semantics of these parts are. What do "ihier-part" and "iquery" represent in a ws URI? What'S the effect? How are they used? BR, Julian PS: what does RFC5238 have to do with this?
Received on Friday, 14 August 2009 07:23:28 UTC