13:45:37 RRSAgent has joined #i18nits 13:45:37 logging to http://www.w3.org/2006/05/03-i18nits-irc 13:46:14 meeting: i18n ITS working group 13:46:22 agenda: http://lists.w3.org/Archives/Member/member-i18n-its/2006AprJun/0056.html 13:46:24 chair: Yves 13:46:27 scribe: Felix 13:46:32 scribeNick: fsasaki 13:50:28 YvesS has joined #i18nits 13:50:45 Hi felix. 13:50:52 Hi Yves 13:51:14 FYI: We have regrets from Goutam, Sebastian and Diane. 13:51:32 o.k., thanks. 13:51:48 regrets: Diane, Goutam, Sebastian 13:52:08 Richard said he would join today to discuss the "renaming" issue of the techniques document 13:54:10 great 13:56:36 I18N_TS()10:00AM has now started 13:56:44 + +33.8.73.03.aaaa 13:58:41 +Felix.a 14:01:48 chriLi has joined #i18nits 14:02:34 +??P19 14:04:24 topic: action items 14:05:40 action: Christian and felix to finish the text for the inclusion issue (Felix creates normative part, christian the non-normative part) (ONGOING) 14:05:47 statement in normative part: 14:05:58 "Selection relies on the information which is given in the XML Information Set [XML Infoset]. ITS applications MAY implement inclusion mechanisms such as XInclude or DITA's [Dita 1.0] conref." 14:07:13 r12a has joined #i18nits 14:07:15 christian: I would use it for the informative part 14:07:16 Yves: the way it is worded is fine. 14:07:20 zakim, dial ishida 14:07:20 ok, r12a; the call is being made 14:07:22 +Ishida 14:07:50 yves: as for the reference to DITA 1.0, make the key upper case 14:07:59 felix: will do 14:08:37 topic: title of techniques document 14:08:45 richard: I propose best practices 14:09:18 .. I discussed with the architecture domain lead, he said it's fine 14:10:00 .. another guy said he does not like the term "best practices", but would not stand against it 14:10:46 .. the document is best practices for schema developers? 14:10:51 yves: also for content developers 14:11:05 .. current title is "XML Internationalization Techniques" 14:11:26 richard: How about "Best practices for XML Internationalization"? 14:12:59 felix: would topics like "integrating i18n related markup in a schema" or "using ITS rules" be covered by the "best practices" title? 14:13:07 richard: all titles are not perfect 14:13:21 .. MW people have used BP as well 14:13:34 .. the document will not be only a techniques document 14:15:07 .. we might also have separate documents for techniques, as we discussed at the Oxford f2f briefly 14:15:47 felix: I'm just wondering if our WG members who developed ITS are fine with the "not on techniques" focused title. If that's o.k.? 14:16:38 christian: It must be sure that ITS (tagset) is in the references 14:16:54 yves: that's for sure, I'm fine with the title 14:18:01 richard: "best practices": it's easier to subsume "techniques" under it 14:18:13 action: Yves to post a mail on the new name proposal for the "techniques document" 14:18:34 action: Christian to write a paragraph describing the requirement for ITS information about non-textual objects (DONE) 14:19:16 yves: result is in the tagset draft and in the requirements document 14:19:47 .. christian said: have the paragraph in a subsection on translatability 14:20:55 .. I proposed to have it as a separate requirement 14:21:02 felix: in the tagset draft: http://www.w3.org/International/its/itstagset/itstagset.html#note-object-selection 14:21:57 christian: so in the requirements doc, there is a new requirement for this? Which must be listed in the introduction of the tagset doc? 14:21:59 yves: yes 14:23:01 christian: I'll work on that 14:23:34 action: Sebastian and Yves to work on integration of modularization section into Techniques document (ONGOING) 14:23:54 action: Yves to write text about within text. (DONE) 14:24:21 yves: I was concerned about non-listed elements: how to deal with them? 14:24:40 .. if an element is bracketed by text, mostly it is inline 14:25:01 .. you could propose mostly all documents, without defining anything 14:25:37 .. I was not sure how to define a default for non-listed elements 14:26:12 .. Felix proposed using as the first rule, which might solve the problem 14:27:14 .. but there are other problems 14:28:45 .. esp. how to actually implement the data category 14:29:12 .. Christian had concerns on the wording "subflow", I proposed "nested" instead 14:29:54 zakim, mute ishida 14:29:54 Ishida should now be muted 14:30:49 http://lists.w3.org/Archives/Public/public-i18n-its/2006AprJun/0151.html 14:31:58 Felix: I'm fine with Yves wording and examples on the issue 14:32:35 action: All make sure "rules" is using non-prefix attributes in all samples and test (DONE) 14:32:51 action: All to try out the "translate" test case to achieve compatibility of output (PENDING) 14:33:01 yves: not important right now, only after last call 14:33:01 chriLi has joined #i18nits 14:33:32 action: All to work on examples: Christian takes 1-9, Felix 10-18, Sebastian 19-28, Yves 29-37 (ONGOING) 14:34:18 christian: I looked at the examples, I did not find anything 14:34:26 felix: I did that as well 14:34:31 yves: me as well 14:34:53 s/Yves 29-37 (ONGOING)/Yves 29-37 (DONE)/ 14:35:15 action: Christian to integrate changes in section 1.1 and 1.2 within 2 weeks. (DROPPED) 14:36:23 christian: I had editing environment issues 14:37:00 action: Christian to propose a wording for the inclusion issue (DROPPED) 14:37:12 action: Everybody to think about which W3C working groups shoud comment on the tagset last call draft. (DONE) 14:37:20 action: Felix to add a rbspanPointer attribute to rubyRule (DONE) 14:37:29 action: Felix to check how license should be handled in the schema. (ONGOING) 14:38:50 christian: sebastian pointed out that a document is different from an application 14:39:51 .. I would wonder if the examples in the spec should also have a time stamp 14:39:57 .. e.g. via XML comments 14:40:16 .. it might give us a way to check that an example is still up to date or outdated 14:40:53 felix: that's fine with me 14:41:20 action: Felix to add time stamps to the examples in the spec 14:41:36 action: Felix to produce descriptions for each entry in the schema. (DONE) 14:42:23 felix: please look at http://www.w3.org/International/its/itstagset/its.xsd 14:42:33 .. all xs:annotation elements 14:44:03 action: all to review the xs:annotation elements in http://www.w3.org/International/its/itstagset/its.xsd (to see if the explanations of ITS markup are o.k.) 14:45:39 christian: should we check the ITS schemas with various editors? 14:45:43 chriLi has joined #i18nits 14:45:58 felix: I'm always checking with Oxygen, XML SPY and emacs 14:46:07 action: Felix to specify the "required-ness" of attributes when needed in the schemas (DONE) 14:46:17 action: Richard to discuss with people whether we should change the title of the "techniques doc" (DONE) 14:46:33 action: Sebastian and Felix to add comment in ODD to have it inside the generated schema to explain how it was created (DONE) 14:46:41 action: Sebastian to get rid of "empties" from generated schema (PENDING) 14:46:57 action: Yves to explore the reference attributes (termRef, locRef) with regard to spliting URI "base versus fragment" (DONE) 14:47:15 http://lists.w3.org/Archives/Public/public-i18n-its/2006AprJun/0156.html 14:47:34 Yves explains the mail 14:49:59 zakim, unmute ishida 14:49:59 Ishida should no longer be muted 14:49:59 christian: I agree with Yves proposal 14:51:28 felix: me too, but I'm not sure if we have time to make the change 14:51:56 richard: we should be careful not to make a change "ourself" after last call 14:52:21 felix: I would have time to make the change, if we agree on it until Monday 14:52:46 action: Yves to post a mail with the proposal at http://lists.w3.org/Archives/Public/public-i18n-its/2006AprJun/0156.html , saying that we decide it until monday 14:53:22 yves: as for terminology markup in various vocabularies: there are a lot of differences 14:54:41 .. it is an example of how to relate different data types 14:55:17 zakim, mute ishida 14:55:17 Ishida should now be muted 14:56:14 FYI, NMTOKEN = "Name Token" 14:56:53 yves: at some point, we might have to drop the referencing issue 14:56:59 nope 14:57:13 .. because it is hard to come up with a general solution 14:58:46 felix: at least people are not hindered to use ITS natively 14:59:40 yves: another problem: currently we have "anyURI" 14:59:47 .. which could also be "#something" 15:00:17 chriLiWhoAlwaysDr has joined #i18nits 15:01:35 action: felix to look on the issue of xml:base, see http://lists.w3.org/Archives/Public/public-i18n-its/2006AprJun/0156.html 15:02:23 christian: I'm looking for vocabularies that have these problems 15:02:28 yves: maybe XHTML? 15:02:51 s/felix to look/felix (possibly others) to look/ 15:03:08 topic: other business 15:03:52 christian: what should we do about the feedback on ITS tagset we got today from Jerry? 15:04:20 yves: I can go through his comments and come up with an answer, and post it to the member list 15:05:48 christian: that would be great 15:07:14 action: Yves to post his thoughts on Jerry's comments on the member list 15:08:43 christian gives thougths on Jerrys mail 15:09:12 bye 15:09:14 -Yves 15:09:18 -Ishida 15:09:20 r12a has left #i18nits 15:09:30 I have made the request to generate http://www.w3.org/2006/05/03-i18nits-minutes.html fsasaki 15:14:05 -Christian 15:14:07 -Felix.a 15:14:09 present: Christian, Felix, Richard, Yves 15:14:09 I18N_TS()10:00AM has ended 15:14:10 Attendees were Felix.a, Yves, Christian, Ishida 15:14:11 I have made the request to generate http://www.w3.org/2006/05/03-i18nits-minutes.html fsasaki 17:01:54 Zakim has left #i18nits