W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2015

[Bug 28174] [F+O 3.1] schema for json-to-xml() namespace: automatically imported?

From: <bugzilla@jessica.w3.org>
Date: Tue, 21 Apr 2015 19:58:36 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28174-523-wwhMIiOIJf@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28174

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
I was asked to make a proposal to resolve this.

The essence of my proposal is:

1. The schema components for the XML results of fn:analyze-string and
fn:json-to-xml should NOT be automatically added to the static context; they
should be added to the context only if explicitly imported (using import schema
in the case of XQuery).

2. In XQuery and XSLT, the processor must accept an import-schema declaration
for the relevant namespaces. If such a declaration includes a schema location,
the schema location must be ignored (no error occurs if no schema is present at
the location, or if the wrong schema is present at the location, etc), and the
schema as defined in our specifications is added to the static context.

3. In XPath, mechanisms for adding schema components to the static context are
implementation-defined.

4. The XDM trees returned by fn:analyze-string and fn:json-to-xml should be
typed (have non-trivial type annotations on element and attribute nodes) if and
only if the processor is able to handle typed data (in XQuery this means if the
processor implements the typed data feature), unless the user has requested
otherwise (in an implementation-defined way).

I think point 4 probably belongs in F+O, the other points belong in the host
language specs.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 21 April 2015 19:58:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 21 April 2015 19:58:39 UTC