In the following test-cases:
    K2-DirectConElem-47
    K2-DirectConElemNamespace-59
    K2-DirectConElemNamespace-65
    K2-DirectConElemNamespace-75
    K2-DirectConElemNamespace-76
    DirectConElemNamespace-3
    DirectConElemNamespace-4
the expected results include the error XQST0022, which I believe
should be removed. (And likewise in QT3_TS.)

XQST0022 should only be raised when the DirAttributeValue of
a namespace declaration attribute contains an EnclosedExpr,
and that is not the case for any of these queries.

-----------------------------------

History:

On 2010-10-12, Sorin Nasoi added
    Bug 6868 comment #28 
and
    Bug 7975 comment #5

Both comments say:

    I have added XQST0022 as an alternate result for tests:

    K2-DirectConElem-47
    K2-DirectConElemNamespace-59
    K2-DirectConElemNamespace-65
    K2-DirectConElemNamespace-75
    K2-DirectConElemNamespace-76

    because, as it was also mentioned by a comment for these
    tests, some processors MAY report the URI's as invalid.

(Note that both bugs had been resolved months previously, so the new
comments don't reflect a decision of the WG. As far as I can tell,
these comments haven't been discussed (or even acknowledged) by the WG.)

(In addition to the 5 test-cases mentioned, Sorin also added XQST0022
to DirectConElemNamespace-{3,4}.)

-----------------------------------

If a processor finds that these tests involve invalid URIs, XQST0022
is not the error to raise, rather XQST0046 is. (And indeed, all of these
test-cases include XQST0046 as a possible result, and already did so
at the time that Sorin added XQST0022.)

It's possible that Sorin was proceeding based on an old definition of
XQST0022:
    It is a static error if the value of a namespace declaration attribute
    is not a URILiteral.
but that definition had been rendered obsolete by the resolution of Bug 5083
three years previous. (See also Bug 11986 re a vestige of the old definition.)