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

[Bug 19670] New: [XQ3.0] What does it mean to prohibit "all extensions"?

From: <bugzilla@jessica.w3.org>
Date: Tue, 23 Oct 2012 16:33:53 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-19670-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19670

          Priority: P2
            Bug ID: 19670
          Assignee: jonathan.robie@gmail.com
           Summary: [XQ3.0] What does it mean to prohibit "all
                    extensions"?
        QA Contact: public-qt-comments@w3.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: mike@saxonica.com
          Hardware: PC
            Status: NEW
           Version: Last Call drafts
         Component: XQuery 3.0
           Product: XPath / XQuery / XSLT

XQuery 3.0 provides an option declaration whose effect is to disable all
(vendor) extensions.

But the spec doesn't say what counts as a (vendor) extension.

Extending the grammar clearly is an extension, I assume.

What about pragmas in a vendor namespace - are these extensions? (The spec
calls these "extension expressions" so I guess so).

What about option declarations in a vendor namespace?

What about implicit addition of functions, collations, types etc to the static
and dynamic context? Are these extensions? Are they extensions only if added to
the context "by default", or also if added by explicit user request, e.g. using
an API?

The rules need to be made much more clear.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 23 October 2012 16:33:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 23 October 2012 16:33:59 GMT