- From: <bugzilla@jessica.w3.org>
- Date: Tue, 02 Dec 2014 17:53:42 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27330 C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> --- The QT WGs discussed this issue on their joint call today, and agreed that the state of affairs described in the first paragraph appears to be a problem we should fix; the editors were so instructed. The answer to the question ending the second paragraph is (as far as we can tell) "yes". The analysis is essentially that any attempt to serialize QNames to JSON is almost certainly either (a) headed for disappointment at some stage, which we cannot prevent, or (b) doing something very clever, which we cannot predict. Other analyses of the situation are possible, but there was not consensus today for changing the spec in this point. Accordingly, I'm marking this bug as resolved. Josh, please review the resolution and indicate your assent or dissent by closing or reopening the bug as appropriate. If we don't hear from you in the next two weeks, the WGs will assume you assent. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 2 December 2014 17:53:43 UTC