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

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

From: <bugzilla@jessica.w3.org>
Date: Mon, 18 May 2015 16:28:13 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28174-523-1ry5SnFWMb@http.www.w3.org/Bugs/Public/>

--- Comment #3 from Jonathan Robie <jonathan.robie@gmail.com> ---
(In reply to Michael Kay from comment #1)
> I was asked to make a proposal to resolve this.

I'm implementing this right now.  Comments below.

> 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).

I don't think this requires anything to be said explicitly in XQuery 3.1 /
XPath 3.1.  Both specs explicitly state what schema types are predefined.


When adding this, though, I realized I wasn't sure who "they" is in the above
statement.  In-scope schema types are "augmentable" according to Appendix C. I
assume that should not change?

> 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.

I am adding this to the section on import-schema.

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

I believe this is equally true for all components of C.1 Static Context

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 18 May 2015 16:28:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 18 May 2015 16:28:16 UTC