[Bug 19671] [XQ3.0] Backwards compatibility and the version declaration


Josh Spiegel <josh.spiegel@oracle.com> changed:

           What    |Removed                     |Added
                 CC|                            |josh.spiegel@oracle.com

--- Comment #3 from Josh Spiegel <josh.spiegel@oracle.com> ---
A slight downside I see is that if the policy is changed to "accept", it
becomes a little awkward if the 3.0 processor encounters a 1.0 labeled module
using updates.  Strictly speaking, I would expect it to raise an error as if
updates do not exist until XQuery Update 3.0 goes REC. In the current spec, the
bit that reads "... or attempt to process the module with an XQuery 1.0
processor. " handles this case cleanly.  

Switching to "accept" seems more tolerable if there very little chance that
XQuery Update 3.0 will introduce a backwards incompatibility.  On this same
note, can we be sure that XQuery 4.0 won't introduce a backwards
incompatibility with 3.0?

You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 29 October 2012 22:06:40 UTC