See also: IRC log
http://lists.w3.org/Archives/Member/member-i18n-core/2006Jan/0041.html
Felix conclusion: we can continue to refer to rfc 3066 or its successor
Francois: it would be good to have an FAQ on this
Richard: I have asked Addison to write an FAQ
Francois: For the moment we tell spec writers to point to RFC 3066 and its successor
Francois: explains the issue, described in
http://lists.w3.org/Archives/Public/public-i18n-core/2006JanMar/0126.html
... it is a general thing of escaping characters
... we want
to tell them to use escaping as in XML or Java
... not in URL where the bytes are escaped
... so "use the 'hex' code for each character
that you cannot have", and that's it
Francois: Did not have time to look at this
Felix: Did not have time to look in this, should do it before the tech plenary, to be able to talk to the XML / XSL / XQuery / XML Schema folks
<scribe> ACTION: francois / all to go through charmod norm comments of QT people etc. (ONGOING) [recorded in http://www.w3.org/2006/01/31-i18ncore-minutes.html#action01]
http://lists.w3.org/Archives/Public/public-i18n-core/2006JanMar/0133.html
comment 1 on CSS
felix: let's give this up
francois: spec's are not tutorials
comment 2 on CSS
francois: In that case it is a source of confusion
... all it requires saying "this is not the type as in
XML Schema"
felix: let's try again
comment 3 on CSS
francois: you see various usages of selectors (css, w3c selectors)
... they need to clarify this
felix: go back to them to clarify their usage with a consistent terminology
comment 5 on CSS
Francois: o.k. with that
comment 6 on CSS
Francois: a problem with definition of conformance
... we should push back on them to define conformance
with respect to the binding mechanism
... we don't have to insist of prescribing it
comment 8 on CSS
comment 11 on CSS
http://www.w3.org/TR/2005/WD-css3-selectors-20051215/#pseudo-classes
<fyergeau> http://www.w3.org/TR/2005/WD-css3-selectors-20051215/#attribute-substrings
francois: drop this
comment 12
felix: o.k.
comment 15
Richard: they seem to be afraid of matching problems
... they are saying how they define the matching is
done
... not rfc 3066bis or something else
Francois: it was poorly worded in the spec
... we should ask Addison or Mark or both what they think about
this
<scribe> ACTION: Felix to ask Addison and Mark about language tags in css selectors [recorded in http://www.w3.org/2006/01/31-i18ncore-minutes.html#action02]
<fyergeau> comment 16
<fyergeau> we need to insist
<fyergeau> on case-insensitve
comment 17
accepted
comment 20
francois: need to wait for answer or asked again
comment 23
francois: we should keep that open, until they clarify the relation between css and selectors (see comment
3)
... what they do for 3 will make it clear
http://lists.w3.org/Archives/Public/public-i18n-core/2006JanMar/0133.html
comment cdr-2
francois: drop this
comment cdr-5
francois: I still disagree
... I have a scenario with an XHTML document which contains an SVG image
...
if I make it external, the language information does not apply anymore
... my concern is: what should happen if there is no other
information?
... that is, no "authoritative metadata"
<scribe> ACTION: Felix to give back i18n core WG feedback to CSS and CDF WG [recorded in http://www.w3.org/2006/01/31-i18ncore-minutes.html#action03]
<scribe> ACTION: felix to summarize RFC 3066bis and to contact AP and Mark (ONGOING) [recorded in http://www.w3.org/2006/01/31-i18ncore-minutes.html#action04]
<scribe> ACTION: felix to ask addison for preparations for meetings with ws folks at tech plenary (ONGOING) [recorded in http://www.w3.org/2006/01/31-i18ncore-minutes.html#action05]
<scribe> ACTION: Felix to contact Moataz about HP replacement and TP (ONGOING) [recorded in http://www.w3.org/2006/01/31-i18ncore-minutes.html#action06]