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

[Bug 19602] [XQ30] Features not scoped to a module

From: <bugzilla@jessica.w3.org>
Date: Tue, 30 Oct 2012 16:32:38 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-19602-523-qRrTuTkSKM@http.www.w3.org/Bugs/Public/>

--- Comment #1 from Jonathan Robie <jonathan.robie@gmail.com> ---
We agreed to resolve this as follows.

General principle:

(1) do not change anything to the optional feature section (2)
require-feature raises an error if the product does not support it
(unchanged) (3) prohibit-feature raises an error if it can be detected
statically that the feature is actually used by the module (validate,
module import, dynamic function call, ...). (4) you cannot prohibit
static typing or serialization.

Schema Aware Feature:

allows/prohibits schema import and validate, nothing more or less. Different
modules may enable/disable this feature in a given query

Static Typing Feature:

Fine as written.

Module Feature:

Only allowed in a main module.

Serialization Feature:

Require/prohibit is not supported, there is no name for this feature. But it is
an optional feature, and support for it is implementation-defined.

Higher Order Functions:

No change

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 30 October 2012 16:32:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:40 UTC