- From: <bugzilla@jessica.w3.org>
- Date: Tue, 05 Jan 2016 17:40:24 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29354
O'Neil Delpratt <oneil@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from O'Neil Delpratt <oneil@saxonica.com> ---
The WG decision that the test is valid:
The key rationale is to decouple our spec from Unicode: using an unassigned
character may be (perhaps is) a violation of the agreement between data source
and data sink, if they have agreed to use a particular version of Unicode.
But it is not (and should not be) a violation of our specs.
Unicode may assign the character next month or next year, and it should be
possible to use the character then, in a conforming implementation.
That means it must be possible *now* to use it in a conforming implementation.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 5 January 2016 17:40:29 UTC