14:52:13 RRSAgent has joined #i18nits 14:52:13 logging to http://www.w3.org/2006/03/15-i18nits-irc 14:52:21 meeting: i18n ITS working group 14:52:23 chair: Yves 14:52:26 scribe: Felix 14:52:40 agenda: http://lists.w3.org/Archives/Member/member-i18n-its/2006JanMar/0186.html 14:52:57 regrets: Andrzej 14:59:54 regrets: Diane as well. 15:00:37 I18N_TS()10:00AM has now started 15:00:38 GoutamSaha has joined #i18nits 15:00:42 chriLi has joined #i18nits 15:00:42 +Andrzej_Zydron 15:00:44 +Yves_Savourel 15:00:46 -Yves_Savourel 15:00:49 +Yves_Savourel 15:00:55 rahtz has joined #i18nits 15:00:56 cgi-irc has joined #i18nits 15:01:26 AZ has joined #i18nits 15:01:50 +??P7 15:01:58 Hi Felix, Yves, Christian, Andrzej 15:02:10 +Sebastian_Rahtz 15:04:53 Hi Goutam 15:05:03 zakim, mute AZ 15:05:03 sorry, AZ, I do not see a party named 'AZ' 15:05:07 Zakim, who is here? 15:05:07 On the phone I see Yves_Savourel, Andrzej_Zydron, ??P7, Sebastian_Rahtz 15:05:09 On IRC I see AZ, cgi-irc, rahtz, chriLi, GoutamSaha, RRSAgent, Zakim, fsasaki, YvesS 15:05:16 +??P16 15:05:32 zakim, mute Andrzej_Zydron 15:05:32 Andrzej_Zydron should now be muted 15:05:55 zakim, ??P16 is Felix 15:05:55 +Felix; got it 15:06:09 topic: action items 15:06:43 action: Tag set editors to integrate discussion result about bugs 2881,2,3 (ONGOING) 15:07:05 action: Yves to work on XHTML + ITS modularization (ONGOING) 15:07:18 http://lists.w3.org/Archives/Public/public-i18n-its/2006JanMar/0298.html 15:07:31 Sebastian: This is an illustration, just an example how the rules might work 15:07:47 Yves: yes, esp. for the DTD it is hard to create hard defined rules 15:08:03 Sebastian: The more important question is how to get it in the DTD 15:08:13 Yves: if you change the DTD, it it no longer XHTML 15:08:42 Sebastian: Maybe the prose could say "this is a DTD which cannot be changed. This shows why we need external rules" 15:09:02 Yves: and you can use the HTML @class attribute to use translatability local 15:09:27 action: All to read and comment on RI's notes (ONGOING) 15:09:42 Yves: we have to come back to this after talking about the Mandelieu proposals 15:09:58 action: All comment on Mandelieu 9 proposals ('agree' or 'need discussion') (DONE) 15:10:34 action: Editor's of the techniques document: give examples how to use its:locInfoRef (decide on distinction of "alert" versus "description") (PENDING) 15:11:00 action: Richard to describe an additional level of conformance for Ruby (PENDING) 15:11:30 action: Felix to update bugzilla with open issues. (DROPPED) 15:12:34 action: Christian and Felix need to update their result of conformance discussion in the spec. (ONGOING) 15:12:45 Felix: not finished, but we have a good agreement on how to go 15:12:53 topic: Mandelieu proposals 15:13:12 Yves: we had discussion on editor call, and discussion between Richard and Felix 15:13:12 http://lists.w3.org/Archives/Public/public-i18n-its/2006JanMar/0283.html 15:13:19 Yves: these are the final proposals 15:14:37 proposal01 and proposal02 15:15:07 Christian: just an observation 15:15:18 r12a has joined #i18nits 15:15:33 zakim, dial ishida 15:15:33 ok, r12a; the call is being made 15:15:34 +Ishida 15:16:46 .. also, using names of elements might be more difficult than attributes 15:16:59 Sebastian: as you implement this, element names might be more natural 15:17:09 zakim, mute ishida 15:17:09 Ishida should now be muted 15:17:53 .. as for CSS, we could have a selector on documentRule, to have similar grouping 15:18:02 Yves: would that be an improvement? 15:18:20 Sebastian: If you want to express multiple bits of information about the same information 15:19:49 Felix: would that not be more verbose? 15:22:18 15:22:19 15:22:21 15:22:22 15:22:24 15:22:25 15:22:27 15:22:28 15:22:30 15:24:07 chriLi has joined #i18nits 15:25:16 fsasaki has joined #i18nits 15:27:09 Felix: how about putting this as a remark in the draft, and ask for feedback? 15:27:50 Yves: how about having this as an remark in the next draft and look for feedback? 15:28:16 Sebastian: it would make the XHTML example more verbose maybe 15:28:31 Yves: the change might be necessary for translatability, term, ruby 15:28:46 .. actually the different data categories rather overlap 15:28:59 s/rather/rarely 15:29:40 action: put a note on the proposal for grouping data categories in next working draft 15:31:31 Sebastian: One motivation for this was validation 15:31:32 15:31:33 15:31:35 15:31:36 15:31:38 15:31:39 15:31:41 15:31:42 15:31:44 15:32:40 Yves: we need to make decisions on some proposals 15:34:40 Yves: everybody happy with implementing proposal 1 and 2? taking Sebastians example in the draft as a note into account? 15:35:15 Sebastian: I would like to go ahead with this 15:35:28 Yves: proposal 1 and 2 accepted 15:35:30 proposal 3 15:35:39 Yves: everybody agreed on that 15:36:18 zakim, unmute ishida 15:36:18 Ishida should no longer be muted 15:36:24 Sebastian: one worry: 15:36:50 .. people might put markup into the element 15:37:14 .. we could have a remark "currently we support only unicode characters", no content 15:37:32 chriLi has joined #i18nits 15:38:58 Felix: is this necessary for this specific element 15:39:16 Richard: we are putting this in an element because of i18n issues like bidi 15:41:56 Felix: valid points. But maybe we should discuss its:span, and then use the same stuff for the element 15:42:06 Yves: but everybody is happy about having an element? 15:42:15 Christian: one concern: 15:43:07 .. here we do not use attributes 15:43:18 Felix: that's no issue since this is global usage 15:43:26 Yves: accept the proposal? 15:43:32 proposal 03 accepted 15:43:36 proposal 04: 15:43:44 Have an attribute @its:locInfoRef for localization information globally/locally 15:44:51 Sebastian: URIs make it easy to refer to anything in the same document or a different document 15:45:13 Christian: My concern is: if we allow pointers 15:45:31 .. they might no longer be valid as some localization work has been done 15:45:56 Yves: valid point 15:46:10 Sebastian: saying "#somepoint" does not say what the starting point is 15:48:40 Felix: that can be resolved if you make it clear in the spec 15:49:41 .. but is this not a general XML problem? 15:49:47 Yves: how is this useful for loc info? 15:49:56 Sebastian: you could point to wikipedia 15:50:19 Yves: we have the same mechanism with termref, so both should work the same way 15:50:43 -Andrzej_Zydron 15:50:50 Richard: with termref, you point only to a term and to a termReference 15:51:01 .. with locinfo, you only have localization info 15:52:20 Felix: the implementations are the same: you identify s.t. as "term" or as "subject to locinfo", and add a reference to it 15:53:31 Richard: could you point to the same node? 15:53:48 Yves: that is only possible globally 15:54:19 .. if we would have locinforef, we should have locinforefmap as well 15:55:02 Yves: could we have locinforef in the spec for now? 15:55:06 Richard: yes 15:55:12 proposal 04 for now accepted 15:55:23 Yves: now no. 05: mapping mechanism 15:55:43 Yves: original idea was to provide a mapping for each data category 15:56:02 .. the concern some of us had that you would have an extra mechanism in many places 15:58:21 Sebastian: how do you deal if you want to have everything in one namespace? you would need to map everything 15:58:37 .. we argued in Canne against this in verbosity 16:02:16 Sebastian: I argued for clearness of implementation 16:04:01 action: Felix to start the discussion on not having mapping for the translatability and the dir category on the mailing list; everybody please participate 16:04:12 topic: next face-to-face 16:04:27 Yves: people who come please let me know 16:08:57 topic: on the mapping discussion 16:11:35 yves: need to continue that on friday 16:11:37 -Sebastian_Rahtz 16:11:39 -Ishida 16:11:40 -??P7 16:11:40 -Yves_Savourel 16:11:42 -Felix 16:11:44 I18N_TS()10:00AM has ended 16:11:45 Attendees were Andrzej_Zydron, Yves_Savourel, Sebastian_Rahtz, Felix, Ishida 16:18:14 r12a has left #i18nits 16:50:20 rahtz has left #i18nits 17:59:41 Zakim has left #i18nits 18:04:19 fsasaki has joined #i18nits 18:04:34 rrsagent, make log public 18:04:47 rrsagent, draft minutes 18:04:47 I have made the request to generate http://www.w3.org/2006/03/15-i18nits-minutes.html fsasaki 18:23:32 fsasaki has left #i18nits