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

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 29 Nov 2011 21:34:26 +0000
To: public-qt-comments@w3.org
Message-Id: <E1RVVJq-000656-7X@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14932

--- Comment #4 from Michael Kay <mike@saxonica.com> 2011-11-29 21:34:25 UTC ---
The use cases for unparsed-text in XSLT (where it has existed for some years)
are primarily for reading and parsing data files in non-XML formats, either for
conversion into XML or for searching. I have used it, for example to search
Java source code. I think nearly all the applications I have come across are
reading local files rather than doing HTTP access. But of course, that doesn't
stop other people inventing other uses, and there is no reason why the spec
should restrict the possibilities: mapping URIs to resources delivered as
strings of characters seems a pretty general and powerful capability. (In fact,
it makes you wonder why we need environment-variable()...)

Many of the applications involve collections of text resources, so we
definitely need some kind of relationship between uri-collection() and
unparsed-text().

-- 
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 Tuesday, 29 November 2011 21:34:32 UTC

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