W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2012

[Bug 15688] New: [XQ30] Effect of prohibiting the serialization option

From: <bugzilla@jessica.w3.org>
Date: Tue, 24 Jan 2012 10:42:52 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-15688-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15688

           Summary: [XQ30] Effect of prohibiting the serialization option
           Product: XPath / XQuery / XSLT
           Version: Member-only Editors Drafts
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3.0
        AssignedTo: jonathan.robie@gmail.com
        ReportedBy: tim@cbcl.co.uk
         QAContact: public-qt-comments@w3.org


It's pretty clear what effect prohibiting the following optional features will
have:

schema-import: Raise XQST0009 on schema import.
schema-validation: Raise XQST0075 on validate expressions.
static-typing: Don't raise XPTY0004, XPST0005 for some expressions.
module: Raise XQST0016 on module declaration or module import.

But it's not quite so clear what disabling the serialization feature will do.

Does it cause an implementation-defined error to be raised if the user attempts
to serialize the results of a query (via the implementation's API)?

Does it cause errors to be raised when output declarations are encountered?

Does it cause fn:serialize to raise an error?

-- 
Configure bugmail: https://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 Tuesday, 24 January 2012 10:42:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:47 UTC