- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 02 Apr 2009 20:01:57 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6733
Jim Melton <jim.melton@acm.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #1 from Jim Melton <jim.melton@acm.org> 2009-04-02 20:01:57 ---
The problem with a bug like this one is that it takes us down (however
slightly) the slippery slope of trying to make valid XQuery expressions out of
nearly arbitrary XQueryX syntax.
As one participant told me, "If users can write arbitrary xqueryx, and every
such xqueryx needs to translate into correct xquery, i bet i could hand you
dozens of other bugs...it means there are valid XQueryX documents (by the
schema) that the stylesheet will turn into not-correct XQuery, but that does
not mean it's broken."
Without prejudice, I'm RESOLVING this bug as WONTFIX, but am willing to hear
stronger arguments either that this case is sufficiently unique to justify
special treatment, or that this is one of a set of cases that are sufficiently
unique (and important) to justify special treatment.
If you accept this resolution, please mark the bug CLOSED.
--
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 Thursday, 2 April 2009 20:02:07 UTC