W3C home > Mailing lists > Public > public-i18n-core@w3.org > July to September 2005

[I18N Core] REMINDER Teleconference is 2005-08-02 TOMORROW

From: Addison Phillips <addison.phillips@quest.com>
Date: Mon, 1 Aug 2005 20:35:48 -0700
Message-ID: <634978A7DF025A40BFEF33EB191E13BC0C4AB337@irvmbxw01.quest.com>
To: <public-i18n-core@w3.org>
W3C Internationalization Core Working Group Teleconference
----------------------------------------------------------------------------
Bridge   : +1-617-761-6200 (Zakim) with conference code 4186 (spells "I18N")
Duration : 60 minutes + 60 minutes for LTLI
----------------------------------------------------------------------------
Day      : Tuesday
Dates    : 2 August 2005
Start    : UTC/GMT: 15:00
           America/New York: 11:00
           America/Los Angeles: 08:00
           Asia/Tokyo: 00:00 (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


Note: I'm traveling and won't be able to scribe and not necessarily able to call in. The IRI discussion is very important to me to be present for personally, so I'll make my best effort, though.


AGENDA
======
1. Agenda/Announcements (5 minutes)
2. Action Items (5 minutes)
3. XQuery and Time Zone Wiki work [1] (10 minutes)
4. IRI discussion: HCG prep; cf. [2] (20 minutes)
5. <q> feature discussion (20 minutes)


ACTION ITEMS
============
AP: be sure to link the links page
FS: update review documents for CCXML and CSS 2.1 and post
AP: point out reference material for LTLI
FY: CharMod Norm draft?

[1] http://esw.w3.org/topic/i18nFAQTimeZone 
[2] quoting an email from Chris Lilley suggesting topics for this:

<q>
A certain amount of IRI 101 education is thus in order. I suggest (but feel free to change, of course) the following structure:

- The need (not just easy to type web addresses for non-English folks but also the query part for dictionary lookup, etc)
- The problem of guessing the encoding ('encoding of the page' not working for bookmarked queries, etc)
- Overview of what anyURI, XML, and XLink already require in terms of what can be put as an attribute value (ie, all the Unicode stuff) and what must be done to turn it into a URI, and how late that is done (on link traversal, not on content creation)
- Check at this point whose specs reference what by way of attributes that take URI
- What IRI adds (IDNS, character normalisation) and how easy that is
- Choice between older practice of specifying the whole copy and paste thing (hexify, etc) or newer practice of just referring to IRI section 3.1
- Samples of newer specs that move to IRI (XLink 1.1, SVG 1.2, what is Schema 1.1 doing?)
</q>

Addison P. Phillips
Globalization Architect, Quest Software
http://www.quest.com


Chair, W3C Internationalization Core Working Group
http://www.w3.org/International


Internationalization is not a feature.
It is an architecture. 


Received on Tuesday, 2 August 2005 03:35:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 October 2008 10:18:49 GMT