Re: subpipelines, Vnext and extension elements redux

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

As promised, I've tried to draft a proposed change to 2.1 and 4.7 wrt
all this.  I've actually produced this as a way-cut-down alternate
draft [1], as the formatting is sufficiently complex/important to need
to be seen in full to be comprehensible.  Please try to have a look
before tomorrow's call.

After all the discussion about non-standard compound steps, all I've
done to implement my preferred option (4) is _remove_ any way they
could sneak in.  If we feel more is necessary, a Note along the lines
of "It follows from the above that there is no provision for
backwards-compatible introduction of new compound step types." could
be added.

ht

[1] http://www.w3.org/XML/XProc/docs/alternate/
- -- 
 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)

iD8DBQFH4Uz2kjnJixAXWBoRApeuAJ9GpnmO3N93YJbewRFJ1nsHKYEe+QCcCzvW
YlMevsuOqRPbASU/h/FAjjE=
=wGAQ
-----END PGP SIGNATURE-----

Received on Wednesday, 19 March 2008 17:27:55 UTC