W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > July to September 2000

RE: XSL Transform

From: Joseph M. Reagle Jr. <reagle@w3.org>
Date: Wed, 26 Jul 2000 13:23:49 -0400
Message-Id: <3.0.5.32.20000726132349.0142b258@localhost>
To: Ed Simon <ed.simon@entrust.com>
Cc: "'w3c-ietf-xmldsig@w3.org'" <w3c-ietf-xmldsig@w3.org>, "'ht@cogsci.ed.ac.uk'" <ht@cogsci.ed.ac.uk>
At 12:28 7/26/2000 -0400, Ed Simon wrote:
 >Ed responds:
 >If we can enforce, to a reasonable degree, that XSLT <Transform>s indeed
 >have
 >a <stylesheet> root element, then I think the derived benefits of 
 >interoperability more than outweigh the cost of two or three more lines in
 >the schema. 

I'm not sure how to. I was thinking we could define our own XSLT root and
pretend its of the XSLT namespace, or even create our own schema stub with
the root node defined and everything else open (so we don't have to recreate
a whole schema). But, I'd be happier with some prose in that section stating
a recommendation over the content. So if you want to propose some prose or
clever schema tricks, please do so. <smile>

 > (It would certainly be nice is XSLT did provide a schema and
 >I hope they do in their next Recommendation version.)
 
The XSLT spec is littered with comments saying they plan to next time around.

_________________________________________________________
Joseph Reagle Jr.   
W3C Policy Analyst                mailto:reagle@w3.org
IETF/W3C XML-Signature Co-Chair   http://www.w3.org/People/Reagle/
Received on Wednesday, 26 July 2000 13:24:12 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.29 : Thursday, 13 January 2005 12:10:10 GMT