Hi Vincent,

Is there a way to use the xsl:transform-report function to obtain messages and the serialized result (instead of document nodes) that is currently returned by xslt:transform-text?


Currentl no; we’ll think about it. A long-term solution could be to support fn:transform, but that’s currently out of scope.

Is there a way to provide a base URI in the options of xsl:transform-text (or xsl:transform-report or xsl:transform)? If the input to the transformation is on disk then the base URI is set automatically, however if the input is held in memory then the base URI is not set so it could be helpful to be able to provide a base uri to the transformer as an option.


We have revised the way how we assess the base URI of the input, and it should also be detected and propagated now for main-memory nodes. Feel free to check out the latest snapshot [1].

Hope this helps,
Christian


[1] https://files.basex.org/releases/latest/

 

 

The documentation doesn’t mention these capabilities so I’m guessing that these things are not currently possible.

 

Thank you,

Vincent

 

______________________________________________

Vincent M. Lizzi

Head of Information Standards | Taylor & Francis Group

E-Mail: vincent.lizzi@taylorandfrancis.com

Web: www.tandfonline.com

Time zone: US Eastern

 

Taylor & Francis is a trading name of Informa UK Limited,

registered in England under no. 1072954

 

"Everything should be made as simple as possible, but not simpler."

  

 


Information Classification: General