[Bug 6522] Please un-deprecate the the namespace http://www.w3.org/2001/XMLSchema-datatypes

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6522


David Ezell <David_E3@VERIFONE.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|editorial, needsReview      |decided




--- Comment #21 from David Ezell <David_E3@VERIFONE.com>  2009-04-17 15:51:21 ---
- 6522 (John Cowan): Please un-deprecate the the namespace
http://www.w3.org/2001/XMLSchema-datatype
The proposal is at:
http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.b6522.html

Summary: reverts most of the earlier change that deprecated the
namespace.  After this change, the relevant part of 3.1 will
read:

     To facilitate usage in specifications other than the XML
     Schema definition language, such as those that do not want to
     know anything about aspects of the XML Schema definition
     language other than the datatypes, each ·built-in· datatype
     is also defined in the namespace whose URI is:

         http://www.w3.org/2001/XMLSchema-datatypes

Note: The status quo says "each non-special built-in datatype
...:, We added 'non-special' when we deprecated the namespace,
probably on the theory that (1) anySimpleType is not in the
namespace as described in 1.0 and (2) if we were going to
deprecate it, it made no sense to 'maintain' it or bring it up to
date.  I propose to revert the change for simplicity: "all
built-ins" is simpler than "all non-special built-ins".  Reliable
authority says RelaxNG doesn't care and can live with specials in
the namespace or not in the namespace.

MSM's recommendation: Quick. Adopt proposal as shipped.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 17 April 2009 15:51:35 UTC