[I18N Core] REMINDER Teleconference is 2005-03-29 TODAY

W3C Internationalization Core Working Group Teleconference
Bridge   : +1-617-761-6200 (Zakim) with conference code 4186 (spells "I18N")
Duration : 60 minutes
Day      : Tuesday
Dates    : 15 March 2005
Start    : 22:00 GMT ; 17:00 Eastern ; 14:00 Pacific ; 7:00 Asia/Tokyo (next day)
Zakim information    : http://www.w3.org/2002/01/UsingZakim

Zakim bridge monitor : http://www.w3.org/1998/12/bridge/Zakim.html

Zakim IRC bot        : http://www.w3.org/2001/12/zakim-irc-bot.html

Useful Links:
Our website     : http://www.w3.org/International/core

Apologies on the late notice: was traveling yesterday with limited IP access.


AP: Send list of current outstanding reviews
FY: provide CharModNorm draft for review.

-- following refer to XHTML 2.0 review responses --
RI: find out how "Number" is being used to see if it is okay (#8)
RI: check with them again about #10 and its application
RI: push back on points given (#21)
TT: generate a short list of items that are language affected to see if worth pursuing (low priority, not an XHTML response)
AP: to write this response (#35c) on AcceptLang vs. hreflang, pushing back
RI: push back please (#38)
AP: push back in separate email about Accept-Charset mess. Copy FY and MD first. (#5)


1. Agenda
2. Action Items
3. Discussion: incorporating IRI into XML Schema (see [1] below)
4. Discussion: any response on language-of-doc thread on winter?
5. CharMod/Lang/WS updates
6. Other business

[1] fsasaki: Proposals for changes of the datatype "anyURI", as described by xml schema (cf. http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#anyURI):

(1) anyURI should refer to sec. 3.1 of the IRI-spec, instead of XLINK. This is important because of the normalization requirements as described in the  IRI-spec: if a legacy-encoding is not normalized before mapping from anyURI to URIs, the result might be different from the normalized case. The IRI-spec  gives an example for such a legacy-encoding from Vietnamese encoded as windows-1258, cf. also sec. 3.1.

(2) for domain names, anyURI should refer to the IDN-part of the ABNF of the IRI-spec, cf. sec. 2.2 of the IRI-spec. THis would allow access to registered  domain names. This constraint should apply at least for processors which accept schemas in the form of XML documents; it is acceptable if it does not apply  for minimally conforming processors of xml schema.

(3) Handling of specific characters, see the passage from the IRI-spec below:
Systems accepting IRIs MAY also deal with the printable characters in
   US-ASCII that are not allowed in URIs, namely "<", ">", '"', space,
   "{", "}", "|", "\", "^", and "`", in step 2 above.  If these
   characters are found but are not converted, then the conversion
   SHOULD fail.  Please note that the number sign ("#"), the percent
   sign ("%"), and the square bracket characters ("[", "]") are not part
   of the above list and MUST NOT be converted.  Protocols and formats
   that have used earlier definitions of IRIs including these characters
   MAY require percent-encoding of these characters as a preprocessing
   step to extract the actual IRI from a given field.  This
   preprocessing MAY also be used by applications allowing the user to
   enter an IRI.

(4) an editorial issue: the reference from anyURI to section 8 of the old charmod-req should be changed to the new charmod-resid spec, cf.  http://www.w3.org/TR/2004/CR-charmod-resid-20041122/

Addison P. Phillips
Globalization Architect, Quest Software

Chair, W3C Internationalization Core Working Group

Internationalization is not a feature.
It is an architecture. 

Received on Tuesday, 29 March 2005 20:12:53 UTC