Nabble - Saxon XSLT and XQuery Processor

Re: Xquery Module External Variables

2008-10-09T14:52:03Z

You have to supply values for all the external variables before starting
query execution, regardless what module they are declared in. If you want
something that varies from one invocation to another, you must declare it as
a local parameter of a particular function within the module.

Modules are not especially well specified so you may well find variations
between implementations, but I wouldn't expect any product to allow external
variables to be modified dynamically.

A good list for XQuery question is talk @ x-query.com

Michael Kay
http://www.saxonica.com/

> -----Original Message-----
> From: Saloucious [mailto:saloucious@...]
> Sent: 09 October 2008 22:21
> To: saxon-help@...
> Subject: [saxon] Xquery Module External Variables
>
>
> Hi,
>
> May be this is not the place to ask this question, more an
> Xquery question than a Saxon one...
>
> Actually, I've an xquery module which declares few external variables.
>
> This module is called from an another query, eg:
>
> for $n in doc($my_doc)
> let $test := data($n/sample)
> return my_module:call()
>
> where $test is an external variable of my_module.
>
>
> Is there any possibilities to set module external variables
> dynamically ?
>
> Thanks.
>
> BTW, do you know an dedicated xquery mailling list ?
> --
> View this message in context:
> http://www.nabble.com/Xquery-Module-External-Variables-tp19907
> 612p19907612.html
> Sent from the saxon-help mailing list archive at Nabble.com.
>
>
> --------------------------------------------------------------
> -----------
> This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> Build the coolest Linux based applications with Moblin SDK &
> win great prizes
> Grand prize is a trip for two to an Open Source event
> anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> saxon-help mailing list archived at http://saxon.markmail.org/
> saxon-help@...
> https://lists.sourceforge.net/lists/listinfo/saxon-help

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Xquery Module External Variables

2008-10-09T14:20:31Z

Hi,

May be this is not the place to ask this question, more an Xquery question than a Saxon one...

Actually, I've an xquery module which declares few external variables.

This module is called from an another query, eg:

for $n in doc($my_doc)
let $test := data($n/sample)
return my_module:call()

where $test is an external variable of my_module.

Is there any possibilities to set module external variables dynamically ?

Thanks.

BTW, do you know an dedicated xquery mailling list ?

From forum: saxon-help

Re: Getting the version of Saxon in a transform

2008-10-08T13:10:35Z

>
> Thanks, that's what I was hoping for. But I noticed from the
> output of the system properties mentioned in the message that
> you are unable to tell whether you are running the B or SA
> version. Fortunately it doesn't matter for me at this point
> in time. For example I get the following when running
> Saxon-B 9.1.0.2:
>
> XSLT Processor:
> vendor: SAXON 9.1.0.2 from Saxonica
> product: SAXON
> version: 9.1.0.2
>

product-version will be "SA 9.1.0.2" if you are running Saxon-SA (that is,
if you are running with a SchemaAwareConfiguration, which will be the case
if you used the -sa flag on the command line).

I should really output "Saxonica" as vendor. It's the way it is because in
XSLT 1.0 only "vendor" was available so I tried to pack all the information
in there, and I left it that way in case anyone was parsing the value
returned.

Michael Kay
Saxonica

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Re: Getting the version of Saxon in a transform

2008-10-08T12:10:34Z

> From: Andrew Welch [mailto:andrew.j.welch@...]
> Sent: Wednesday, October 08, 2008 2:50 PM
> To: Mailing list for the SAXON XSLT and XQuery processor
> Subject: Re: [saxon] Getting the version of Saxon in a transform
>
> 2008/10/8 Houghton,Andrew <houghtoa@...>:
> > I was hoping to see a saxon:version() as xsd:string as an extension
> function, but I didn't see it. The only other possibility I can see is
> system-property(), but would the property name be?
>
> This sort of thing came up the other day:
>
> http://xsl.markmail.org/search/?q=processor+version#query:processor%20v
> ersion+page:1+mid:wwb3fytctkzspt4r+state:results
>
> basically you're after system-property('xsl:product-version')
>
> or from Java you can call:
>
> net.sf.saxon.Version.getProductVersion()

Thanks, that's what I was hoping for. But I noticed from the output of the system properties mentioned in the message that you are unable to tell whether you are running the B or SA version. Fortunately it doesn't matter for me at this point in time. For example I get the following when running Saxon-B 9.1.0.2:

XSLT Processor:
vendor: SAXON 9.1.0.2 from Saxonica
product: SAXON
version: 9.1.0.2

given:

<?xml version="1.0"?>
<xsl:transform version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="text"
media-type="text/plain" encoding="utf-8"
byte-order-mark="no" normalization-form="NFC"
/>
<xsl:template match="/">
<xsl:value-of select="concat('XSLT Processor: ', ' ')"/>
<xsl:value-of select="concat(' ', 'vendor: ', system-property('xsl:vendor'), ' ')" />
<xsl:if test="system-property('xsl:version') = '2.0'">
<xsl:value-of select="concat(' ', 'product: ', system-property('xsl:product-name'), ' ')"/>
<xsl:value-of select="concat(' ', 'version: ', system-property('xsl:product-version'), ' ')"/>
</xsl:if>
</xsl:template>
</xsl:transform>

I guess if I needed to determine whether it was B or SA I could saxon:try a Saxon-SA only function and see if it failed...

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Re: Getting the version of Saxon in a transform

2008-10-08T11:49:49Z

2008/10/8 Houghton,Andrew <houghtoa@...>:
> I have several processing streams that run Saxon for XSL transformation. These processing streams may be running different versions of Saxon. The XSL transforms that are being run use saxon:try to catch certain errors and when an error is caught in the transform, then the transform collects information from <error/> and routes it to a message queue for staff to look into. The issue I'm running into is that the information being collected doesn't indicate the version of Saxon that is running the transform which could be important for tracking down issues. Does anyone know of a way to retrieve the version of Saxon during a transform?
>
> I was hoping to see a saxon:version() as xsd:string as an extension function, but I didn't see it. The only other possibility I can see is system-property(), but would the property name be?

This sort of thing came up the other day:

http://xsl.markmail.org/search/?q=processor+version#query:processor%20version+page:1+mid:wwb3fytctkzspt4r+state:results

basically you're after system-property('xsl:product-version')

or from Java you can call:

net.sf.saxon.Version.getProductVersion()

--
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Getting the version of Saxon in a transform

2008-10-08T11:40:16Z

I have several processing streams that run Saxon for XSL transformation. These processing streams may be running different versions of Saxon. The XSL transforms that are being run use saxon:try to catch certain errors and when an error is caught in the transform, then the transform collects information from <error/> and routes it to a message queue for staff to look into. The issue I'm running into is that the information being collected doesn't indicate the version of Saxon that is running the transform which could be important for tracking down issues. Does anyone know of a way to retrieve the version of Saxon during a transform?

I was hoping to see a saxon:version() as xsd:string as an extension function, but I didn't see it. The only other possibility I can see is system-property(), but would the property name be?

Thanks, Andy.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Re: Passing Nodes To XPath Functions

2008-10-08T01:24:51Z

Thanks. It's not an acceptable workaround! I've reproduced the problem and will produce a further patch. I'm less and less comfortable with this JAXP interface - Saxon has moved so far in the direction of assuming static type information is available that it's very hard to do a good job when everything is dynamic.

Michael Kay

http://www.saxonica.com/

From: Karthick Sankarachary [mailto:karthick.sankarachary@...]
Sent: 08 October 2008 01:17
To: Michael Kay
Cc: Mailing list for the SAXON XSLT and XQuery processor
Subject: Re: [saxon] Passing Nodes To XPath Functions

Michael,

Thanks for pointing me to the patch. I was able to build it into the 9.1.0.2 version of saxon9.jar, and verify that it does indeed work for my use case.

There was one minor change I had to make in my XPathVariableResolver implementation to get it to work. Used to be that you could resolve a variable into a java.lang.String value and pass that to a custom function. However, now you have to wrap that string into a org.w3c.dom.Text node, which I think is an acceptable workaround.

Best Regards,
Karthick Sankarachary

On Mon, Oct 6, 2008 at 6:43 AM, Michael Kay <mike@...> wrote:

Thanks for the reminder. I had in fact fixed the code on the development branch, but had not got around to testing or publishing the equivalent patch for Saxon 9.1. This is now available, see

https://sourceforge.net/tracker/index.php?func=detail&aid=2149517&group_id=29872&atid=397617

Michael Kay

http://www.saxonica.com/

From: Karthick Sankarachary [mailto:karthick.sankarachary@...]
Sent: 04 October 2008 01:34

To: Michael Kay
Cc: Mailing list for the SAXON XSLT and XQuery processor
Subject: Re: [saxon] Passing Nodes To XPath Functions

Hi Michael,

Just checking to see if a patch is available for the issue described below. If there's anything I can do to help, please let me know.

Best Regards,
Karthick Sankarachary

On Thu, Sep 11, 2008 at 3:29 PM, Michael Kay <mike@...> wrote:

It looks as if I didn't run enough tests on the JAXP XPath interface. It's a pretty tough one to support because the architecture of the interface is so different from Saxon's native architecture, and it's full of XPath 1.0 assumptions. Also it's very underspecified - for example there is nothing that says what kinds of values get passed in the list of arguments to a function that's returned by a FunctionResolver. And although it's underspecified, users expect it to behave in the same way as other implementations, which can only be discovered by trial and error.

Saxon is saying "can't convert to Object" because it needs more information about what kind of object the function wants to see. But clearly to conform to JAXP we just have to guess, and pass something. In this case the function probably wants to see a DOM node, so I'll probably patch the code to provide that. However it remains the case that this interface is underspecified and undertested. I think there's a lot to be said for using the s9api interface if you want something more predictable and robust.

Incidentally, at the end of your code you cast the result to Node. Because you've asked for NODELIST, the result will be a DOM NodeList even if it only contains one node.

Michael Kay

Saxonica

From: Karthick Sankarachary [mailto:karthick.sankarachary@...]
Sent: 11 September 2008 21:17
To: Michael Kay

Cc: Mailing list for the SAXON XSLT and XQuery processor
Subject: Re: [saxon] Passing Nodes To XPath Functions

Hi Michael,

First off, thanks for the quick response.

To answer your questions:

Yes, I do have saxon9-dom.jar in my classpath, along with all of the other saxon9*jars.

Yes, the function in question is an extension function. And no, I don't run into this problem with built-in functions.

For your convenience, here's a complete JUnit test case:

import java.util.Iterator;

import java.util.List;

import javax.xml.namespace.NamespaceContext;

import javax.xml.namespace.QName;

import javax.xml.parsers.DocumentBuilder;

import javax.xml.parsers.DocumentBuilderFactory;

import javax.xml.xpath.XPath;

import javax.xml.xpath.XPathConstants;

import javax.xml.xpath.XPathExpression;

import javax.xml.xpath.XPathFactory;

import javax.xml.xpath.XPathFunction;

import javax.xml.xpath.XPathFunctionException;

import javax.xml.xpath.XPathFunctionResolver;

import javax.xml.xpath.XPathVariableResolver;

import junit.framework.TestCase;

import net.sf.saxon.om.NamespaceConstant;

import org.junit.Test;

import org.w3c.dom.Document;

import org.w3c.dom.Node;

public class NodeVariableTestCase extends TestCase {

@Test public void testFunctionCall() throws Throwable {

// Initialize DOM objects

 DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();

 dfactory.setNamespaceAware(true);

 DocumentBuilder docBuilder = dfactory.newDocumentBuilder();

 final Document doc = docBuilder.newDocument();

 final Node node = doc.createElement("Y");

 // Initialize XPath

 System.setProperty(

 "javax.xml.xpath.XPathFactory:" + NamespaceConstant.OBJECT_MODEL_SAXON,

 "net.sf.saxon.xpath.XPathFactoryImpl");

 XPathFactory xpf = XPathFactory.newInstance(NamespaceConstant.OBJECT_MODEL_SAXON);

 XPath xpe = xpf.newXPath();



 // Initialize various resolvers

 xpe.setXPathVariableResolver(new XPathVariableResolver() {

public Object resolveVariable(QName variableName) {

if ("Y".equals(variableName.getLocalPart())) {

return node;

}

return null;

}

 });

 xpe.setXPathFunctionResolver(new XPathFunctionResolver() {

 public XPathFunction resolveFunction(QName functionName, int arity) {

 if ("X".equals(functionName.getLocalPart())) {

 return new XPathFunction() {

public Object evaluate(List args)

throws XPathFunctionException {

if (args.size() == 1) {

if (args.get(0) instanceof Node) {

return args.get(0);

}

}

return null;

}



 };

 }

 return null;

 }

 });

 xpe.setNamespaceContext(new NamespaceContext() {

 public String getNamespaceURI(String prefix) {

 if (prefix.equals("saxon")) {

 return "http://saxon.sf.net/";

 } else {

 if (prefix.equals("tns")) {

 return "http://my.org.com/";

 } else

 return null;

 }

 }

 public String getPrefix(String uri) {

return null;

 }

 public Iterator getPrefixes(String uri) {

return null;

 }

 });



 // Compile

 XPathExpression expr =

 xpe.compile("tns:X($Y)");



 // Execute

 Node result = (Node) expr.evaluate(doc, XPathConstants.NODESET);

}

}

Best Regards,
Karthick Sankarachary

From forum: saxon-help

Re: xsl:copy and disable-output-escaping

2008-10-08T00:28:35Z

Andrew Welch schrieb:
>> If I understand correctly, this is to generate HTML that displays
>> XML (or HTML). If so, the included XSL might be helpful for a start.
>
> Have a look at Oliver Becker's "XML Verbatim" stylesheet:
>
> http://www2.informatik.hu-berlin.de/~obecker/XSLT/#xmlverbatim

Thanks, good pointer. Looks like it's the same approach, but instead of
a mere sketch an elaborate and complete solution.

Michael Ludwig

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Re: Passing Nodes To XPath Functions

2008-10-07T17:16:59Z

Michael,

Thanks for pointing me to the patch. I was able to build it into the 9.1.0.2 version of saxon9.jar, and verify that it does indeed work for my use case.

There was one minor change I had to make in my XPathVariableResolver implementation to get it to work. Used to be that you could resolve a variable into a java.lang.String value and pass that to a custom function. However, now you have to wrap that string into a org.w3c.dom.Text node, which I think is an acceptable workaround.

Best Regards,
Karthick Sankarachary

On Mon, Oct 6, 2008 at 6:43 AM, Michael Kay <mike@...> wrote:

Thanks for the reminder. I had in fact fixed the code on the development branch, but had not got around to testing or publishing the equivalent patch for Saxon 9.1. This is now available, see

https://sourceforge.net/tracker/index.php?func=detail&aid=2149517&group_id=29872&atid=397617

Michael Kay

http://www.saxonica.com/

From: Karthick Sankarachary [mailto:karthick.sankarachary@...]
Sent: 04 October 2008 01:34

To: Michael Kay
Cc: Mailing list for the SAXON XSLT and XQuery processor
Subject: Re: [saxon] Passing Nodes To XPath Functions

Hi Michael,

Just checking to see if a patch is available for the issue described below. If there's anything I can do to help, please let me know.

Best Regards,
Karthick Sankarachary

On Thu, Sep 11, 2008 at 3:29 PM, Michael Kay <mike@...> wrote:

It looks as if I didn't run enough tests on the JAXP XPath interface. It's a pretty tough one to support because the architecture of the interface is so different from Saxon's native architecture, and it's full of XPath 1.0 assumptions. Also it's very underspecified - for example there is nothing that says what kinds of values get passed in the list of arguments to a function that's returned by a FunctionResolver. And although it's underspecified, users expect it to behave in the same way as other implementations, which can only be discovered by trial and error.

Saxon is saying "can't convert to Object" because it needs more information about what kind of object the function wants to see. But clearly to conform to JAXP we just have to guess, and pass something. In this case the function probably wants to see a DOM node, so I'll probably patch the code to provide that. However it remains the case that this interface is underspecified and undertested. I think there's a lot to be said for using the s9api interface if you want something more predictable and robust.

Incidentally, at the end of your code you cast the result to Node. Because you've asked for NODELIST, the result will be a DOM NodeList even if it only contains one node.

Michael Kay

Saxonica

From: Karthick Sankarachary [mailto:karthick.sankarachary@...]
Sent: 11 September 2008 21:17
To: Michael Kay

Cc: Mailing list for the SAXON XSLT and XQuery processor
Subject: Re: [saxon] Passing Nodes To XPath Functions

Hi Michael,

First off, thanks for the quick response.

To answer your questions:

Yes, I do have saxon9-dom.jar in my classpath, along with all of the other saxon9*jars.

Yes, the function in question is an extension function. And no, I don't run into this problem with built-in functions.

For your convenience, here's a complete JUnit test case:

import java.util.Iterator;

import java.util.List;

import javax.xml.namespace.NamespaceContext;

import javax.xml.namespace.QName;

import javax.xml.parsers.DocumentBuilder;

import javax.xml.parsers.DocumentBuilderFactory;

import javax.xml.xpath.XPath;

import javax.xml.xpath.XPathConstants;

import javax.xml.xpath.XPathExpression;

import javax.xml.xpath.XPathFactory;

import javax.xml.xpath.XPathFunction;

import javax.xml.xpath.XPathFunctionException;

import javax.xml.xpath.XPathFunctionResolver;

import javax.xml.xpath.XPathVariableResolver;

import junit.framework.TestCase;

import net.sf.saxon.om.NamespaceConstant;

import org.junit.Test;

import org.w3c.dom.Document;

import org.w3c.dom.Node;

public class NodeVariableTestCase extends TestCase {

@Test public void testFunctionCall() throws Throwable {

// Initialize DOM objects

 DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();

 dfactory.setNamespaceAware(true);

 DocumentBuilder docBuilder = dfactory.newDocumentBuilder();

 final Document doc = docBuilder.newDocument();

 final Node node = doc.createElement("Y");

 // Initialize XPath

 System.setProperty(

 "javax.xml.xpath.XPathFactory:" + NamespaceConstant.OBJECT_MODEL_SAXON,

 "net.sf.saxon.xpath.XPathFactoryImpl");

 XPathFactory xpf = XPathFactory.newInstance(NamespaceConstant.OBJECT_MODEL_SAXON);

 XPath xpe = xpf.newXPath();



 // Initialize various resolvers

 xpe.setXPathVariableResolver(new XPathVariableResolver() {

public Object resolveVariable(QName variableName) {

if ("Y".equals(variableName.getLocalPart())) {

return node;

}

return null;

}

 });

 xpe.setXPathFunctionResolver(new XPathFunctionResolver() {

 public XPathFunction resolveFunction(QName functionName, int arity) {

 if ("X".equals(functionName.getLocalPart())) {

 return new XPathFunction() {

public Object evaluate(List args)

throws XPathFunctionException {

if (args.size() == 1) {

if (args.get(0) instanceof Node) {

return args.get(0);

}

}

return null;

}



 };

 }

 return null;

 }

 });

 xpe.setNamespaceContext(new NamespaceContext() {

 public String getNamespaceURI(String prefix) {

 if (prefix.equals("saxon")) {

 return "http://saxon.sf.net/";

 } else {

 if (prefix.equals("tns")) {

 return "http://my.org.com/";

 } else

 return null;

 }

 }

 public String getPrefix(String uri) {

return null;

 }

 public Iterator getPrefixes(String uri) {

return null;

 }

 });



 // Compile

 XPathExpression expr =

 xpe.compile("tns:X($Y)");



 // Execute

 Node result = (Node) expr.evaluate(doc, XPathConstants.NODESET);

}

}

Best Regards,
Karthick Sankarachary

From forum: saxon-help

Re: xsl:copy and disable-output-escaping

2008-10-07T08:04:26Z

>> Output must be:
>> > size="1">This is a text
>
> If I understand correctly, this is to generate HTML that displays
> XML (or HTML). If so, the included XSL might be helpful for a start.
>

Have a look at Oliver Becker's "XML Verbatim" stylesheet:

http://www2.informatik.hu-berlin.de/~obecker/XSLT/#xmlverbatim

--
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Re: xsl:copy and disable-output-escaping

2008-10-07T03:58:36Z

walterbt schrieb:
> andrew welch wrote:
>> Out of interest, what is the problem where CDATA sections and d-o-e
>> are the answer?
>
> It is a XML/CSS to HTML wrapper.

> Output must be:
> size="1">This is a text

If I understand correctly, this is to generate HTML that displays
XML (or HTML). If so, the included XSL might be helpful for a start.

If this is not the best way to do this sort of thing in 2.0 (or even
1.0, for that matter), I'd be glad to learn how to do it properly.

Michael Ludwig

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:template match="/">
<html>
<body>
<pre>
<xsl:apply-templates select="*"/>
</pre>
</body>
</html>
</xsl:template>

<xsl:template match="*[node()]">
<xsl:text><</xsl:text>
<xsl:value-of select="name()"/>
<xsl:apply-templates select="@*"/>
<xsl:text>></xsl:text>
<xsl:apply-templates select="node()"/>
<xsl:text></</xsl:text>
<xsl:value-of select="name()"/>
<xsl:text>></xsl:text>
</xsl:template>

<xsl:template match="*">
<xsl:text><</xsl:text>
<xsl:value-of select="name()"/>
<xsl:apply-templates select="@*"/>
<xsl:text>/></xsl:text>
</xsl:template>

<xsl:template match="@*">
<xsl:text> </xsl:text>
<xsl:value-of select="name()"/>
<xsl:text>="</xsl:text>
<xsl:value-of select="."/>
<xsl:text>"</xsl:text>
</xsl:template>

</xsl:stylesheet>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Re: xsl:copy and disable-output-escaping

2008-10-07T03:09:47Z

> <xsl:template match="style">
> <xsl:param name="content"/>
> <xsl:if test="@font-weight='bold'"><xsl:text
> disable-output-escaping="yes"><![CDATA[]]></xsl:text></xsl:if>
> <xsl:if test="@link-vertical-align='top'"><xsl:text
> disable-output-escaping="yes"><![CDATA[]]></xsl:text></xsl:if>
> <xsl:copy-of select="$content"/>
> <xsl:if
> test="@link-text-decoration='line-through'"><xsl:text
> disable-output-escaping="yes"><![CDATA[</strike>]]></xsl:text>
> </xsl:if>
> <xsl:if test="@font-weight='bold'"><xsl:text
> disable-output-escaping="yes"><![CDATA[]]></xsl:text></xsl:if>
> </xsl:template>

I'm having trouble relating this to the output you said you wanted, and
trouble seeing why you are generating a start tag but a </strike> end
tag. Let alone going to a great deal of effort to output nothing in the case
of font-weight='bold'.

But the clean way to handle this situation is with a set of template rules
like this:

<xsl:template match="style[@font-weight='bold']" priority="10">
<xsl:next-match/>
</xsl:template>

<xsl:template match="style[@link-vertical-align='top']" priority="9">
<xsl:next-match/>
</xsl:template>

<xsl:template match="style[@link-text-decoration='line-through']"
priority="8">
<strike><xsl:next-match/></strike>
</xsl:template>

<xsl:template match="style" priority="7">
<xsl:apply-templates/>
</xsl:template>

It doesn't suggest to me that d-o-e is justified. But I might have
misunderstood - your explanation is rather confusing.

Michael Kay
http://www.saxonica.com/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Re: Saxon 9.0.0.2J from Saxonica overwrite incaseaskingwith doc-available before

2008-10-07T02:55:28Z

>
> When doc-available() returns false, it leaves no record that
> it was called; there is therefore no guarantee that
> subsequent calls on doc-available() with the same argument
> will again return false (that is, the function is not stable
> in this case). Equally, there is nothing to stop
> xsl:result-document being called to create the resource that
> was found to be non-existent.
>

A slight change to the design: after doc-available(X) returns false, a
subsequent call on doc(X) will always now fail, and a subsequent call on
doc-available(X) will return false. However a call on <xsl:result-document
href="X"/> is allowed: you can create the document, but it will not become
available for use within the transformation.

Michael Kay
http://www.saxonica.com/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Re: xsl:copy and disable-output-escaping

2008-10-07T01:50:35Z

You've completely failed to explain your problem.

You say

Output must be:
<font color=

that is you want escaped markup as output, in which case there is no
problem at all you _want_ escaping so you do not want to use
disable-output-escaping as that stops that happening.

As has benn explained you can not use d-o-e in teh context that you want
it, but if it had had any effect then you would have got

<xsl:text
disable-output-escaping="yes"><![CDATA[]]></xsl:text></xsl:if>

is a no-op, whether the test is true or false, nothing will be generated
in teh result tree, quite likely the enttire expression is removed by
optimisation rewrites.

David

________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs.
________________________________________________________________________

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Re: xsl:copy and disable-output-escaping

2008-10-07T01:43:54Z

>
> I thought it is a saxon specific problem because it works
> using Xalan2.
>

There's a history to this.

XSLT 1.0 as originally published says:

"It is an error for output escaping to be disabled for a text node that is
used for something other than a text node in the result tree. "

Note this concept of "the result tree" - XSLT 1.0 is based very much on the
idea that there is a single result tree. Many vendors, not all, interpreted
this to mean that it was an error to use d-o-e when writing a text node to a
result tree fragment.

Erratum E2, however changed this, and stated explicitly that you could use
d-o-e when writing to a variable containing a result tree fragment. This was
known in the WG as the "sticky d-o-e" debate: specifically, d-o-e is
effectively a boolean attribute attached to each character in a result tree
fragment, which stays with it when the fragment is copied.

This change caused a lot of grief when it came to defining XSLT 2.0, which
abolished result tree fragments and turned them into fully-functional
temporary trees. To preserve the stickiness of d-o-e, it would have been
necessary to explicitly add this bit-per-character to the data model and
explain how it was propagated through the wide range of operations that were
now permitted on nodes in temporary trees.

In 2.0, d-o-e is deprecated, and processors are not required to implement it
at all. Using d-o-e when writing to a variable is covered by this sentence:

"If output escaping is disabled for an xsl:value-of or xsl:text instruction
evaluated when temporary output state is in effect, the request to disable
output escaping is ignored."

(Temporary output state is in force when evaluating variables or functions
and in other similar situations).

This is specifically listed as a known incompatibility: clause 20 of J.1.4
states:

"An erratum to XSLT 1.0 specified what has become known as "sticky
disable-output-escaping": specifically, that it should be possible to use
disable-output-escaping when writing a node to a temporary tree, and that
this information would be retained for use when the same node was later
copied to a final result tree and serialized. XSLT 2.0 no longer specifies
this behavior (though it permits it, at the discretion of the
implementation)."

(But I think the final phrase in parentheses is incorrect: it does not
permit it. Section 20.2 takes priority, because it is normative, whereas
Appendix J is non-normative.)

Michael Kay
http://www.saxonica.com/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Re: xsl:copy and disable-output-escaping

2008-10-07T01:40:02Z

andrew welch wrote:

Out of interest, what is the problem where CDATA sections and d-o-e
are the answer?

It is a XML/CSS to HTML wrapper.

I've following XML:
<structure>
<container class="abc">
<setting name="abc" width="500"/>
<content>
<style font-weight="bold" color="#FEFEFE" font-size="11" text-decoration="underline"/>
<text>This is a text</text>
</content>
... nested containers with other styles and other text ...
</container>
... other containers ...
</structure>

Output must be:
This is a text

Because I'am not allowed to use font-weight:bold; and text-decoration:underline as CSS. At the end, the output must be placed in a table-column

<table width="500"><tr><td>This is a text</td></tr></table>

Here are some xsl-parts:

<xsl:template match="container">
<xsl:apply-templates select="setting">
<xsl:with-param name="content"><xsl:apply-templates select="content | container"/></xsl:with-param>
</xsl:apply-templates>
</xsl:template>

<xsl:template match="setting">
<xsl:param name="content"/>
<table width="500"><tr><td>
<xsl:copy-of select="$content"/>
</td></tr></table>
</xsl:template>

<xsl:template match="text">
<xsl:apply-templates select="../style">
<xsl:with-param name="content"><xsl:apply-templates/></xsl:with-param>
</xsl:apply-templates>
</xsl:template>

<xsl:template match="style">
<xsl:param name="content"/>
<xsl:if test="@font-weight='bold'"><xsl:text disable-output-escaping="yes"><![CDATA[]]></xsl:text></xsl:if>
<xsl:if test="@link-vertical-align='top'"><xsl:text disable-output-escaping="yes"><![CDATA[]]></xsl:text></xsl:if>
<xsl:copy-of select="$content"/>
<xsl:if test="@link-text-decoration='line-through'"><xsl:text disable-output-escaping="yes"><![CDATA[</strike>]]></xsl:text></xsl:if>
<xsl:if test="@font-weight='bold'"><xsl:text disable-output-escaping="yes"><![CDATA[]]></xsl:text></xsl:if>
</xsl:template>

From forum: saxon-help

Re: xsl:copy and disable-output-escaping

2008-10-07T00:44:14Z

>> Using disable-output-escaping means either that you are an expert tackling
>> a
>> very unusual and difficult problem, or that you are a beginner who hasn't
>> yet worked out how to use the language properly.
>>
>
> I'm an expert. As I wrote I have this problem in another context where I
> have to use CDATA and disable-output-escaping.

Out of interest, what is the problem where CDATA sections and d-o-e
are the answer?

--
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Re: xsl:copy and disable-output-escaping

2008-10-07T00:17:35Z

I thought it is a saxon specific problem because it works using Xalan2.

Michael Kay wrote:

Using disable-output-escaping means either that you are an expert tackling a
very unusual and difficult problem, or that you are a beginner who hasn't
yet worked out how to use the language properly.

I'm an expert. As I wrote I have this problem in another context where I have to use CDATA and disable-output-escaping.

Thx, Walter

From forum: saxon-help

Re: Saxon 9.0.0.2J from Saxonica overwrite in caseaskingwith doc-available before

2008-10-06T15:39:48Z

I've looked into this.

When doc-available() returns false, it leaves no record that it was called;
there is therefore no guarantee that subsequent calls on doc-available()
with the same argument will again return false (that is, the function is not
stable in this case). Equally, there is nothing to stop xsl:result-document
being called to create the resource that was found to be non-existent.

I'm fixing this for a future release, but I will leave it as it is for the
9.1 branch.

Michael Kay
http://www.saxonica.com/

> -----Original Message-----
> From: Michael Kay [mailto:mike@...]
> Sent: 23 September 2008 23:08
> To: jim.robinson@...; 'Mailing list for the SAXON
> XSLT and XQuery processor'
> Subject: Re: [saxon] Saxon 9.0.0.2J from Saxonica overwrite
> in caseaskingwith doc-available before
>
> > I was just looking into this because some folks in my dept
> have been
> > using what appears to be a sneaky and fragile way to handle
> caching...
> > They've got a URI Resolver which can cache/resolve trees, and are
> > calling it like:
> >
> > <xsl:choose>
> > <xsl:when test="doc-available($cache-uri)">
> > <xsl:sequence select="doc($cache-uri)" />
> > </xsl:when>
> > <xsl:otherwise>
> > <xsl:variable name="result" type="element()">
> > ... build the result ...
> > </xsl:variable>
> > <xsl:result-document href="{$cache-uri}">
> > <xsl:sequence select="$result" />
> > </xsl:result-document>
> > <xsl:sequence select="$result" />
> > </xsl:otherwise>
> > </xsl:choose>
> >
> > I was very surprised that this worked, I would have expected it to
> > give the same error as you are recieving.
>
> Yes, I would expect so too: assuming that cache-uri is an
> absolute URI, or that if relative, the base URI is the same
> in both cases. It's possible that there's a minor difference
> between the absolutization of the two URIs that causes them
> not to compare equal, for example "file:/" versus "file:///".
>
> If you want to circumvent the safety checks defined in the
> spec, you can often achieve it by taking advantage of the
> fact that different URIs can refer to the same resource on disc.
>
> Michael Kay
> http://www.saxonica.com/
>
>
> --------------------------------------------------------------
> -----------
> This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge Build the coolest Linux based
> applications with Moblin SDK & win great prizes Grand prize
> is a trip for two to an Open Source event anywhere in the
> world http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> saxon-help mailing list archived at
> http://saxon.markmail.org/ saxon-help@...
> https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help

Re: xsl:copy and disable-output-escaping

2008-10-06T09:03:19Z

This list is for issues that are specific to Saxon. You're asking for XSLT
coding help, which is better done on the xsl-list at mulberrytech.com

disable-output-escaping has no effect unless the text nodes you are creating
are passed directly to the serializer, because escaping is something that
the serializer does. When variables are created, you are constructing nodes
in a tree; no escaping is done, and therefore there is nothing to disable.

Why are you trying to do it this way? What's wrong with

<xsl:variable name="test">5</xsl:variable>

?

Using disable-output-escaping means either that you are an expert tackling a
very unusual and difficult problem, or that you are a beginner who hasn't
yet worked out how to use the language properly. So it might be best (on
xsl-list, please, not here) to explain the problem you are trying to solve,
and find out the proper way to tackle it.

Michael Kay
http://www.saxonica.com/

> -----Original Message-----
> From: walterbt [mailto:guenstig-und-gut@...]
> Sent: 06 October 2008 16:43
> To: saxon-help@...
> Subject: [saxon] xsl:copy and disable-output-escaping
>
>
> Hi,
>
> I'm using Saxon-B 9.0.0.6. I've following XSL-Template
>
> <?xml version="1.0" encoding="UTF-8"?>
> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> version="2.0">
> <xsl:template match="/">
> <xsl:variable name="test"><xsl:text
> disable-output-escaping="yes"><![CDATA[5]]></xsl:
> text></xsl:variable>
> <xsl:copy-of select="$test"></xsl:copy-of>
> </xsl:template>
> </xsl:stylesheet>
>
> The output of $test in any browser is 5 but I
> want that the number 5 is bold. If I only use <xsl:text
> disable-output-escaping="yes"><![CDATA[5]]></xsl:text>
> it works. Can somebody help me?
>
> That's only a example which shall explain my problem. I know
> that I could write 5 without <xsl:text>.
>
> Thx Walter
>
> ps: sorry for my bad english
> --
> View this message in context:
> http://www.nabble.com/xsl%3Acopy-and-disable-output-escaping-t
> p19840509p19840509.html
> Sent from the saxon-help mailing list archive at Nabble.com.
>
>
> --------------------------------------------------------------
> -----------
> This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> Build the coolest Linux based applications with Moblin SDK &
> win great prizes
> Grand prize is a trip for two to an Open Source event
> anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> saxon-help mailing list archived at http://saxon.markmail.org/
> saxon-help@...
> https://lists.sourceforge.net/lists/listinfo/saxon-help

From forum: saxon-help