Related notes:

Making good progress on editing the IRI document, and, more importantly, working with Martin and Roy. Tack is to change IRI to match common processing model (parse before doing any encoding). Trying to talk Roy into updating URI document such that one spec would cover URI, IRI.

I have a specification that isn't ready for public review yet but is being circulated to a smaller group. The work so far has focused on making global changes to the IRI document to make integration of the "Web Address" specification reasonable (pushing some changes into the normative IRI processing rules.)

The motivation is to actually address the issue that WebAddress in HTML and W3C specs shouldn't be different from IRIs and URIs in IETF-specified applications such as email, instant messaging, telephony, directories, etc.

Leaving "Web Address" or "HREF" as an appendix in the IRI specification wouldn't address the issue.

However, this didn't address all HTML WG comments as promised, although I'd made some good progress. The main "issue" (which led to splitting this out in the first place) is to come up with a way of resolving conflicts between IETF and W3C specs and what browsers actually do (see section 12 of above document.)

Subsequently (and after some discussions with Maciej and Hixie on IRC chat and discussions at TAG meeting now ongoing), I expect to be able to produce another document in the next few days. (Updating due date to 9/28).

In the meanwhile, I'm trying to schedule IETF work to get IETF approval of this approach to URI/IRI/etc. An IETF working group may be necessary to get other IETF working groups (IDNA, HTTP, mailto URI) to pay attention.

Larry Masinter, 24 Sep 2009, 13:25:32 highlight

We are proposing updating IETF documents on IRIs in such a way that they are both acceptable to the communities that participate in IETF (DNS implementors, domain administrators, web security experts, implementors of systems that use IRIs in directory services, email systems, instant messaging, etc.) as well as the communities that participate in W3C HTML and WhatWG (implementors of browsers, search engines, HTML validators).

This work will happen in IETF, in a (proposed) IRI working group.

Larry Masinter, 16 Oct 2009, 08:36:43 highlight

[MikeSmith]: Larry is working on setting up a lunch meeting during TPAC week