W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2005

[Bug 1860] [XSLT] Uses cases for document() functions

From: <bugzilla@wiggum.w3.org>
Date: Fri, 19 Aug 2005 07:36:52 +0000
To: public-qt-comments@w3.org
Message-Id: <E1E61Qq-00064m-Fa@wiggum.w3.org>


mike@saxonica.com changed:

           What    |Removed                     |Added
            Summary|Uses cases for document()   |[XSLT] Uses cases for
                   |functions                   |document() functions

------- Additional Comments From mike@saxonica.com  2005-08-19 07:36 -------
I'm surprised by your comment, since there is very little that is new in the
document() function compared with XSLT 1.0. The specification has been
generalized a little: 

(a) in XSLT 1.0 the argument had to be either a node-set or a string, we now
allow other arguments such as a sequence of xs:anyURI values. That's really just
to integrate the new type system cleanly rather than to provide any new

(b) we have changed the way we describe the process of URI dereferencing to make
it clear that what you get back is context-dependent (this reflects the reality
of APIs that allow you to do your own URI derefencing with a user-written

Our general approach in the specification has been to reduce the amount of
"justification" (that is, explaining why the features are provided, as distinct
from explaining how they work), particularly in relation to features that were
present in XSLT 1.0 and are now widely covered in books and tutorials. Examples
to make the specification clear are in scope; use cases to give users ideas on
how to exploit the features are not.

If this response is acceptable, I'd be grateful if you could close the bug as it
will save scarce Working Group time.

Michael Kay
personal response
Received on Friday, 19 August 2005 07:36:54 UTC

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