14:54:49 RRSAgent has joined #i18n 14:54:49 logging to http://www.w3.org/2011/06/15-i18n-irc 14:54:53 Zakim has joined #i18n 14:55:00 trackbot, prepare teleconference 14:55:02 RRSAgent, make logs world 14:55:04 Zakim, this will be 4186 14:55:04 ok, trackbot; I see I18N_CoreWG()11:00AM scheduled to start in 5 minutes 14:55:05 Meeting: Internationalization Core Working Group Teleconference 14:55:05 Date: 15 June 2011 14:55:30 Agenda: http://lists.w3.org/Archives/Member/member-i18n-core/2011Jun/0006.html 14:55:37 Chair: Addison Phillips 14:55:44 Scribe: Addison Phillips 14:55:44 ScribeNick: aphillip 14:56:02 rrsagent, draft minutes 14:56:02 I have made the request to generate http://www.w3.org/2011/06/15-i18n-minutes.html aphillip 14:56:26 rrsagent, set logs world-visible 14:56:30 moo 14:56:37 rrsagent, draft minutes 14:56:37 I have made the request to generate http://www.w3.org/2011/06/15-i18n-minutes.html aphillip 14:57:02 David has joined #i18n 14:57:28 matial has joined #i18n 14:58:14 I18N_CoreWG()11:00AM has now started 14:58:21 +??P11 14:58:21 kojiishi has joined #i18n 14:58:43 zakim, ??P11 is matial 14:58:43 +matial; got it 14:58:46 + +44.141.888.aaaa 14:59:03 zakim, +44 is David 14:59:04 +David; got it 14:59:05 zakim, dial richard 14:59:06 ok, r12a; the call is being made 14:59:08 +Richard 14:59:14 +Addison_Phillips 14:59:23 zakim, who's here ? 14:59:23 On the phone I see matial, David, Richard, Addison_Phillips 14:59:25 On IRC I see kojiishi, matial, David, Zakim, RRSAgent, aphillip, r12a, trackbot 14:59:48 zakim, I am Richard 14:59:48 ok, r12a, I now associate you with Richard 15:00:13 zakim, who's noisy? 15:00:24 aphillip, listening for 10 seconds I heard sound from the following: Addison_Phillips (4%), David (33%) 15:00:45 zakim, mute me 15:00:45 David should now be muted 15:01:03 fsasaki has joined #i18n 15:01:50 -David 15:02:16 +David 15:02:32 +??P15 15:03:13 +??P31 15:03:22 zakim, ??p31 is me 15:03:31 +kojiishi; got it 15:03:49 Topic: Minutes and Agenda review 15:04:04 aharon has joined #i18n 15:04:05 Topic: Action Items 15:04:22 Finish edits and convert time zones document to HTML 15:05:00 http://www.w3.org/International/track/actions/open 15:05:26 Talk with Bert about how to deal with change marks in Ruby spec 15:05:26 Talk with Bert about how to deal with change marks in Ruby spec 15:05:41 + +972.5.424.5aabb 15:05:57 zakim, mute me 15:05:57 sorry, aharon, I do not know which phone connection belongs to you 15:06:07 zakim, +972 is aharon 15:06:07 +aharon; got it 15:06:25 zakim, mute me 15:06:25 aharon should now be muted 15:06:38 Create wiki page with normalization position paper 15:06:53 agenda item for today 15:07:11 Review Contacts API and collect last call comments for the WG. WG members to perform review. 15:07:21 will start this week 15:07:31 everyone: should help koji out 15:07:44 Reply to WOFF indicating our acceptance/non-acceptance of issues per 2011-06-01 telecon 15:08:22 done; they are having a telecon concurrently and will discuss last open issue (splitting items into localizable elements) 15:09:05 close ACTION-44 15:09:05 ACTION-44 Reply to WOFF indicating our acceptance/non-acceptance of issues per 2011-06-01 telecon closed 15:09:16 Publish qa-personal-names for wide review 15:09:25 not done; need to respond to Mark's comments 15:09:40 Dump charmod-norm and add disclaimer paragraph, dates, etc. so that we can publish an interim working draft 15:10:44 Topic: Info Share 15:11:13 close ACTION-21 15:11:13 ACTION-21 Review techniques index pages to check that all the current links in the index point to the right place closed 15:11:43 close ACTION-34 15:11:43 ACTION-34 Ask chinese colleagues about character orientation spec closed 15:12:36 chris lilley is likely to contact us to set up a meeting about normalization 15:13:54 http://www.wired.com/gadgetlab/2011/06/microsoft-developers-windows-8/all/1 15:14:10 David: link about Windows8 use of HTML5/JS 15:15:00 Topic: Reviews 15:15:09 - Widgets - HTML5 15:15:21 -Contacts API 15:16:20 chair: call to arms on reviewing HTML5 15:16:44 Topic : Time Zones document progress 15:17:01 http://www.w3.org/International/docs/timezones/ 15:17:42 addison: I think I could nearly almost sorta be done 15:17:48 richard: I have a few comments 15:18:22 ACTION: addison: collect any remaining comments and update timezones document for final publication 15:18:22 Created ACTION-47 - Collect any remaining comments and update timezones document for final publication [on Addison Phillips - due 2011-06-22]. 15:19:13 richard: really detailed (hyper-detailed) and kind of scary 15:19:22 ... could use a short article about time zones in HTML5 15:20:45 ... "here's how to use the new forms elements" 15:21:20 Topic: Normalization 15:21:33 http://www.w3.org/International/wiki/CharmodNormSummary 15:22:00 http://www.w3.org/TR/charmod-norm/ 15:23:54 Specifications MUST require identifiers, namespaces, element names, attribute names, and attribute values to be compared as if they were fully-normalized. Specifications SHOULD NOT require documents to be stored or transcoded to any particular normalization form. However, specifications MAY require specific fields or values within a document to be fully-normalized. 15:25:30 Textual content SHOULD be stored and interchanged in a fully-normalized format, except where it interferes with the author's intentions. give examples 15:27:33 define A "normalization-sensitive operation" is one whose results may differ when normalization is applied to content. define A "normalizing operation" is one whose results are normalization sensitive and which fully-normalizes the text on which it operates. 15:29:14 richard: 3.2.5 defines normalization sensitve operations 15:30:31 A text-processing component MAY perform normalization-sensitive operations without first normalizing or checking for normalization of content. The results of any such operation are dependent upon the code points encoded and visually and semantically identical strings might compare as unequal. 15:31:03 compare -> be treated as 15:31:48 "addison: I like this" 15:33:58 identifiers, namespaces, element names, attribute names, and attribute values 15:38:24 -aharon 15:38:52 richard: call out authoring tools and keyboards 15:39:07 ... should they provide normalization option or generally output normalized output?? 15:39:43 Authoring tool implementations for a (formal) language that does not mandate full-normalization SHOULD either prevent users from creating content with composing characters at the beginning of constructs that may be significant, such as at the beginning of an entity that will be included, immediately after a construct that causes inclusion or immediately after markup, or SHOULD warn users when they do so. 15:40:35 q+ to ask if we should put pointers from each recommendation to specs (as much as there are already) that already do the right thing with regards to normalization 15:40:36 add a requirement about authoring tools/keyboards/input 15:40:41 ack me 15:40:42 fsasaki, you wanted to ask if we should put pointers from each recommendation to specs (as much as there are already) that already do the right thing with regards to normalization 15:40:46 ack fsasaki 15:42:51 C308 [S] Where operations may produce unnormalized output from normalized text input, specifications of API components (functions/methods) that implement these operations MUST define whether normalization is the responsibility of the caller or the callee. Specifications MAY state that performing normalization is optional for some API components; in this case the default SHOULD be that normalization is performed, and an explicit option SHOULD be used to swit 15:43:08 Specifications of API components (functions/methods) MAY optionally require that normalization is performed for normalization-sensitive operations; the default SHOULD be that normalization is performed, and an explicit option SHOULD be used to switch normalization off. 15:43:34 zakim, who's making noise? 15:43:45 r12a, listening for 11 seconds I heard sound from the following: Addison_Phillips (12%), David (59%), fsasaki (78%) 15:43:55 zakim, mute david 15:43:55 David should now be muted 15:46:19 richard: worried that "full normalization" creates a lot of complexity 15:46:26 .... hard to pin down 15:46:47 ... but also created problems such as combining mark inside a for example 15:47:16 Specifications of text-based languages and protocols SHOULD define precisely the construct boundaries necessary to process the language, protocol, or document format in the absence of normalized textual content. These definitions SHOULD include at least the boundaries between markup and character data as well as entity boundaries (if the language has an include mechanism), SHOULD include any other boundary that may create denormalization when instances of the 15:48:40 addison: deal with combining marks after parsing the document rather than before 15:49:13 Authoring tool implementations for a (formal) language that does not mandate full-normalization SHOULD either prevent users from creating content with composing characters at the beginning of constructs that may be significant, such as at the beginning of an entity that will be included, immediately after a construct that causes inclusion or immediately after markup, or SHOULD warn users when they do so. 15:49:55 addison/richard: not wild about that one 15:51:01 attribute=/foo 15:51:10 where '/' is a combining solidus 15:54:07 \// r12a// this is my comment // 15:54:34 put a couple of spaces on the front 15:55:20 ACTION: addison: update charmodsummary and review WG member comments as they come in 15:55:20 Created ACTION-48 - Update charmodsummary and review WG member comments as they come in [on Addison Phillips - due 2011-06-22]. 15:55:56 Topic: List traffic items 15:56:16 - should UTF-8 BOM trump document encoding - changes to text/* default character encoding 15:56:28 latter is an internet-draft 15:57:07 addison: add review of tracker issues to agenda for each week going forward 15:57:09 http://www.w3.org/International/track/products/6 15:57:19 http://www.w3.org/International/track/products/7 15:58:17 http://www.w3.org/International/track/issues/24 15:58:49 "do we need complex ruby?" 15:58:49 -fsasaki 15:59:04 koji: personally am for complex ruby 15:59:12 ... but some folks don't agree 16:02:12 addison: need to be able to produce print-grade publications 16:02:36 ... can we be forward looking here? or is that too hard? 16:03:40 koji: because of form factors, jukugo-ruby is likely to be more important for browsers and mobile devices than for print 16:03:52 ... according to discussions in kyoto 16:04:13 ... particularly for wrapping text in narrow columns 16:04:59 r12a: need to work out if possible in current html5 ruby model 16:05:46 koji: epub guys interested, but busy to ship epub3 16:06:22 ... will try to get information from epub guys this week 16:06:52 ACTION: koji: contact epub folks and see if jukugo-ruby can be supported with html5 markup or if something else is needed 16:06:52 Created ACTION-49 - Contact epub folks and see if jukugo-ruby can be supported with html5 markup or if something else is needed [on Koji Ishii - due 2011-06-22]. 16:07:06 addison: me too. 16:07:18 Topic: AOB 16:07:54 bye 16:07:55 -Addison_Phillips 16:07:56 -kojiishi 16:08:02 -Richard 16:08:32 -matial 16:08:43 rrsagent, make minutes 16:08:43 I have made the request to generate http://www.w3.org/2011/06/15-i18n-minutes.html aphillip 16:09:20 zakim, bye 16:09:28 I18N_CoreWG()11:00AM has ended 16:09:31 Zakim has left #i18n 16:09:33 Attendees were matial, +44.141.888.aaaa, David, Richard, Addison_Phillips, fsasaki, kojiishi, +972.5.424.5aabb, aharon 16:10:02 Present: Addison, Richard, Felix, David, Mati, Koji, Aharon 16:10:11 I have made the request to generate http://www.w3.org/2011/06/15-i18n-minutes.html aphillip 16:10:15 rrsagent, bye 16:10:15 I see 3 open action items saved in http://www.w3.org/2011/06/15-i18n-actions.rdf : 16:10:15 ACTION: addison: collect any remaining comments and update timezones document for final publication [1] 16:10:15 recorded in http://www.w3.org/2011/06/15-i18n-irc#T15-18-22 16:10:15 ACTION: addison: update charmodsummary and review WG member comments as they come in [2] 16:10:15 recorded in http://www.w3.org/2011/06/15-i18n-irc#T15-55-20 16:10:15 ACTION: koji: contact epub folks and see if jukugo-ruby can be supported with html5 markup or if something else is needed [3] 16:10:15 recorded in http://www.w3.org/2011/06/15-i18n-irc#T16-06-52