See also: IRC log
<scribe> scribe: Felix
<scribe> scribeNick: felix-boulder
Proposal for the agenda: we go through all issues listed at http://lists.w3.org/Archives/Member/member-i18n-its/2006JulSep/0125.html , and change the Bugzilla entries on the fly
<r12a> since it puts less strain on ears and phone batteries
<r12a> register ? i have skype (but only the version that allows computer to computer calls - not dialling real numbers)
<r12a> correct
<rahtz_> any skype can call real numbers, surely? you just have to pay...
<r12a> is zakim booked for the whole 3 days ?
yes
http://lists.w3.org/Archives/Member/member-i18n-its/2006JulSep/0125.html
Yves: list of items we have to go
through
... I would like to go from top to bottom
... if you want to discuss a particular item with more time,
please tell us
Yves: closed.
<scribe> Closed. commentor satisfied.
Sebastian: some issue at Christian's proposal:
<rahtz_> "ITS is a technology to easily create XML which can be internationalized and localized effectively"
(Richard made some explanation, Sebastian is fine)
<scribe> Closed. The modularization is now part of the BP document.
Spelling error. Closed. Commentor statisfied.
<scribe> Closed. Commentor satisified.
Felix: I also wrote a mail also to Daniel Glazman, he did not reply.
<scribe> Closed.
About the relation of terminology data category to existing standards for terminology
<scribe> Closed.
about the version of XPath
Yves: do we need an indicator which says which version of XPath is used?
<scribe> ACTION: Felix to make the change for 3321 [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action01]
Yves: do we need meta-data to indicate the XPath version in ITS?
Sebastian: XPath 2 does not exist
formally. We don't know "legally" if there will be a version
2
... version 2 might say s.t. about versions
Yves: CSS also has no version info
(discussion on whether we should have a definite reference to 1.0 or a general reference)
Richard: two questions: successor
versus not-successor, where I agree
... the other question is if we need version info
we close the issue, accept Michael's proposal , and two action items:
<scribe> ACTION: Richard to bring this to the architecture domain to make a sense check [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action02]
<scribe> ACTION: Felix to make the change in the draft [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action03]
Felix: sorry, this is for the BP document, it should not be here
<r12a> http://www.w3.org/International/its/itstagset/itstagset.html
<scribe> ACTION: Felix to fix the "latest generation generation" in the document [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action04]
currently, there is no modification after the LC
about directionality
Yves: where do we need the explanatation?
<r12a> http://www.w3.org/International/its/itstagset/itstagset.html
Richard: 6.5.1
<r12a> # lro: Left-to-right override. The effect of this attribute is defined by the CSS2 rule:
<r12a> *[dir="lro"] { unicode-bidi: bidi-override; direction: ltr}
<r12a> # rlo: Right-to-left override. The effect of this attribute is defined by the CSS2 rule:
<r12a> *[dir="rlo"] { unicode-bidi: bidi-override; direction: rtl}
<r12a> from http://www.w3.org/TR/2005/WD-xhtml2-20050527/mod-bidi.html#adef_bidi_dir
<r12a> http://www.w3.org/TR/CSS21/visuren.html#propdef-direction
<scribe> ACTION: Richard to check the relation between CSS 2 to CSS 2.1 (due to 13 September) [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action05]
summary: for now we refer to CSS 2, and copy the text of XHTML 2,
the text explains the different values
<scribe> ACTION: Felix to make the change in the spec [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action06]
<scribe> Closed. Now part of BP.
<scribe> closed.
<GoutamSaha> Good Morning Felix, Yves and Richard
"No defined behavior if external rules can't be accessed"
Summary: Discussed at http://www.w3.org/2006/09/06-i18nits-minutes.html#item14 . Resolution of WG:
(still discussions)
Summary: the WG decides to make no change
Richard: behavior is currently undefined. Implementors are encouraged to use common sense in implementing ITS processors
Yves: "common sense and generate errors"
Discussed at http://www.w3.org/2006/09/06-i18nits-minutes.html#item14 . Resolution of the WG: the behavior is currently undefined. Implementors are encouraged to use common sense and generate errors when needed in implementing ITS processors.
<scribe> ACTION: Felix to ask Addison for the correct reference to BCP 47 [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action07]
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3458#c2
Yves: put this in the
implementation section?
... 6.2.2
<scribe> ACTION: Felix to make the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action08]
<scribe> ACTION: Felix to draft a text how to work-around the problem of arbitrary nesting of its:span in ruby (due to 13 September) [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action09]
nesting of its:span in ruby
Felix will make changes to the draft and send replies to i18n core
<scribe> ACTION: Felix to make i18n core related changes not later than Monday and send mails to i18n core and ask for a discussion slot on the core call [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action10]
Richard: say in your mail that
people should read the mails before the meeting
... and decide what you want to discuss
... we will not go through everything during the meeting
Summary: we change the name of the data category to localization note, and change the markup to locNote
Yves: no further explanation necessary
<scribe> ACTION: Felix to make the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action11]
about the role of term info
<scribe> ACTION: Yves to track the proposal [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action12]
<scribe> ACTION: Felix to update the document and to go back to i18n core [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action13]
<scribe> ACTION: Felix to make the change and to go back to i18n core [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action14]
Yves: tomorrow we will start at 9 Denver time, that is: an hour later than today
<felix-out> ACTION: Action: Felix to make the change and to go back to i18n core [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action15]
<felix-out> Yves: put that into the implementation section.
<felix-out> ACTION: editors to make the change in the implementation section. [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action16]
http://lists.w3.org/Archives/Member/member-i18n-its/2006JulSep/0125.html
<YvesS> The attributes [todo: list the values.] which contain resource identifiers MUST contain IRI [ref. to RFC 3987] values to easy the adoption of ITS in international usage scenarios. The ITS schemas in App. A are not normative. Hence this specification defines no validation requirements for IRI values in ITS markup.
<YvesS> For processing of these values, relying on IRIs imposes no specific requirements. The reason is that the processing happens on the infoset level, where no difference between IRIs and URIs exists."
Felix: this mail has a proposal for IRI, see text above
Yves: get rid of the following:
The ITS schemas in App. A are not
normative. Hence this specification defines no validation requirements
for IRI values in ITS markup.
Felix: fine by me
Yves: we will put the stuff about IRI at the end of sec. 5.1
Felix: and change the the wording to IRI for the ref attributes, like locNoteRef
resolution: we put we proposal at http://lists.w3.org/Archives/Member/member-i18n-its/2006JulSep/0125.html in a new section 3.5 , with the modifications described here, and change the wording of ref attributes to IRI
<scribe> ACTION: Felix to make the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action17]
<YvesS> http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0253.html
my proposal:
So my proposals:
- delete conformance clause 2-2 in the draft (which is about normative
references to the ruby spec and XHTML 2),
- cite Ruby, XHTML 2.0 (or HTML 4.01) and the IRI spec only
informatively, and
- tell implementers in a non-normative section what they should do - on
top of ITS.
Richard: fine by me
<scribe> ACTION: Felix to make the change for ruby and XHTML (dir) [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action18]
put this into the implementation sections
<scribe> ACTION: Felix to make the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action19]
<scribe> ACTION: Felix to change must to RFC2119 style, integrate CL change in the draft and go back to i18n core [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action20]
<scribe> ACTION: Felix to make the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action21]
discussion about the need of verbatim in the embedded examples. Proposal: check if XInclude like in http://www.w3.org/TR/2004/REC-xinclude-20041220/#xml-as-text-example would do the job
<scribe> ACTION: Felix to check xinclude for examples [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action22]
<scribe> ACTION: felix to integrate CLs change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action23]
<scribe> ACTION: Felix to integreate CLs change and to go back to i18n core [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action24]
<scribe> ACTION: Felix to update examples and text , see http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0201 [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action25]
<scribe> ACTION: Felix to integrate the explanations in the ODD file and change the examples [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action26]
<scribe> ACTION: Felix to make the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action27]
we decided to get rid of the sentence "The terminology data category is used to mark terms."
<scribe> ACTION: Felix to make the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action28]
it is a dublication
<scribe> ACTION: Felix to make the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action29]
WG needs to discuss: do we need to move to xml spec, to allow others than Felix and Christian to make changes?
standardized wording issue is currently at the bottom of TODO list, we see if we have time
Yves: fine by me
<scribe> ACTION: Felix to implement CLs text in the draft [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action30]
Yves: this will be rewritten
Felix: according to http://www.w3.org/2006/09/06-i18nits-minutes.html#item11
<scribe> ACTION: Felix to integrate the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action31]
<scribe> ACTION: Felix to integrate the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action32]
<scribe> ACTION: Felix to integrate the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action33]
<scribe> ACTION: felix to make the changes [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action34]
We need to go through this in detail later, during the editing
Yves: make the change as CL did
<scribe> ACTION: Felix to make the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action35]
<scribe> ACTION: Felix to integrate the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action36]
<scribe> ACTION: Felix to make the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action37]
We agree that it this is on the bottom of the TODO list. If we don't have time (which seems to be likely), we will drop it
<scribe> ACTION: Felix to make the change for: locNotePointer, langPointer, locNoteRefPointer, termInfoRefPointer, rubyPointer, rbPointer, rtPointer, rpPointer, rbcPointer, rtcPointer, rbspanPointer, termInfoPointer [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action38]
<scribe> ACTION: Felix to do implement the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action39]
<scribe> ACTION: Felix to make the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action40]
<scribe> ACTION: Felix to implement the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action41]
proposal: change table in sec. 6.1
remove last column
have three columns: defaults (e.g. translate=yes for elements, translate=no for elements)
inheritance (only elements, elements and attributes, or none (for terminology and ruby and "elements within text")
and overriding behaviour (yes or "not applicable". yes: everything except terminology, ruby and "elements within text")
<scribe> ACTION: WG to look at the change [recorded in http://www.w3.org/2006/09/06-i18nits-minutes.html#action42]
Input to rewording:
The datatype of termInfoRef is xs:anyURI. To point to a link to a term reference in the current document, a termInfoRefPointer attribute can be used.
Rewording needs to mention termInfoPointer as well, with an example
mentioned already
This is scribe.perl Revision: 1.127 of Date: 2005/08/16 15:12:03 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/arbitrary/arbitrary nesting of its:span in ruby (due to 13 September)/ Succeeded: s/info set/infoset/ Succeeded: s/name/the wording/ Succeeded: s/to/do/ Succeeded: s/others/others than Felix and Christian/ Succeeded: s/them/it/ Succeeded: s/ruby)/ruby and "elements within text")/ Found Scribe: Felix Found ScribeNick: felix-boulder Default Present: Yves_Savourel, Sebastian_Rahtz, Richard Present: Yves_Savourel Sebastian_Rahtz Richard Agenda: http://lists.w3.org/Archives/Member/member-i18n-its/2006JulSep/0124.html Got date from IRC log name: 6 Sep 2006 Guessing minutes URL: http://www.w3.org/2006/09/06-i18nits-minutes.html People with action items: editors felix richard wg yves[End of scribe.perl diagnostic output]