- From: Clive D.W. Feather <clive@demon.net>
- Date: Mon, 30 Jun 2008 10:21:32 +0100
- To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
- Cc: uri@w3.org
Frank Ellermann said: >> reuse the phone number definition in the tel URI scheme > > | local-number-digits = > | *phonedigit-hex (HEXDIG / "*" / "#")*phonedigit-hex > .......................................^ > > TILT, game over. I think that was never correct, compare > RFC 2396 section 2.4.3 "excluded US-ASCII Charactes". Agreed. In other contexts, I've assumed that # was meant to be encoded. > Simplified, after an <authority>, if you use this, you > have to match a path/query/fragment structure, even if > you don't need any path/query/fragment. In the "path" > you can use any <pchar> as is. Notably not "/" (unless > it separates path-segments), not "?" (starts a <query>), > not "#" (starts a <fragment>). As soon as you are in > the <query> you can also use "/" and "?" as is, but not > "#" (still starts a <fragment>). Not quite. The tel URI scheme is using <opaque_part> rather than any form with an <authority>. You can't use "/" at all without escaping and "?" does *NOT* start a query, it is an uninterpreted character. > IIRC "#" is also never allowed as is, unless it starts > a <fragment>. Agreed. > If you want to use tel: maybe start with > a 3966bis (?) I'd be willing to update 3966; I take it this is the right WG? -- Clive D.W. Feather | Work: <clive@demon.net> | Tel: +44 20 8495 6138 Internet Expert | Home: <clive@davros.org> | Fax: +44 870 051 9937 Demon Internet | WWW: http://www.davros.org | Mobile: +44 7973 377646 THUS plc | |
Received on Monday, 30 June 2008 10:16:38 UTC