Re: towards consensus on fixup, part 2

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

Alex Milowski writes:

> So what is the advisory going to say:

Something such as "The output of this step may require (one or more
of) [namespace fixup, xml:base fixup, xml:lang fixup] before
serialization, see section 2.6."

> That list would have to  include:
>
>    p:add-attribute
>    p:insert
>    p:replace
>    p:rename
>    p:wrap
>    p:unwrap
>    p:set-attributes
>    p:xslt
>    p:pack

     p:viewport    

> which is a third of our required steps.  To me, that's an admission that
> we have a problem that we don't want to solve.

The fact that we haven't spelled out the fixes in detail is not, in my
view, a bug.  Rather, it's an acknowledgement that we don't want to
adjudicate between all the methods that e.g. XSLT1.0 processors and
XInclude processors have developed for doing fixup.

ht
- -- 
 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)

iD8DBQFG4WunkjnJixAXWBoRAvuZAKCDDM0YPAGcbTCn1J10XJxIH4hqNQCfV2hi
+uz+IPxIihV8rggKev751Z8=
=4dc4
-----END PGP SIGNATURE-----

Received on Friday, 7 September 2007 15:18:09 UTC