'Protection' from parameter 'polution'

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

_If_ we think we need to allow pipeline writers to 'protect' steps or
regions of their pipelines from pollution by miscellaneous inherited
parameters, we should provide a specific mechanism to do this,
e.g. with a 'block-parameter-inheritance' attribute on p:group.

I'm inclined _not_ to do this, on the grounds that the two step types
we know of which will use parameters at all will not have a problem:

 1) XSLT, XQuery and friends - spurious params have no impact, as they
    aren't looked at -- there's no way to iterate over all visible
    params;

 2) http-request - We can and probably should use a separate namespace
    for the params which http-request is spec'd to turn into headers,
    to avoid collision with XSLT params.

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.2.6 (GNU/Linux)

iD8DBQFGVbimkjnJixAXWBoRAhVjAJ44rH1VRRin9VdCiYQULU2aaIl07wCfUI+x
X0kHEY6MYqMcq6c6t4z3h1g=
=VI4v
-----END PGP SIGNATURE-----

Received on Thursday, 24 May 2007 16:09:24 UTC