13:58:39 RRSAgent has joined #i18nits 13:58:39 logging to http://www.w3.org/2006/04/05-i18nits-irc 13:58:47 meeting: i18n ITS working group 13:58:50 chair: Yves 13:58:51 scribe: Felix 13:58:57 scribeNick: fsasaki 13:59:12 agenda: http://lists.w3.org/Archives/Member/member-i18n-its/2006AprJun/0007.html 14:00:09 I18N_TS()10:00AM has now started 14:00:15 + +1.303.516.aaaa 14:01:20 +[IPcaller] 14:01:23 - +1.303.516.aaaa 14:01:24 + +1.303.516.aaaa 14:01:44 zakim, who is here? 14:01:44 On the phone I see +1.303.516.aaaa, [IPcaller] 14:01:45 On IRC I see RRSAgent, chriLi, Zakim, fsasaki, YvesS 14:02:00 zakim, [IPcaller is Felix 14:02:00 +Felix; got it 14:03:07 zakim, [1.303.516.aaaa is Yves 14:03:07 sorry, fsasaki, I do not recognize a party named '[1.303.516.aaaa' 14:03:20 zakim, +1.303.516.aaaa is Yves 14:03:20 +Yves; got it 14:03:27 zakim, who is here? 14:03:29 On the phone I see Yves, Felix 14:03:33 On IRC I see RRSAgent, chriLi, Zakim, fsasaki, YvesS 14:04:10 +??P15 14:04:24 zakim, ??P15 is Christian 14:04:24 +Christian; got it 14:05:53 regrets: Sebastian, Andrzej 14:05:58 topic: action items 14:06:33 topic: versioning 14:06:36 http://www.w3.org/Bugs/Public/show_bug.cgi?id=2876 14:07:04 Yves: last summary was to have an its:version attribute, to put at the top of the document 14:07:24 .. Martin had some comments about the future version 14:07:35 Felix: would it be in the rules element as well? 14:07:39 +Diane_Stoick 14:08:43 diane has joined #i18nits 14:08:55 Yves: if it is an external file which is not linked 14:09:12 .. if it has a version, you take the rules from the top level element in that file 14:10:20 .. XSLT puts the version in the root element as well 14:12:26 Christian: I'd go for a version attribute both at the top of the doc and the rules element 14:12:30 Felix: XSLT way: 14:12:33 [[[Definition: There are a number of standard attributes that may appear on any XSLT element: specifically version, exclude-result-prefixes, extension-element-prefixes, xpath-default-namespace, default-collation, and use-when.]]] 14:13:27 Yves: rules can have their own version, they are prossed before the other ones 14:14:14 Christian: We could say: If you include a rules element 14:14:26 .. in your document, you could put the version identifier in the rules element 14:14:47 .. if you don't have a rules element, then put it on the top most element of the host vocabulary 14:16:21 test 14:16:31 Yves: do we need that for version 1? 14:17:35 We don't want this, right? 14:19:00 Yves: why not? 14:19:13 .. the rules element is s.t. you can link 14:19:21 .. so it may be of a different version 14:21:07 Christian: you should have either 14:22:57 Yves: summary: either a version number at the top of the document, or in the rules element 14:23:05 Christian: no, always in the rules element 14:23:55 Yves: what if you would have both? 14:24:55 Felix: for the top of the document, the version attribute at the root element counts, for the rules element, the mandatory attribute at the rules element 14:27:03 Yves: how about having a version attribute at top of the document only? That could be used for external rules as well 14:27:14 I suggest: It is incorrect to have its:version at the top-level if there exists an its:Rules 14:27:15 I suggest: It is incorrect to have its:version at the top-level if there exists an its:Rules 14:28:53 Yves: if you have rules, it is the rules version 14:29:09 .. if you have local only, it is local only, if you have both, it is the rules which wins 14:30:03 Diane: I think we need that information somewhere 14:30:16 Yves: we can try that 14:30:40 .. so let's go for that 14:31:43 action: Yves to write a paragraph on versioning for the tagset draft 14:32:17 topic: Decide on term "localization properties" 14:32:47 Yves: everybody agrees that we will have no change on this? 14:33:44 action: Yves to summarize the terminology discussion on "localization properties" 14:33:49 topic: Decide on term "data category" 14:33:53 Yves: again agreement 14:34:02 action: Yves to summarize "loc prop" discussion 14:34:23 topic: conformance section 14:34:37 Yves: any further comments? 14:35:33 .. according for our schedule, that will be an item this week 14:36:00 topic: further action items 14:36:16 action: Editor's of the techniques document: give examples how to use its:locInfoRef (ONGOING) 14:36:29 Yves: if you have comments, please tell me 14:38:11 Felix: we could use the period of ITS tagset last call for that 14:38:30 action: Richard to describe an additional level of conformance for Ruby (PENDING) 14:38:58 action: Felix to remind Richard of ruby additional level 14:39:21 action: Spec editors to integrate discussion result about bugs 2881,2,3 (PENDING) 14:39:58 Yves: we wait until Friday to see if people agree 14:40:08 action: Felix to write a mail to the data category thread (DROPPED) 14:40:36 action: Yves to see what problems could happen if there is no prefix at rule elements? (DONE) 14:40:51 Yves: I tried that with my implementations, but there were no problems 14:41:54 Felix: in the next draft, it will still be with prefixes, due to editing problems 14:42:05 action: Yves to write a mail about his finding about the usage of "overriding" (DONE) 14:42:57 Yves: even Richard used "overriding" 14:43:21 .. Sebastian gave two definitions 14:44:55 action: Sebastian to give feedback on the overriding change proposal, Diane to look at it again 14:45:28 topic: last call preparation 14:46:51 http://www.w3.org/International/its/itstagset/itstagset.html 14:48:39 Felix: please give feedback of my changes with regard to syntax changes 14:48:47 Christian: I made only initial changes 14:49:24 .. it will be a section "introduction" and "basic concepts" 14:49:37 .. I will work on it later today, and tomorrow 14:51:44 Yves: how about publishing on Friday? 14:52:02 Felix: o.k., Friday next week 14:52:50 .. with final input of Christian on Friday this week 14:54:13 .. as for groups, please tell me from whom you want to have feedback 14:54:19 yves: how about XSLT people? 14:54:30 christian: is it good design to have localizable in XSLT? 14:54:34 yves: it is reality 14:55:40 action: everybody to think about which W3C working groups shoud comment on the tagset last call draft 14:55:45 topic: topics for next week 14:55:52 yves: conformance to be finalized 14:56:00 .. element within text 14:56:33 .. ruby 14:58:00 action: everybody to look at rescheduling proposed at http://lists.w3.org/Archives/Member/member-i18n-its/2006AprJun/0001.html 14:58:29 topic: next face-to-face meeting (after Oxford) 14:59:44 felix: end of last call period would be good 14:59:52 yves: how about specific locations? 15:00:10 yves: I would propose "Boulder" 15:00:21 .. it is far for people in Europe 15:00:57 -Diane_Stoick 15:01:02 felix: as we discuss last call issues, we need as many people as possible 15:03:08 topic: XTech paper 15:03:13 felix: deadline is http://xtech06.usefulinc.com/content/speakers 15:04:30 -Felix 15:04:32 -Yves 15:04:41 .. first create input to tag set draft, then to the XTech paper 15:04:55 Yves: on Friday, we will discuss Christian's changes 15:04:56 -Christian 15:04:58 I18N_TS()10:00AM has ended 15:04:59 Attendees were [IPcaller], Felix, Yves, Christian, Diane_Stoick 15:05:09 present: Christian, Diane, Felix, Yves 15:05:43 rrsagent, make log public 15:05:54 rrsagent, draft minutes 15:05:54 I have made the request to generate http://www.w3.org/2006/04/05-i18nits-minutes.html fsasaki 15:07:59 GoutamSaha has joined #i18nits 15:08:58 Hi Christian, Hi Diane 15:35:41 bye 16:25:53 Zakim has left #i18nits