See also: IRC log
<scribe> Scribe: Addison
<scribe> ScribeNick: aphillip
richard: spoke at @media
... pretty good crowd (in the queen elizabeth hall); quite
impressive crowd
... richard to print the handouts and announce them
... talked about char encodings and lang declarations; some on
text expansion
... went well; about 25-30 came up afterwards with supportive
comments
[OPEN] ACTION: Addison to check latest XMLHTTPRequest LC draft against previous comments made when we reviewed the document
[OPEN] ACTION: Addison to guide decision next week (28th May) on which document(s) to tackle next from Charmod, etc list, and choose editor(s) to get work started
[OPEN] ACTION: Andrew to continue work on What should I consider wrt moving to UTF-8?
[OPEN] ACTION: Felix to check whether there are any issues in CURIE Syntax spec http://www.w3.org/TR/2008/WD-curie-20080506/
[OPEN] ACTION: Felix to report issue "IRI/URI Canonicalization does not address IRIs with IDNs" to the IDNA WG at IETF and see if they have any comments
[OPEN] ACTION: Addison to write an alternative proposal for the para giving an example in SSML 3.2.1
[OPEN] ACTION: Addison: write basic outline in wiki for a note on case folding
<scribe> ACTION: Addison to send link to Stephane's summary of the extlang mess to list [recorded in http://www.w3.org/2008/06/04-core-minutes.html#action01]
http://lists.w3.org/Archives/Member/member-i18n-core/2008Jun/0000.html
richard: LGTM
schedule: meeting monday tuesday in a 15 person room
addison: opportunity to do editing together
yves: not attending
<David> I should be there - we're holidaying nearby!
location: cannes-mandelieu
in october: bring your bathing costume
<r12a> http://www.w3.org/MarkUp/2008/WD-xhtml-access-20080526/
richard: a way of making things
happen via the keyboard
... has attribute called 'key' which is a single unicode char
that represents a shortcut key
... uses in all sorts of ways that suggest that 1 key == 1
character
... and that there are no i18n issues here
... no reference to DOM3 KeyEvents
... thinking of writing to them asking for clarification
... maybe we should sit down and enumerate the issues with keys
and key events
... not clear if key represents key press action or result of
key press action
addison: have a title attribute with text (human readable)
richard: title is overloaded
attribute too
... maybe have element contain text instead
... allows for <span> and other useful markup
... follow ITS guidelines
addison: I support those comments
yves: felix reviewed for ITS IG... nothing really from them
richard: so we should go ahead and make these comments
addison: the element builds an association between a "letter" and some specific text
<scribe> ACTION: Richard: to build comments on XHTML Access and send to XHTML [recorded in http://www.w3.org/2008/06/04-core-minutes.html#action02]
http://lists.w3.org/Archives/Public/public-i18n-core/2008AprJun/0052.html
http://lists.w3.org/Archives/Public/public-i18n-core/2008AprJun/0053.html
http://lists.w3.org/Archives/Public/public-i18n-core/2008AprJun/0061.html
What you should probably say is:
--
The user's language preferences as a comma-separated list of basic language ranges as defined in [BCP47]. The first item represents the user's most preferred language range [BCP47], followed by the next most preferred language and so forth. For example, "en, fr, es", where English is preferred over French, and French is preferred over Spanish, and Spanish is preferred over the default. Each language range MUST match the 'language-range' production in RFC 46
--
Davids comments: http://lists.w3.org/Archives/Public/public-i18n-core/2008AprJun/0059.html
<YvesS> oops... dropped. Coming back
any objection to making these official comments?
carried... no objection
http://lists.w3.org/Archives/Public/public-i18n-core/2008AprJun/0065.html
As a result of (3) there is likely to be regex matching against the
langtag, as opposed to RFC 4647 language ranges. I believe that regex
matching is more powerful, so that RFC 4647 could be supported by
software compliant with the spec being written, but explicit support for
RFC 4647 is currently not envisaged.
<scribe> ACTION: Addison: Prepare comments on OWL changes for review next week (11 June) [recorded in http://www.w3.org/2008/06/04-core-minutes.html#action03]
richard: pemberton says they are
going to write a schema for Ruby
... ruby spec has informal point to DTD for use in XHTML
... do we want to change Ruby spec to also point to
Schema
... Ruby is REC-Track
... maybe we can't change? need to investigate how to do errata
on it
... pemberton to send formal request to our list
This is scribe.perl Revision: 1.133 of Date: 2008/01/18 18:48:51 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/commenbts/comments/ Found Scribe: Addison Found ScribeNick: aphillip WARNING: Dash separator lines found. If you intended them to mark the start of a new topic, you need the -dashTopics option. For example: <Philippe> --- <Philippe> Review of Action Items Present: Addison Richard Michael Yves David Regrets: Andrew Felix Got date from IRC log name: 04 Jun 2008 Guessing minutes URL: http://www.w3.org/2008/06/04-core-minutes.html People with action items: addison richard[End of scribe.perl diagnostic output]