W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2016

[Bug 29938] New: [XSLT30] Suggestion to drop XTDE1370 and XTDE1380 to bring them in line with XDM 3.0

From: <bugzilla@jessica.w3.org>
Date: Sun, 16 Oct 2016 06:21:38 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29938-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29938

            Bug ID: 29938
           Summary: [XSLT30] Suggestion to drop XTDE1370 and XTDE1380 to
                    bring them in line with XDM 3.0
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

This bug applies to our description of fn:unparsed-entity-uri and
fn:unparsed-entity-public-id.

We currently say this for these errors (descr. is the same for both):

[ERR XTDE1370] It is a dynamic error if $node, or the context item if the
second argument is omitted, is a node in a tree whose root is not a document
node.


We explain these functions in terms of the dm:unparsed-entity-uri and the
dm:unparsed-entity-public-id accessors. According to the DM, these accessors
return an empty sequence if applied to something other than a document node.

Since our functions find the root of the current tree, this root can be a
document node, or something else. In the latter case we ought to raise these
errors.

I propose to drop these errors. I don't see a use for them and I think it is
good to be more in line with the DM. Furthermore, less errors is usually better
:).

We may consider to return the empty sequence (change of signature) or the empty
string (with current signatures). I don't see a problem for either, but have a
preference for returning the empty sequence (in line with the DM).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 16 October 2016 06:21:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:02 UTC