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

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

From: <bugzilla@jessica.w3.org>
Date: Wed, 30 Nov 2011 01:07:55 +0000
To: public-qt-comments@w3.org
Message-Id: <E1RVYeR-00085P-46@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14932

--- Comment #5 from Erik Wilde <erik.wilde@emc.com> 2011-11-30 01:07:54 UTC ---
i've used unparsed-text() to crawl for robots.txt files and for CSS, and if you
have extension functions for tidying HTML, you can do pretty amazing things
with just writing XQuery.

i think it would be good to have a clear separation of concerns and talk about
identification, interactions, and representation in well-separated steps. to a
certain extent this exists with resolve-uri(), but there is also some mixing of
concerns such as with doc(). in an ideal world, there should be resolve-uri(),
then interaction (maybe specifically supported for HTTP), and then handling the
result, so that users could resolve() a relative URI, GET() an XML resource,
and then parse() it into an XDM. i think not separating these issues cleanly
has created the situation reported in this bug, and the cleanest solution would
be to separate the steps, expose them as functions, and then just define doc()
as a combination of the basic function. maybe that's too ambitious, but
personally, i'd like to see XQuery's web-friendliness increased anyway.

-- 
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 Wednesday, 30 November 2011 01:07:57 UTC

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