See also: IRC log
<scribe> ACTION: Felix to Ask HP AC rep about HP participation in tech plenary (DONE) but I guess too late for tech plenary, maybe we find some body in general [recorded in http://www.w3.org/2006/02/21-i18ncore-minutes.html#action01]
<scribe> ACTION: Felix to schedule a meeting with WS folks on Thursday and Friday (DONE) but not successfuly the meeting will be on Monday / Tuesday, within the WSDL group [recorded in http://www.w3.org/2006/02/21-i18ncore-minutes.html#action02]
<scribe> ACTION: Francois to review the PLS spec (ONGOING) [recorded in http://www.w3.org/2006/02/21-i18ncore-minutes.html#action03]
<scribe> ACTION: all except Mary to read ws-i18n before the tech plenary (ONGOING) [recorded in http://www.w3.org/2006/02/21-i18ncore-minutes.html#action04]
<scribe> ACTION: Felix to ask Addison and Mark about language tags in CSS (ONGOING) hope to be able to talk to them at the Unicode conference [recorded in http://www.w3.org/2006/02/21-i18ncore-minutes.html#action05]
<scribe> ACTION: francois / all to go through charmod norm comments (ONGOING) [recorded in http://www.w3.org/2006/02/21-i18ncore-minutes.html#action06]
francois: that will mostly happen during the tech plenary
<scribe> ACTION: http://www.w3.org/International/core/reviews [recorded in http://www.w3.org/2006/02/21-i18ncore-minutes.html#action07]
felix: 3 new documents:
... xml schema data types
... wsdl addr 1.0
... p3p 1.1
...
http://www.w3.org/TR/2006/WD-xmlschema11-2-20060217/
francois: real issues with xml schema data types
... with time and date stuff
felix: they have taken some stuff from xquery
francois: they have data types in different name spaces
felix: that might be solved soon
on p3p 1.1: http://lists.w3.org/Archives/Public/public-i18n-core/2006JanMar/0197.html
richard: could we get martin to review that?
<scribe> ACTION: felix to ping martin to review p3p 1.1 [recorded in http://www.w3.org/2006/02/21-i18ncore-minutes.html#action08]
<scribe> ACTION: felix to ask mark davis to participate in the review of xml schema data types [recorded in http://www.w3.org/2006/02/21-i18ncore-minutes.html#action09]
<scribe> ACTION: mary to review wsdl addr 1.0 http://www.w3.org/International/core/reviews#ws-addr-wsdl [recorded in http://www.w3.org/2006/02/21-i18ncore-minutes.html#action10]
francois: we should set mary as the main reviewer
felix: will do
<r12a> http://www.w3.org/International/tutorials/tutorial-lang/
<r12a> http://www.w3.org/QA/2006/02/content_negotiation.html
richard: wrote comments on this
... I will ask them to get i18n review stuff by i18n geo or core people
felix: do you want us to go through your comments and send them as core comments?
richard: no, don't need to make this formal at this stage. I'll just copy to the list
felix: what issues did you have with the article?
richard: they miss a bunch of stuff about why one should use language negation
... and a lot of other
stuff.
felix: no update
francois: we will meet them at the tech plenary
... what is open for CDF?
felix: IRI stuff
... and spelling errors, we don't have to follow these
<r12a> http://www.w3.org/International/reviews/0602-mwbp10/
richard: comment 7:
felix: will it be o.k. to give them the comments later?
richard: the deadline was last week
felix: I will make the changes tomorrow
richard: in Unicode you need more bytes for indic scripts
... it is a true statement, why include it
here?
francois: one point that is worth making:
... if you have fields with fixed length
... they might not
be big enough
... if they are created for latin languages
richard: what do you propose?
felix: to say "take lenght issues for forms into account"
francois: people try to take band width into account
... so they have to be careful of script related
issues
richard: so to say "you may want to consider special compression forms of Unicode"
francois: an additional point: if you want to translate to a different encoding, a different bandwith might be necessary
<scribe> ACTION: richard to try a formulation for comment 9 [recorded in http://www.w3.org/2006/02/21-i18ncore-minutes.html#action11]
felix: I'll try s.t. before as well
comment 10
richard: what is the issue?
francois: in a mobile, you might not have the option to get translations
richard: e.g. the pull down menues
francois: yes. it is not technically impossible, but I don't know if it exists
felix: example of a lexicon which can only be accessed from a non-mobile HP
... and as the comment: make
this obvious in the comment
richard: have a wording on it tomorrow?
<scribe> ACTION: felix and richard to finish up mwbp comments tomorrow (richard's time) [recorded in http://www.w3.org/2006/02/21-i18ncore-minutes.html#action12]
comment 16
richard: we say "has to be made"
... how about "would be"?
felix: o.k.
richard: comment 24
felix: I'll go trough it tomorrow
comment 28
francois: to encourage them to use standard mechanisms for lang decl?
richard: they should point to the standard mechanisms
francois: good thing
... I would add:
... there may be a mobile specific mean
... use the
standards for language, if there is s.t. else (mobile specific), go ahead
richard: o.k., I'll change that
francois: use the standards as far as possible, then go behind it
richard: last comment:
... encourage Unicode
all agree on that
francois: filled everthing, except for the last slot
... the slot for ws will be empty
felix: how about using more time for charmod (norm)?
francois: some items can be short, e.g. ltli
... fine everybody?
... 90 minutes o.k. for ws i18n?
richard: tech plenary is very useful
... to talk to other groups
... the 4 days as i18n core
<scribe> ACTION: felix to set up a meeting with xml core / xml schema people about charmod norm [recorded in http://www.w3.org/2006/02/21-i18ncore-minutes.html#action13]