Re: [web-annotation] Terminology issue: Use IRI as resource identifier

The examples below show how modern browsers differently keep typed URL
 inside (document.URL, window.location). 
To turn URL into IRI, it would be necessary to apply both IDNA's 
toUnicode() [1] for URL host name and "decode percent encoding"[2]  
for URL path.
The difference between IDNA 2003 and IDNA 2008 [3] might not affect to
 the IRI conversion, but I'm not 100% sure.

1. non-Ascii URL host name
 -  [original] http://新宿駅.jp  
IE 11: http://新宿駅.jp  
Google Chrome: http://xn--oct34u4y7b.jp  
Safari: http://xn--oct34u4y7b.jp  
FireFox: http://新宿駅.jp  


2. non-Ascii URL path
 -  [original] https://ja.wikipedia.org/wiki/新宿駅
IE 11: https://ja.wikipedia.org/wiki/新宿駅
Google 
Chrome:https://ja.wikipedia.org/wiki/%E6%96%B0%E5%AE%BF%E9%A7%85
Safari:https://ja.wikipedia.org/wiki/%E6%96%B0%E5%AE%BF%E9%A7%85
FireFox:https://ja.wikipedia.org/wiki/%E6%96%B0%E5%AE%BF%E9%A7%85

 - [original] https://fr.wikipedia.org/wiki/caf
IE 11: https://fr.wikipedia.org/wiki/Caf%C3%A9
Google Chrome:https://fr.wikipedia.org/wiki/Caf%C3%A9
Safari:https://fr.wikipedia.org/wiki/Caf%C3%A9
FireFox:https://fr.wikipedia.org/wiki/Caf%C3%A9

[1] https://tools.ietf.org/html/rfc3490
[2] https://tools.ietf.org/html/rfc3986
[3] http://unicode.org/reports/tr46/

-- 
GitHub Notification of comment by tkanai
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/183#issuecomment-198304922
 using your GitHub account

Received on Friday, 18 March 2016 10:55:00 UTC