- From: merlin <merlin@baltimore.ie>
- Date: Wed, 02 Aug 2000 19:23:18 +0100
- To: "Joseph M. Reagle Jr." <reagle@w3.org>
- Cc: Ed Simon <ed.simon@entrust.com>, "'w3c-ietf-xmldsig@w3.org'" <w3c-ietf-xmldsig@w3.org>, "'ht@cogsci.ed.ac.uk'" <ht@cogsci.ed.ac.uk>
Hi, The preference was, I think, to eliminate the XSLT element: The Transform element /+ MUST contain a single <stylesheet> element (and its children/content) as defined by the XSL Transformations [XSLT] language and its namespace. +/ The processing rules for the XSLT transform are stated in the XSLT specification [XSLT]. Merlin r/reagle@w3.org/2000.08.02/11:45:31 >At 13:54 7/26/2000 -0400, Ed Simon wrote: > >I think we need input from someone like Henry T. who deeply > >understands schemas. > >While we await an answer from Henry, I came up with the following prose (if >schema doesn't do the complete trick) since I'm looking at that section >anyway. We could probably get rid of the XSLT element type in the dsig >namespace as its just a hint in the schema that style sheets can go there ... > >http://www.w3.org/TR/2000/WD-xmldsig-core-20000711/#sec-XSLT > >6.6.5 XSLT Transform >Identifier: >http://www.w3.org/TR/1999/REC-xslt-19991116 >The Transform element contains a single <XSLT> element /+ that MUST contain >a single <stylesheet> element (and its children/content) as defined by the >XSL Transforms [XSLT] language and its namespace.+/ The processing rules for >the XSLT transform are stated in the XSLT specification [XSLT]. > >_________________________________________________________ >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, 2 August 2000 14:24:00 UTC