[Bug 7366] Support JCnQName type

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


Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mike@saxonica.com




--- Comment #1 from Michael Kay <mike@saxonica.com>  2009-08-19 09:38:49 ---
If there ever is a 1.2, I would support this. Though I don't think it needs to
be a separate data type; rather it's a new lexical representation for an
existing type. (It's a big shame that the spec doesn't really recognize this
concept: hexBinary and base64Binary should have been the same data type, with
facets to select the lexical representation).

I've been experimenting in Saxon using the ability to have vendor-defined
facets, including "pre-lexical" facets that allow you, for example, to have
booleans written as yes|no, or numbers written in Continental European
notation, or dates written in North American format. This could be another
application of this idea - except that it's not clear what to do with all the
baggage that QNames carry about requiring the namespace prefix to be in scope.


-- 
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 Wednesday, 19 August 2009 09:39:04 UTC