See also: IRC log
<scribe> ACTION: Felix to write a mail about possibility for SVG tiny specific IRI tests to martin and the i18n core list (ONGOING) [recorded in http://www.w3.org/2006/10/10-i18ncore-minutes.html#action02]
Francois: waiting for a reply from Chris Lilley
<scribe> ACTION: Francois to give input to wiki for the LTLI summary (ONGOING) [recorded in http://www.w3.org/2006/10/10-i18ncore-minutes.html#action01]
Francois: started on that
<scribe> ACTION: Richard to send his mail on bidi-override scope in CSS2 and CSS 2.1 to www-international and the style-list, and copy the BIDI-unicode list (ONGOING) [recorded in http://www.w3.org/2006/10/10-i18ncore-minutes.html#action03]
<scribe> ACTION: Francois to build a current issues list on charmod norm (PENDING) [recorded in http://www.w3.org/2006/10/10-i18ncore-minutes.html#action04]
<scribe> ACTION: Felix to look for possible participants (esp. implementors) for the WS i18n work (ONGOING) [recorded in http://www.w3.org/2006/10/10-i18ncore-minutes.html#action05]
Felix: made a presentation at the WS-CG, need to do more recruting
Richard: we would only reply to the original question, which shoud be fine now
... I'd just say: fine, close
it
Francois: fine with me as well
Richard: link to the the place in the document were the changes were made
iri description at http://www.w3.org/International/its/itstagset/itstagset.html#iri-usage
Richard: IRI section looks o.k.
Francois: future proove is maybe a problem. If there are changes it is easy to loose track of that section and update it
Richard: better say "RFC 3987 or its successor"
<scribe> ACTION: Felix to change the reference to RFC 3987 to "RFC 3987 or its successor" and go back to Martin [recorded in http://www.w3.org/2006/10/10-i18ncore-minutes.html#action06]
mail from Martin at http://lists.w3.org/Archives/Public/public-i18n-core/2006OctDec/0003.html
Francois: wait another week for Martin, Felix to ping Martin and Mary
<scribe> ACTION: Felix to ping Martin and Mary on the XML Schema issue [recorded in http://www.w3.org/2006/10/10-i18ncore-minutes.html#action07]
http://www.w3.org/TR/2006/WD-owl-time-20060927/#timezone
http://lists.w3.org/Archives/Member/member-i18n-core/2006Oct/0001.html
Francois: Mark said the ontology is too western centric
... e.g. durations are not translatable directly
between calendars
Felix: how should the change the ontology model to avoid this translation problem?
... maybe just tell them
the problem, they need to fix it
... we could also point them to http://www.w3.org/TR/timezone/
... our WG note on timezone, e..g with regard to terminology ("offest"
versus "timezone")
... they are also not aware of Olson IDs
<scribe> ACTION: everybody to look for issues in http://www.w3.org/TR/timezone/ until next call [recorded in http://www.w3.org/2006/10/10-i18ncore-minutes.html#action08]
http://lists.w3.org/Archives/Public/public-i18n-core/2006OctDec/0000.html
Felix: just to make you aware of this
... no need to follow up
Richard: currently the ws i18n wg is expected to work on ws i18n wg and LTLI document
... Felix and plh
discussed whether the LTLI spec should be in the ws i18n WG
... I understand the rationale of the idea, it goes into the direction to have a
general specification WG
Francois: historically LTLI is based on ws i18n, but if LTLI is relevant for other groups as well, we could have it in the same group as the charmod specs
Richard: how about having the "i18n development WG"?
Francois: I'd prefer "infrastructure", but could live with "development"
Richard: o.k., let's go back to Philippe and discuss
Felix I will attend the XSL-FO workshop next week in Germany
Francois: we want to give input, would be good to get a summary of the workshop, if available
Felix: I will take care of that
adjourned