Altova Mailing List Archives

RE: [xsl] Content negotiation in XSLT

From: "Houghton,Andrew" <houghtoa@-------->
Date: 7/21/2008 6:54:00 PM
> From: Florent Georges [mailto:lists@xxxxxxxxxxxx]
> Sent: Monday, July 21, 2008 1:49 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [xsl] Content negotiation in XSLT
> "Rushforth, Peter" wrote:
> > I'm curious as to why saxon:serialize and saxon:parse are required
> > for the <body> element?
> > Should the extension function not be able to avoid their use by
> > serializing/parsing the request/response internally without the
> > need for the other extensions?
>   This extension is aimed to provide HTTP features.  And HTTP is not
> restricted to XML, it sends and receives text.

I'm assuming that saxon:parse is just one aspect of the <body> element since
the example assumes that the element contains XML.  It would be possible for
the <body> element to contain a Jpeg image in the form of base 64 encoding and
one would use saxon:base64Binary-to-octets to manipulate or output the actual

However, what about multi-part content?  It doesn't seem like the extension
function currently handles this possibility.  Looking at the examples I think
that a small change in the request/response XML could handle multi-part
content.  Just wrap the <header> and <body> in a <part> element which takes an
attribute for the part's identifier.



These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.