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

/ ht@inf.ed.ac.uk (Henry S. Thompson) was heard to say:
|> 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.

So you're proposing to change 2.6.3 so that it distinguishes between
steps that take options whose values are XPaths and those that don't?

I don't like that inconsistency, but it might work for XSLT and
XQuery. We'd still be signing on for the limitation I described for
any extension step or step we add in the future though.

I think that's another question that goes in the "we'd need to think
hard about this" bucket.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | I often marvel that while each man
http://nwalsh.com/            | loves himself more than anyone else, he
                              | sets less value on his own estimate
                              | than on the opinions of others.--Marcus
                              | Aurelius