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 18:35:18 +0000
To: public-qt-comments@w3.org
Message-Id: <E1RVSWU-0006Vb-JY@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14932

Erik Wilde <erik.wilde@emc.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |erik.wilde@emc.com

--- Comment #3 from Erik Wilde <erik.wilde@emc.com> 2011-11-29 18:35:17 UTC ---
not sure whether that's a comment or should be filed as a new bug:
fn:unparsed-text() is not really clear about whether a text resource should be
requested (by using HTTP Accept, for example), or whether a requested resource
should be passed into XQuery as a string. the difference might matter, because
essentially, there are three things that users might want to do:

- GET XML, and then process as XDM. this is covered by doc().
- GET XML, and then process it as text (i.e., get serialized XDM).
- GET text/plain, i.e. a plain text variant of a resource, which could be very
different, such as the server stripping out markup and delivering formatted
text/plain.

i think all of this could be addressed in a more explicit way how XQuery
interfaces with HTTP and generally fits into the web, and that's one of the
things i am really interested in, but that's definitely only appropriate for
3.1.

-- 
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 18:35:26 UTC

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