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

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

From: <bugzilla@jessica.w3.org>
Date: Mon, 13 Feb 2012 23:04:58 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Rx4x8-0004y4-O0@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14932

--- Comment #10 from Michael Kay <mike@saxonica.com> 2012-02-13 23:04:56 UTC ---
Jonathan's proposal (member-only):
https://lists.w3.org/Archives/Member/w3c-xsl-query/2012Feb/0021.html

>From today's minutes: DECIDED to accept Jonathan's proposal for resolving this
with some modifications. Change "available resources" to "available text
resources". Change the description of unparsed-text() to say it returns not
"the resource" but "a string representation of the resource". We should note
that there is no essential relationship between the sets of URIs accepted by
the two functions unparsed-text() and doc() (a URI accepted by one may or may
not be accepted by the other), and if a URI is accepted by both there is no
essential relationship between the results (different resource representations
are permitted by web architecture). We should also note that there are no
constraints on the MIME type of the resource. Also unparsed-text() needs a
similar section to the "Various aspects are implementation-defined" paragraph
that currently exists for the doc() function.

-- 
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 Monday, 13 February 2012 23:05:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:37 UTC