Proposed change to Monday's agenda (IRI's versus URI's)

[robert_weir@us.ibm.com]

I've been handed some unofficial feedback from the
Japanese standards body, indirectly forwarded to me via IBM's Japanese
subsidiary.  It appears that ODF's use of URI's rather than the new
unicode IRI's (http://www.w3.org/International/O-URL-and-ident.html) has
been received poorly, and may result in an unfavorable ISO vote from Japan.

They are also questioning ODF's use of CSS3 and DOM
level 3 events, since neither were formally adopted by the W3C.  The
suggestion was to define necessary portions of these specs in the ODF spec,
rather than by reference.  (IMHO, this seems like more of an editorial
comment than a technical one.)

I'm asking that we agree to take on this issue on
Monday's call as a priority issue.  The next meeting of their standards
group will be before the end of the month, so there is some urgency for
the TC to state if and how they will address this issue before then, which
could turn around their vote.  

I'm no expert in this area, but it seems a possible
fix would be to allow an IRI every place in the spec where a URI is currently
specified.  Would this cause any other issues in the specification?
 Any implementation issues?

The tricky part might be where we reference an external
specification which has not been updated to allow IRI's. (SVG?  SMIL?).
 If there is any data which is essentially shared between legacy URI-based
standards and newer IRI-aware standards, then we'll need to be careful
how they interface.

Do we agree that this IRI issue is a legitimate concern
with ODF documents in Japan (and potentially China, Korea, etc.)?

Can I get some +1's for adding this to the agenda
for Monday?

-Rob