Namespace does not contain any functions

djmarquette · February 9th, 2005, 12:43 PM

Hello,

I am trying to implement a simple example from Michael Kay's XSLT 2.0 3rd edition book in a xslt I have. It's the comment example from page 240, where the comment should output file generation properties.

I call a template similar to the following from the book:

Code:

    <xsl:template name="file-properties">
        <xsl:comment>
            <xsl:text> Generated on: </xsl:text>
            <xsl:value-of select="format-dateTime(
                    current-dateTime(), '[D]  [MNn]  [Y]  at  [H]:[m01]:[s01]')" />
            <xsl:text> using </xsl:text>
            <xsl:value-of select="system-property('xsl:product-name')" />
            <xsl:text> version </xsl:text>
            <xsl:value-of select="system-property('xsl:product-version')" />
        </xsl:comment>
    </xsl:template>

At first I get errors stating the date functions are not valid XSLT or XPATH functions. I have the following namespaces declared at the top:

Code:

<xsl:stylesheet version="2.0" 
        xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
        xmlns:xs="http://www.w3.org/2001/XMLSchema" 
        xmlns:fn="http://www.w3.org/2004/07/xpath-functions" 
        xmlns:xdt="http://www.w3.org/2004/07/xpath-datatypes">

Next I try to prepend the functions with either xs: or fn: (I've tried both) and get a complaint that "Namespace whichever does not contain any functions.

Any suggestions on how to implement this? I don't know if its an error from the book example, or something I am doing wrong.

Thanks in advance for your help,
Dan

mhkay · February 9th, 2005, 01:09 PM

The problem is that the namespace for the standard function library keeps changing with each new draft, so you need to check what it is for the particular Saxon version you are using.

However, there's an easier solution: don't use a prefix for standard functions like format-dateTime and current-dateTime. Whatever the namespace is, it's the default.

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference

mhkay · February 9th, 2005, 01:12 PM

I should have checked: you are using an XSLT 2.0 processor, I assume?

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference

djmarquette · February 9th, 2005, 03:14 PM

Thanks Michael. I am using the MSXML 4.0 processor. OK, so after checking msdn (I am in a MS development tools shop) I see that MSXML 4.0 and later are only XSLT 1.0, so perhaps that is the root of my problem here.

That issue aside, and referring to your first reply, to use the default function library, should I then remove the fn namespace (or others) from my declarations?

Thanks again, guess I'll look into XSLT processor alternatives that I can use here at work.

Dan

mhkay · February 9th, 2005, 03:42 PM

If you're using a 1.0 processor (as you are) then you not only need to remove the prefix from these functions, you need to rewrite your stylesheet so it doesn't need these functions. The 2.0 function library is vastly richer than the 1.0 library.

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference

merothehero86 · June 22nd, 2009, 06:21 AM

I need to use the xslt version 2.0 but the posts suggest that I need to have an xslt processor of 2.0 to be able to use the functionalities of version 2.0

how can I upgrade my xslt processor then?!

Martin Honnen · June 22nd, 2009, 06:29 AM

I know of four XSLT and XPath 2.0 implementations, there is Saxon 9 from http://saxon.sourceforge.net/, there is AltovaXML tools from http://www.altova.com/, there is Gestalt from http://gestalt.sourceforge.net/ and I think IBM has a beta release of its own implementation.
You can't really "upgrade" your XSLT processor unless you consider replacing a Java Trax/JAXP XSLT 1.0 processor like Xalan or like Saxon 6 with Saxon 9 an upgrade.
So choose an XSLT 2.0 processor for your platform and use that.