> Sounds like casting the soap-c14n spec as a transform is the best bet, > I'll modify it accordingly. No, I disagree. If you make it a URI then it is easy for XSLT folks to recognize that URI and call the built-in transform. It is also easy for code-based folks to call their built-in subroutine. If you make it a transform, then both folks will have to do some serious work (e.g., canonicalize!) the transform to see if it's the special-case applies. The simplest thing for all implementors is URI with non-normative transform as an appendix. /r$Received on Friday, 10 January 2003 13:51:28 GMT
This archive was generated by hypermail 2.2.0 + w3c-0.29 : Thursday, 13 January 2005 12:10:16 GMT