  PSVI issues  From: Henry S. Thompson <ht@inf.ed.ac.uk> Date:
Thu, 08 May 2008 14:11:47 +0100 Message-ID:
<f5br6cdym7g.fsf@hildegard.inf.ed.ac.uk>  Hash: SHA1  1) The
functionality provided by the 'psvi-required' attribute is
perfectly reasonable and self-contained, and it should be
retained    unchanged.  If I want to write pipelines which
simple won't work    (statically) when a processor doesn't
support the PSVI, that's what    I'll use.  2) I am unconvinced
that we need to provide a means to tell processors    which do
support the PSVI whether or not they need to do so when
executing a particular pipeline.  That feels like an    product-
specific optimisation to me, and as such _finally_ gives me
an example of a realistic use for <pipeinfo> -- a product is
free    do define a <pipeinfo> child which can be inserted
before    e.g. validate steps to say, in effect, "I do/don't
care about the     I'd rather wait until we see if such
annotations turn out to be    provided, and what they look like,
bef