13:43:06 RRSAgent has joined #i18nits 13:43:06 logging to http://www.w3.org/2006/04/07-i18nits-irc 13:43:18 meeting: i18n ITS working group (editor's call) 13:43:20 chair: Yves 13:43:22 scribe: Felix 13:44:04 scribeNick: fsasaki 13:54:52 YvesS has joined #i18nits 13:56:40 Hi Yves 13:57:20 Hi Felix :) 13:58:05 I18N_ITS(EDIT)10:00AM has now started 13:58:12 +Yves_Savourel 13:58:14 zakim, dial felix-home 13:58:14 ok, fsasaki; the call is being made 13:58:16 +Felix 14:00:55 +??P18 14:01:53 chriLi has joined #i18nits 14:05:09 topic: christian: change report 14:05:23 christian: I integreated all "water proove" comments Yves made 14:05:53 http://lists.w3.org/Archives/Public/public-i18n-its/2006AprJun/0035.html 14:06:15 (above are comments from Yves) 14:06:24 christian: I did proposal 1, 2, 3, but not 4 14:06:32 yves: 4 was just a suggestion 14:07:02 christian: I suggest "content-related tools" 14:07:05 yves: fine with me 14:07:14 christian: 5, the "knowledge-workers" 14:07:48 yves: it sounds strange 14:07:58 Felix: I have heard it only in German 14:08:39 .. how about "content producers"? 14:08:45 christian: +1 14:08:49 yves: +1 14:09:09 christian: comment 6 14:09:43 yves: not important, that's fine 14:10:11 christian: on 7: grammatical correctness? 14:10:55 felix: we don't have keep track of it now 14:11:45 christian: remark 8: I would keep it 14:11:47 yves: +1 14:12:24 http://www.w3.org/International/its/itstagset/itstagset.html#introduction 14:13:01 chriLi has joined #i18nits 14:13:03 http://www.w3.org/International/its/itstagset/itstagset.html#introduction 14:14:13 yves: example 2 seems incorrect 14:14:31 felix: its:translateSelector="//dt"/ 14:15:12 .. maybe fits better 14:15:36 yves: translate is still set to "yes" 14:15:54 christian: Yves comment 11: 14:16:22 [[Just an observation. To some degree the text above make it sounds like that internationalization is limited to allow 14:16:22 localization. Maybe some small rewording may inject the aspect of allowing content in any language (maybe after this draft is done) 14:16:23 ]] 14:16:35 yves: i18n allows to have content in different languages 14:16:43 .. which is not covered by the definition 14:17:23 christian: how should that be reworded? 14:18:02 yves: let's see what others think 14:18:25 .. as for 13: again a lot about localization 14:22:30 Yves: the formatting has some additional line feeds 14:23:04 christian: how about the example about "in the schema"? 14:23:13 felix: that is left from the "schemaRule" area 14:25:24 christian: how about schema developers? 14:27:16 yves: examples might be very complex 14:27:25 .. schema developers can do very different things 14:28:46 .. e.g. mapping ITS via rules, or integrating markup declarations in the schema 14:29:02 felix: how about a pointer to section 7 / the separate document 14:29:07 yves: +1 14:29:10 christian: +1 14:34:03 topic: section on "basic concepts" 14:34:09 para above Example 9 "thetranslate attribute" is missing a space. 14:34:22 christian: made some minor changes 14:34:44 yves: there are some spacing issues 14:34:52 .. maybe due to XML Spy 14:37:13 .. some markup for code? 14:37:22 felix: a

 element would help
14:37:36  .. "its:translate='no'"
14:38:13  yves: "in the example translateSelector" should be with "selector"
14:38:50  .. I'll review section "basic concepts"
14:39:08  .. and write a mail to the list
14:39:45  yves: as for examples in that section: they seem to be very basic
14:40:49  .. e.g. they are not valid, e.g. "..."
14:41:58  felix: how about the difference between pointing and adding information?
14:42:07  .. is that good here, or too specific?
14:42:25  christian: we say in this section that we have a local and a local one
14:42:31  .. and the selection
14:44:00  felix: definition in the normative part: http://www.w3.org/International/its/itstagset/itstagset.html#selection-global
14:44:33  chriLi has joined #i18nits
14:45:46  .. you can use that to make the non-normative explanation 
14:47:14  felix: so we can close the three bugs on these changes?
14:47:18  christian: yes
14:47:24  topic: versioning issue
14:47:51  yves: we have to say: is it o.k. to have one or more rules elements in one document?
14:48:01  .. if yes, we get some problems
14:48:20  .. if we have only on rules element per file, things get easier
14:48:26  christian: +1
14:51:10  felix: +1
14:51:20  yves: all agree it is a bad idea
14:51:52  action: Yves to send an action item about the "only" one rules element per file topic
14:56:14  yves: we had a consensus on the position 
15:05:52  felix: sorry for the confusion of my explanation, I would go for the version element at the root element
15:06:06  christian: as for an external file
15:06:14  .. what would it contain?
15:06:34       xlink:href="myRules.xml">
15:07:26  .. what may be in "myRules.xml"?
15:07:39  yves: somewhere in that file there is an rules element
15:08:05  christian: the top element of that file could be rules
15:08:13  yves: that is a specific case of a generic case
15:08:33  .. that approach good for extensibility
15:09:00  christian: I would make clear that "rules" does not has to be the top level element of the external file
15:09:23  .. it would make things clearer
15:09:56  yves: so we resolved "linking" and "multiple rules" issues, for the three of us
15:10:56  felix: so we integrate that into the draft
15:11:29  zakim, make log public
15:11:29  I don't understand 'make log public', fsasaki
15:11:35  rrsagent, make log public
15:12:28  present: Christian, Felix, Yves
15:12:36  rrsagent, draft minutes
15:12:36  I have made the request to generate http://www.w3.org/2006/04/07-i18nits-minutes.html fsasaki
15:13:18  -Felix
15:13:19  -Yves_Savourel
15:13:20  -Christian
15:13:21  I18N_ITS(EDIT)10:00AM has ended
15:13:22  Attendees were Yves_Savourel, Felix, Christian