W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2011

[Bug 14932] New: [FO30] fn:unparsed-text

From: <bugzilla@jessica.w3.org>
Date: Fri, 25 Nov 2011 09:56:03 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-14932-523@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14932

           Summary: [FO30] fn:unparsed-text
           Product: XPath / XQuery / XSLT
           Version: Member-only Editors Drafts
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators 3.0
        AssignedTo: mike@saxonica.com
        ReportedBy: tim@cbcl.co.uk
         QAContact: public-qt-comments@w3.org


In Bug 14831, it has been pointed out that fn:unparsed-text and fn:doc use
different mechanisms for resolvling URIs to resources.

"doc() uses a mapping of URIs to resources in the static context,
whereas unparsed-text() lacks this indirection: the spec is written to require
direct resolution of the URI supplied."

This means that 

fn:doc('http://www.example.com/')

and

fn:unparsed-text('http://www.example.com/')

may bear no relation to each other.  This seems to be unfortunate.

-- 
Configure bugmail: http://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 Friday, 25 November 2011 09:56:07 UTC

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