AW: AW: Schema definition for <Transform>

Why?

Thanks, Gregor

> -----Ursprüngliche Nachricht-----
> Von: w3c-ietf-xmldsig-request@w3.org
> [mailto:w3c-ietf-xmldsig-request@w3.org]Im Auftrag von John Boyer
> Gesendet: Dienstag, 10. April 2001 18:26
> An: merlin; Gregor Karlinger
> Cc: Joseph M. Reagle Jr.; Ed Simon; w3c-ietf-xmldsig@w3.org
> Betreff: RE: AW: Schema definition for <Transform>
>
>
> Hi Merlin, Gregor and Joseph,
>
> Please note that the Transform is also the most likely place to define
> the xmlns:xsl namespace attribute.
>
> Thanks,
> John Boyer
> Senior Product Architect, Software Development
> Internet Commerce System (ICS) Team
> PureEdge Solutions Inc.
> Trusted Digital Relationships
> v: 250-708-8047  f: 250-708-8010
> 1-888-517-2675   http://www.PureEdge.com <http://www.pureedge.com/>
>
>
>
> -----Original Message-----
> From: merlin [mailto:merlin@baltimore.ie]
> Sent: Tuesday, April 10, 2001 2:26 AM
> To: Gregor Karlinger
> Cc: Joseph M. Reagle Jr.; Ed Simon; w3c-ietf-xmldsig@w3.org
> Subject: Re: AW: Schema definition for <Transform>
>
>
>
> I'm with Gregor. I think that the text should be something along
> the lines of:
>
> The normative specification for XSL Transformations is [XSLT].
> The XSL transformation is encoded within a namespace-qualified
> <code>stylesheet</code> element which MUST be the sole transform
> parameter child element.
>
> I.e:
>
> <Transform xmlns="&dsig;" Algorithm="&xslt;">
>   <xsl:stylesheet xmlns:xsl="&xslt;" ...>
>     ...
>   </xsl:stylesheet>
> </Transform>
>
> Next paragraph, typo "covert" -> "convert".
>
> Next paragraph, typo "to perform canonicalize" -> "to c10e".
>
> Merlin
>
> r/gregor.karlinger@iaik.at/2001.04.10/10:35:58
> >Joseph,
> >
> >> Ok, the actual element type in the dsig namespace has now been
> >> removed from
> >> the spec, dtd, and xsd, though the text still reads:
> >>
> >>
> http://www.w3.org/Signature/Drafts/xmldsig-core/Overview.html#sec-XSLT
> >> The normative specification for XSL Transformations is [XSLT].
> >> The XSL style
> >> sheet or transform to be evaluated appears as the character content
> of a
> >> transform parameter child element named XSLT.
> >
> >What does "character content" mean? Should the XSL stylesheet markup be
> >encoded in some fashion in order that it can be inserted as text?
> Otherwise
> >appearance as character content of a "XSLT" Element is invalid.
> >
> >What is the namespace for the "XSLT" element?
> >
> >> The root element of a XSLT
> >> style sheet within a Transform element should SHOULD be a namespace
> >> qualified <stylesheet> element.
> >
> >Liebe Gruesse/Regards,
> >---------------------------------------------------------------
> >DI Gregor Karlinger
> >mailto:gregor.karlinger@iaik.at
> >http://www.iaik.at
> >Phone +43 316 873 5541
> >Institute for Applied Information Processing and Communications
> >Austria
> >---------------------------------------------------------------
> >
> >
> >
>
>
> ------------------------------------------------------------------------
> -----
> Baltimore Technologies plc will not be liable for direct,  special,
> indirect
> or consequential  damages  arising  from  alteration of  the contents of
> this
> message by a third party or as a result of any virus being passed on.
>
> In addition, certain Marketing collateral may be added from time to time
> to
> promote Baltimore Technologies products, services, Global e-Security or
> appearance at trade shows and conferences.
>
> This footnote confirms that this email message has been swept by
> Baltimore MIMEsweeper for Content Security threats, including
> computer viruses.
>    http://www.baltimore.com
>
>
>
>

Received on Tuesday, 10 April 2001 13:30:13 UTC