Forwarded message 1
Char encoding is (most probably) inherited from the pipeline, and whitespace is probably handled the same way the XML parser handled the pipeline. Those should probably be stated in the spec explicitly though.
Why have DOE? Give at least one use case for it. It made sense in XSLT 1.0, but in XProc, it doesn't, and that has been one of the most misused features in XSLT 1.0. If it is to be included here, there's got to be a pretty damn good reason for it.
What will this "wrap element" option do? I can't figure it out... example?
-----Original Message-----
From: public-xml-processing-model-comments-request@w3.org [mailto:public-xml-processing-model-comments-request@w3.org] On Behalf Of James Fuller
Sent: Friday, October 12, 2007 9:53 AM
To: public-xml-processing-model-comments@w3.org
not particularly serious, but was wondering if we need to add anything
to p:inline element?
* char encoding attribute
* white space handling
* doe ?
* wrap element
Jim Fuller
--
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]