See also: IRC log
http://www.w3.org/International/track/actions/open
ACTION-81
<trackbot> ACTION-81 -- Addison Phillips to Create blog post on what's going on with IRI -- due 2011-11-23 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/81
https://www.w3.org/International/wiki/IRIStatus
close action-239
<trackbot> Closed action-239.
close action-293
<trackbot> Closed action-293.
close action-294
<trackbot> Closed action-294.
close action-296
<trackbot> Closed action-296.
JcK: URN document will probably
be posted tomorrow or monday
... first step
... remove URNs from category of URIs
richard: two best practices
documents out for review currently
... for two weeks from now
Richard: working group extended for two years until end 2015
https://www.w3.org/International/wiki/Review_radar
JcK: ICANN topic in an ICANN committee
richard: can you send link to the
list?
... trying to follow IRI/URI/IDNA thing
... Don Hollander sent me a ping
... issue is that
... IDNA works technically, but purchasers are unhappy
... because they aren't well supported widely away from the
core DNS
<scribe> ScribeNick: aphillip
Richard: getting wide range of
stakeholders together to discuss universal deployment of
IDNs
... and further discussion at MLWeb conf
JcK: Don is trying to raise
visibility
... some folks think this could work "by magic" and others want
it to be improved
... another problem is that (particularly in china) that there
is non-UTF-8 content unlabelled or wrongly labelled
... some of this stuff is "hard"
... for example, mail fixes requires work on mail
transports
... in IMAP and POP clients
... problem occurs when you read community boundary
... MUAs run into problems crossing script boundaries
... not to mention use of IDNs for spoofing
<r12a> companies can change their policies to accept idn identifiers, but you may not be able to type it in to an airport terminal
addison: could solve the IDNA bit
in isolation
... but not the non-host part of URI or the local part of
email, etc.
JcK: if you know the A label form
you can use that (the punycode form)
... might be solved by having a smartphone app to conver to
ascii
... the system is worldwide
... but this solves communicating inside communities
... say China-to-China
... or Arabic-to-Arabic
... but hard when you start to go Arabic-to-Chinese
addison: most systems can *read* or display the data
richard: who are the players. what's going on, what the issues are
addison start our own list of the problems?
see you in two weeks