W3C home > Mailing lists > Public > public-xml-processing-model-comments@w3.org > November 2008

RE: XSLT 2 and xsl:result-document

From: <Toman_Vojtech@emc.com>
Date: Thu, 27 Nov 2008 09:59:46 -0500
Message-ID: <6E216CCE0679B5489A61125D0EFEC7870D99B410@CORPUSMX10A.corp.emc.com>
To: <public-xml-processing-model-comments@w3.org>

> > My reading of the XSLT 2 spec. (and the way Saxon works) 
> suggest we have
> > something that at least needs work:  xsl:result-document with an
> > explicit "href" attribute is defined to (try to) write a document to
> > the specified location.  Do we care?
> 
> Those documents are required to appear on the secondary output port.
> They do not get written to disk unless your pipeline does so.
> 
> > Insofar as XSLT processors are
> > likely to expose some security controls to the user, should we at
> > least add an option which attempts to expose that control to the
> > pipeline author?  Or should we mandate locking this down 
> unilaterally?
> > At the very least we need to call attention to this, I think.
> 
> From 7.1.31:
> 
>   The primary result document of the transformation appears on the
>   result port. All other result documents appear on the secondary
>   port.
> 
> I think that locks it down.
> 

Just a question: How does exsl:document relate to this?

Vojtech
Received on Thursday, 27 November 2008 15:01:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:26 UTC