W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2009

[Bug 7737] New: Unclear rules for schema import

From: <bugzilla@wiggum.w3.org>
Date: Sun, 27 Sep 2009 20:36:15 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-7737-523@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7737

           Summary: Unclear rules for schema import
           Product: XPath / XQuery / XSLT
           Version: Recommendation
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery
        AssignedTo: jonathan.robie@redhat.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


This bug takes one aspect of bug #6513 which appears to be separable from the
rest of the discussion. This also relates to bug #5738.

Specifically:

(a) the text does not clearly distinguish between a schema and a schema
document. It talks of a "schema" having a target namespace and a location,
whereas those are actually properties of a schema document only.

(b) the text does not make it clear whether all the elements, attributes, and
types in the referenced schema are imported, or only those in the specified
target namespace.

(c) the text does not deal adequately with multiple imports of overlapping
schemas. For example, it makes it an error if multiple imported schemas contain
definitions for the same name in the same symbol space: but multiple imported
schemas will *always* overlap in that sense, if only because they always
contain the built-in types such as xs:integer; in practice it is also highly
likely that there will be other overlaps, such as the definitions in the xml
namespace.

Note that from previous WG discussion of the referenced bugs, there appears to
be a consensus in the WG that schema import should add to the static context of
the module all the elements, attributes, and types from the schema obtained by
expanding xs:include and xs:import declarations in the referenced schema
documents transitively. This will be taken as the starting point, even though
the existing text might appear to suggest that it only imports those elements,
attributes, and types whose target namespace is equal to the target namespace
explicitly specified in the "import schema" declaration.


-- 
Configure bugmail: http://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 Sunday, 27 September 2009 20:36:25 UTC

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