Re: I think p:import-schema is too big and too late for V1

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

Norman Walsh writes:

I'll reserve my position on the overall question, but one of your
points can be answered simply, I think:

> 3. It's even worse than that. We've agreed that the static context
> constructed by the pipeline processor is the static context made
> available to steps. We have to do this for some steps (so that they
> can evaluate expressions containing named types) so we do it for all
> steps.
>
> This means that an XSLT or XQuery step that does its own schema
> importing might fall over if I've imported a pipeline library that
> imports a schema, even if I'm not using that schema or any steps that
> use that schema in my pipeline.

The "static context made available to steps" is only made available
for them to use when evaluating XPath expressions passed to them as
options.  Neither the XSLT nor the XQuery step take any options whose
value is an XPath.  So no issue.

ht
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
                         Half-time member of W3C Team
      10 Crichton Street, Edinburgh EH8 9AB, 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)

iD8DBQFIieFTkjnJixAXWBoRAnL+AJ44wvyOHsr1qIVe7EVhkNShErGSzQCfWOXZ
RaspG3qTVD79tmr9/6MdJi4=
=PkTD
-----END PGP SIGNATURE-----

Received on Friday, 25 July 2008 14:21:49 UTC