This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 2865 - RQ-4 Address localization issues with datatypes (localization)
Summary: RQ-4 Address localization issues with datatypes (localization)
Status: RESOLVED WONTFIX
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.1 only
Hardware: Other All
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: needsAgreement
Depends on:
Blocks:
 
Reported: 2006-02-11 02:02 UTC by C. M. Sperberg-McQueen
Modified: 2006-09-21 00:00 UTC (History)
0 users

See Also:


Attachments

Description C. M. Sperberg-McQueen 2006-02-11 02:02:53 UTC
This issue was originally reported by I18n WG.

Address localization concerns regarding Part 2: Datatypes.

See (member-only link)
http://www.w3.org/XML/Group/xmlschema-current/lcissues.html#i18n-dt-misdirected:
LC-207.

Input from Straw Poll O-6

NOTE 2002-08-02: this needs to be analysed into its constituent items,
and each item acted on individually.

This item was postponed in the meeting of 2004-04-22
(http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Apr/0207.html).

According to the requirements document, this topic was discussed in the past
and was postponed for later reconsideration.
Comment 1 C. M. Sperberg-McQueen 2006-09-21 00:00:32 UTC
At the face to face meeting of January 2006 in St. Petersburg,
the Working Group decided not to take further action on this
issue in XML Schema 1.1.  (This issue was not discussed
separately; it was one of those which were dispatched by a
blanket decision that all other open issues would be closed
without action, unless raised again in last-call comments.)  Some
members of the Working Group expressed regret over not being able
to resolve all the issues dealt with in this way, but on the
whole the Working Group felt it better not to delay Datatypes 1.1
in order to resolve all of them.

This issue should have been marked as RESOLVED /WONTFIX at that
time, but apparently was not.  I am marking it that way now, to
reduce confusion.