- From: Felix Sasaki <fsasaki@w3.org>
- Date: Wed, 11 Oct 2006 22:55:47 +0900
- To: public-i18n-its@w3.org
... are at http://www.w3.org/2006/10/04-i18nits-minutes.html and below
as text. Sorry for the delay.
- Felix
[1]W3C
[1] http://www.w3.org/
i18n ITS Working Group
4 Oct 2006
[2]Agenda
[2]
http://lists.w3.org/Archives/Member/member-i18n-its/2006OctDec/0002.html
See also: [3]IRC log
[3] http://www.w3.org/2006/10/04-i18nits-irc
Attendees
Present
Christian, Felix, Sebastian, Yves
Regrets
Andrzej, Richard
Chair
Yves
Scribe
Felix
Contents
* [4]Topics
1. [5]action items
2. [6]issues not closed
3. [7]things to do for CR preparation
4. [8]discussion of (new) charter
* [9]Summary of Action Items
_________________________________________________________
<scribe> agenda:
[10]http://lists.w3.org/Archives/Member/member-i18n-its/2006OctDec/0
002.html
[10]
http://lists.w3.org/Archives/Member/member-i18n-its/2006OctDec/0002.html
action items
<scribe> ACTION: All to think about features at risk (ONGOING)
[recorded in
[11]http://www.w3.org/2006/10/04-i18nits-minutes.html#action01]
Yves: posted a list
Felix: I would say we need to list at least the ruby attributes used
for pointing
... Sebastian and me can work on everything , right?
Sebastian: yes. What we do is just "reporting"
Felix: that is enough
Sebastian: it is not guarenteed that it happens simuntaneously,
might be a pipeline
Yves: so all features would be twice, maybe even more
... do we need really the ruby pointers as features at risk
Sebastian: might technically make sense
[12]http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0
425.html
[12]
http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0425.html
Felix: do we need to mark the MUST in the statement as a feature at
risk?
Yves: I don't see the problem
(Christian reformulates the mail)
Yves: we could put this as features at risk, although I'm not sure
what the problem is
... what would happen if we have this as feature at risk and nobody
implements it?
felix: we would have to remove the MUST statement and have a
non-normative reference to RFC 4646
Christian: our conformance clauses don't go to the level of values
... for the processing expectations
Yves: let's flag it, just to be sure
RESOLUTION: the "MUST" for langRule and the pointing mechanisms for
ruby are features at risk
<scribe> ACTION: Felix to make the change "not possible" with "not
applicable" and go back to i18n core (DONE) [recorded in
[13]http://www.w3.org/2006/10/04-i18nits-minutes.html#action02]
Felix: did the change. This was not an i18n core comment
<scribe> ACTION: Yves to add sumaries for issues in Bugzilla (DONE)
by Felix ;) [recorded in
[14]http://www.w3.org/2006/10/04-i18nits-minutes.html#action03]
<scribe> ACTION: Yves to send mails for replies to comments
(ONGOING) [recorded in
[15]http://www.w3.org/2006/10/04-i18nits-minutes.html#action04]
[16]http://www.w3.org/International/its/itstagset/lc-replies.html
[16] http://www.w3.org/International/its/itstagset/lc-replies.html
<scribe> ACTION: Felix to go back to Steven Pemperton with issue
[17]http://www.w3.org/International/its/itstagset/lc-replies.html#is
sue-3331 [recorded in
[18]http://www.w3.org/2006/10/04-i18nits-minutes.html#action05]
[17]
http://www.w3.org/International/its/itstagset/lc-replies.html#issue-3331
<scribe> ACTION: Everybody to look at the draft, to see if it is
ready for CR transition (ONGOING) [recorded in
[19]http://www.w3.org/2006/10/04-i18nits-minutes.html#action06]
<scribe> ACTION: Sebastian looking at the 'rbspanrbspan' problem
(PENDING) [recorded in
[20]http://www.w3.org/2006/10/04-i18nits-minutes.html#action07]
Yves: we could find a workaround
... the other problem is more important, that is the list of
attributes
<scribe> ACTION: Yves to add a bug for the removal of rbPointer
[recorded in
[21]http://www.w3.org/2006/10/04-i18nits-minutes.html#action08]
issues not closed
see [22]http://www.w3.org/International/its/itstagset/issues
[22] http://www.w3.org/International/its/itstagset/issues
Yves: let's vote for CR today, given that the open issues are
resolved
Sebastian: o.k.
RESOLUTION: WG votes for CR under the condition that issues
[23]http://www.w3.org/Bugs/Public/show_bug.cgi?id=3514 and
[24]http://www.w3.org/Bugs/Public/show_bug.cgi?id=3466 are closed
[23] http://www.w3.org/Bugs/Public/show_bug.cgi?id=3514
[24] http://www.w3.org/Bugs/Public/show_bug.cgi?id=3466
things to do for CR preparation
see
[25]http://lists.w3.org/Archives/Member/member-i18n-its/2006OctDec/0
005.html
[25]
http://lists.w3.org/Archives/Member/member-i18n-its/2006OctDec/0005.html
Yves volunteers to do the change log
[26]http://lists.w3.org/Archives/Member/chairs/2006JulSep/0027.html
[26] http://lists.w3.org/Archives/Member/chairs/2006JulSep/0027.html
Sebastian: I will do the implementation report tonight
Yves: other things to do?
[27]http://www.w3.org/International/its/itstagset/lc-replies.html
[27] http://www.w3.org/International/its/itstagset/lc-replies.html
Yves: fine with the presentation. I don't like the colors so much
... maybe have more space between each issue
... and have at the end of the doc s.t. like "this is the end"
<scribe> ACTION: felix to adopt change proposals from Yves for
[28]http://www.w3.org/International/its/itstagset/lc-replies.html
[recorded in
[29]http://www.w3.org/2006/10/04-i18nits-minutes.html#action09]
[28] http://www.w3.org/International/its/itstagset/lc-replies.html
discussion of (new) charter
Yves: have not thought about that much yet
Sebastian: no thought about that yet
Christian: work on errata
... helping people with implementations
Felix: for example test suite productions?
Christian: plays a role
Yves: trying to evangalize
Christian: yes. But main point would be to do errata
... and to ensure interoperability
Felix: how about issue
[30]http://www.w3.org/Bugs/Public/show_bug.cgi?id=3126 ? Is it o.k.
to postone it?
[30] http://www.w3.org/Bugs/Public/show_bug.cgi?id=3126
Christian: not sure
... depends on the timeline
Felix: we could also have a short charter e.g. for 10 months, and
have a new one after that with new features in ITS 1.x
Yves: the BP document should be in the new charter as well
Adjourn
Summary of Action Items
[NEW] ACTION: felix to adopt change proposals from Yves for
[31]http://www.w3.org/International/its/itstagset/lc-replies.html
[recorded in
[32]http://www.w3.org/2006/10/04-i18nits-minutes.html#action09]
[NEW] ACTION: Felix to go back to Steven Pemperton with issue
[33]http://www.w3.org/International/its/itstagset/lc-replies.html#is
sue-3331 [recorded in
[34]http://www.w3.org/2006/10/04-i18nits-minutes.html#action05]
[NEW] ACTION: Yves to add a bug for the removal of rbPointer
[recorded in
[35]http://www.w3.org/2006/10/04-i18nits-minutes.html#action08]
[NEW] ACTION: Yves to add sumaries for issues in Bugzilla (DONE) by
Felix ;) [recorded in
[36]http://www.w3.org/2006/10/04-i18nits-minutes.html#action03]
[31] http://www.w3.org/International/its/itstagset/lc-replies.html
[33]
http://www.w3.org/International/its/itstagset/lc-replies.html#issue-3331
[PENDING] ACTION: All to think about features at risk [recorded in
[37]http://www.w3.org/2006/10/04-i18nits-minutes.html#action01]
[PENDING] ACTION: Everybody to look at the draft, to see if it is
ready for CR transition [recorded in
[38]http://www.w3.org/2006/10/04-i18nits-minutes.html#action06]
[PENDING] ACTION: Sebastian looking at the 'rbspanrbspan' problem
[recorded in
[39]http://www.w3.org/2006/10/04-i18nits-minutes.html#action07]
[PENDING] ACTION: Yves to send mails for replies to comments
[recorded in
[40]http://www.w3.org/2006/10/04-i18nits-minutes.html#action04]
[DONE] ACTION: Felix to make the change "not possible" with "not
applicable" and go back to i18n core [recorded in
[41]http://www.w3.org/2006/10/04-i18nits-minutes.html#action02]
[End of minutes]
_________________________________________________________
Minutes formatted by David Booth's [42]scribe.perl version 1.127
([43]CVS log)
$Date: 2006/10/11 13:53:49 $
[42] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[43] http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 11 October 2006 13:56:00 UTC