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

[Bug 25919] unparsed-text-023 should not expect a static error

From: <bugzilla@jessica.w3.org>
Date: Fri, 30 May 2014 07:42:32 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-25919-523-YfiHZsxaQJ@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25919

Tim Mills <tim@cbcl.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tim@cbcl.co.uk
           Assignee|oneil@saxonica.com          |tim@cbcl.co.uk

--- Comment #1 from Tim Mills <tim@cbcl.co.uk> ---
The specification says

"This function is ·deterministic·, ·context-dependent·, and
·focus-independent·. It depends on static base uri."

So I'd argue that an implementation is at liberty to determine that it will
require the static base URI.  I think XPST0001 is acceptable, but agree that
[err:FOUT1170] is equally valid.

I take your point about unparsed-tex-available in the case where unparsed-text
would raises FOUT1170 and not XPST0001.

If I remember correctly, I based these tests on those for fn:doc, so I'll take
a look at those

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 30 May 2014 07:42:34 UTC

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