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

[Bug 15406] New: [XQ3.0] Output declarations and parameter documents

From: <bugzilla@jessica.w3.org>
Date: Tue, 03 Jan 2012 18:01:28 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-15406-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15406

           Summary: [XQ3.0] Output declarations and parameter documents
           Product: XPath / XQuery / XSLT
           Version: Member-only Editors Drafts
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3.0
        AssignedTo: jonathan.robie@gmail.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


Consider

declare output:parameter-document "params.xml";

Is it intended that the parameter document is resolved relative to the static
(compile-time) base URI, or the dynamic (deployment time) base URI? We don't
say.

There are different use cases here. If the idea is to allow the serialization
parameters to be specified at run time, then the dynamic base URI should be
used. This appears to be the intended scenario, otherwise why would a parameter
in the file override one in the query?

However, if the intended use case is to define a standard set of serialization
parameters for all queries, which can be overridden perhaps temporarily by a
query developer during debugging, then the requirements are different. In
particular one would then expect the parameter value in the query to override
the one in the parameter file.

Also (editorial point), the text "The value of any other output declaration
overrides any value that might have been specified for the same serialization
parameter..." might be read as implying that the order of declarations is
significant, which I don't think is the intent.

-- 
Configure bugmail: https://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 Tuesday, 3 January 2012 18:01:29 UTC

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