W3C home > Mailing lists > Public > www-ql@w3.org > April to June 2003

Re: xf Namespace

From: Jonathan Robie <jonathan.robie@datadirect-technologies.com>
Date: Thu, 05 Jun 2003 14:22:37 -0400
Message-Id: <>
To: Mark_R_Maxey@raytheon.com, www-ql@w3.org
Cc: Mark_R_Maxey@raytheon.com

At 01:12 PM 6/5/2003 -0500, Mark R Maxey wrote:

>XQuery/XPath issue 228 & XSLT issue 155 state that built-in functions are 
>in the F&O namespace with no controls on changing that namespace.  In the 
>11/15/02 draft, I assumed that "xf" was used to refer to this namespace 
>(though, it was not listed among the predefined namespaces in 
>  Declarations).

Actually, the prefix is now "fn". The predefined  functions in XQuery are [1]:

       xml = http://www.w3.org/XML/1998/namespace
       xs = http://www.w3.org/2001/XMLSchema
       xsi = http://www.w3.org/2001/XMLSchema-instance
       fn = http://www.w3.org/2003/05/xpath-functions
       xdt = http://www.w3.org/2003/05/xpath-datatypes

Note that this same prefix is now used in the Functions and Operators [2].

>While I was looking at the 5/2/3 
>Use Cases Q3, I noticed that built-in string manipulation function 
>"starts-with" was qualified with the "xf" namespace.  Is this a typo or is 
>this still necessary?  Did one of the imports change the default namespace 
>for built-in functions?  If "xf" is still a valid namespace, then 
>shouldn't it be added to the list of predefined namespace in the 
><http://www.w3.org/TR/xquery/#id-namespace-decls>5/2/3 Namespace Declarations?

My bad.

It is not necessary. If I had used "fn:starts-with" it would be redundant 
but correct - as is, it is not even correct, since the xf: prefix is undefined.


[1] http://www.w3.org/TR/xquery/#id-namespace-decls
[2] http://www.w3.org/TR/xpath-functions/ 
Received on Thursday, 5 June 2003 14:22:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:43:42 UTC