[Bug 19683] New: [XQ30] Section 4.20 require-feature and prohibit-feature not updated?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19683

          Priority: P2
            Bug ID: 19683
          Assignee: jonathan.robie@gmail.com
           Summary: [XQ30] Section 4.20 require-feature and
                    prohibit-feature not updated?
        QA Contact: public-qt-comments@w3.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: jim.melton@acm.org
          Hardware: All
            Status: NEW
           Version: Working drafts
         Component: XQuery 3.0
           Product: XPath / XQuery / XSLT

In section 4.20 require-feature and prohibit-feature (of the XQuery 3.0 draft
found at
https://www.w3.org/XML/Group/qtspecs/specifications/xquery-30/html/xquery-30.html
, I read the following:

<text>
In XQuery 3.0, the following feature names may be used in require-feature or
prohibit-feature option declarations; they are all defined in the
http://www.w3.org/2012/xquery namespace.

    The name schema-import corresponds to the feature defined in 5.2.1 Schema
Import Feature.

    The name schema-validation corresponds to the feature defined in 5.2.2
Schema Validation Feature.

    The name static-typing corresponds to the feature defined in 5.2.4 Static
Typing Feature.

    The name module corresponds to the feature defined in 5.2.5 Module Feature.

    The name serialization corresponds to the feature defined in 5.2.6
Serialization Feature.
</text>

However, there is no feature named "Schema Import Feature", nor is there a
feature named "Schema Validation Feature". They have been replaced by a feature
named "Schema Aware Feature".  This can be seen in section 5.2 Optional
Features. 

In addition, section 5.2 Optional Features defines yet another optional
feature: 5.2.7 Higher-Order Function Feature.  That new feature is not
reflected in section 4.20 require-feature and prohibit-feature.  Consequently,
no identifier for that new feature has been defined. 

I strongly suggest that section 4.20 require-feature and prohibit-feature be
updated before the F2F next week to reflect the current list of optional
features.  (Notice that section 5.2 redundantly defines the feature identifiers
that are -- or should be, at least -- also defined in section 4.20. It seems
unfortunate to define them twice, as it can only lead to inconsistencies.)

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