conformance to onRequest. . .

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My feeling is that the use of RFC2119 'should' here is intended to
cover cases where there _is_ no user, or there is no way for a user to
'request' traversal.  In other words, a conformant implementation
which _can_ allow a user to make such a request, _must_ implement
'onRequest' as specified.  Treating 'onRequest' as 'onLoad' is not an
obviously helpful fallback in the absence of a user, but you may have
a good reason for doing so.

ht
- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)

iD8DBQFEx4rlkjnJixAXWBoRArlhAJ0fwszENtLC/4+fpoQXTRzlLibDNgCfXcDl
X5Pmmym2zxws2dqLsZcBUJE=
=2LK8
-----END PGP SIGNATURE-----

Received on Wednesday, 26 July 2006 15:31:57 UTC