This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Hello, this is a comment on behalf of the i18n core Working Group. We suggest that you make clearer that what you call timezone information is actually zone offset information. You should add a note including a reference to http://www.w3.org/TR/2005/NOTE-timezone-20051013/, which makes the difference clear. Location in the document: D.2.1 http://www.w3.org/TR/2008/WD-xmlschema11-2-20080620/#vp-dt-year Personal note: This comment is only about making the distinction between time zone and zone offset clearer, and does not mean to say that one is better than the other. I have looked at the thread at http://lists.w3.org/Archives/Public/www-i18n-comments/2008Aug/thread#msg1 and I think that the comment will take that thread into account and eventually ask for a reference to the *updated* version of the Working Group Note. Thank you, Felix
A similar issue was raised by Frans Englich in bug 4642. The editors believe that any wording proposal which resolves bug 4642 is likely also to resolve this one.
A wording proposal intended to resolve this issue, and also issue 4642, has been prepared by the editors and was adopted by the Working Group on 5 September. http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.b4642.html As noted in the proposal (under "Status of this document"), most occurrences of "time zone" are changed to "time zone offset", a reference to the i18n WG Note is added, and a couple of erroneous notes about the indeterminacy of time zone recovery in 1.0 and 1.1 have been dropped. Felix, if you could report this disposition to the i18n WG and indicate whether the i18n WG is content (by closing the issue) or not content (by reopening it) with the resolution of the issue, we would be grateful. If we don't hear otherwise in the next two weeks, we will assume (not unmindful of our self-interest) that the i18n WG is content with the resolution.
Thank you, Michael, I agree with your resolution and have reported this resolution to the i18n Core Working Group. Felix