- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 17 Feb 2010 22:30:44 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7860
Jonathan Robie <jonathan.robie@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #2 from Jonathan Robie <jonathan.robie@redhat.com> 2010-02-17 22:30:44 ---
(In reply to comment #1)
> A proposal to address this problem (along with bug 7749) is at
>
> http://lists.w3.org/Archives/Member/w3c-xsl-query/2009Oct/0133.html
>
> (member-only)
>
The WG has adopted this proposal
(http://lists.w3.org/Archives/Member/w3c-xsl-query/2010Jan/0081.html):
I think the changes to our specification needed to plug this usability gap
are very modest. Define the construct AType to be an atomic type or a union
type that does not impose any restrictions beyond those imposed by its
member types (for a way of saying this more formally, see Type Derivation OK
(Simple) in XSD 1.1). Then we allow an AType to be used as an ItemType in
the SequenceType production (in place of the current AtomicType), and in
2.5.4.2 we say that when the AType is a union type, then it matches an
atomic value if and only if one of its member types matches that atomic
value.
I will add this to the internal working draft.
--
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, 17 February 2010 22:30:46 UTC