- From: Phillips, Addison <addison@lab126.com>
- Date: Tue, 25 Aug 2015 18:32:30 +0000
- To: Anne van Kesteren <annevk@annevk.nl>
- CC: Lina Kemmel <LKEMMEL@il.ibm.com>, Martin Dürst <duerst@it.aoyama.ac.jp>, Larry Masinter <masinter@adobe.com>, "www-international@w3.org" <www-international@w3.org>
Hi Anne, > > https://www.w3.org/International/wiki/IRIStatus > > Looking through this, the URL Standard addresses the IDNA issues you > mention. Thanks. I'll update the page. It was written a while ago and it incorporates some issues that WG members felt strongly about at the time--and doesn't reflect updates to URL spec since. > The bidirectional section has a good point in that even if we give some advice > towards displaying URLs (including converting their internal percent-encoded > bytes to Unicode) doing anything more than left-to-right string is tricky and it > might indeed be confusing if browser UI displayed these differently from > plain text. (This further argues for only showing domains in the browser UI, I > think, to avoid making the path look like part of the domain.) This was a (perhaps "the") main sticking point for IRI and it's thorny: there is no obvious solution for all use cases, just sets of compromises or potential things we could try to enforce. > > I'm not sure URL detection within a string of text is a worthwhile > standardization topic, but I suppose we could mention it and some of its > pitfalls. It seems though that determining whether n:m is a URL or a > relationship in a diagram is rather hard. This was an item others felt needed to be documented. It falls outside the scope of what URL or specs such as HTML would define, but might be a topic for best practices or other documentation. It could, I suppose, be affected by choices made in the URL spec. > > It's not clear why "Query encoding" is a subsection of "Link detection" or why > it's considered to be an open issue. The URL Standard addresses it. Query encoding isn't part of link detection. I think I added it at the end at someone's behest. URL does address it. I'll fix this section up. > > As for "Confusable characters" I think this is largely up to implementations. I > did add a section detailing some of the issues > here: > > https://url.spec.whatwg.org/#security-considerations > Agreed. Thanks, Addison
Received on Tuesday, 25 August 2015 18:32:53 UTC