• From: Ramkumar Menon <ramkumar.menon@g...>
• To: xml-dev@l...
• Date: Sat, 20 Jun 2009 00:44:32 -0700

Spec lists the following as reserved fn names.

attribute,comment,document-node,element,empty-sequence,if,item,node,processing-instruction,schema-attribute,schema-element,text,typeswitch

Does this mean that user can register other "unprefixed" xpath
functions [custom ones].

If No, okay.
If yes, quick, but naive Q.
What if user defined an unprefixed function named instruction(), or a
function named sequence()?
Lets say instruction() and sequence() functions return numerical values.
What would happen if the user performed the xpath on the following doc.

<numberOfTasks>
   <processing>20</processing>
   ...
    <empty>1</empty>
</numberOfTasks>

xslt
-------
<xsl:template match="numberOfTasks">
    <netValue><xsl:value-of select="processing-instruction()"/></netValue>
    <someValue><xsl:value-of select="empty-sequence()"/></someValue>
</xsl:template>
Whats the behaviour?
Should this be explicitly disallowed?

I'll close my eyes and wait :-) Someone's gonna use a sledgehammer on me :-)

Ram

• Follow-Ups:
  • RE: q on xpath 2.0 reserved functions
    • From: "Michael Kay" <mike@s...>
  • Re: q on xpath 2.0 reserved functions
    • From: Ramkumar Menon <ramkumar.menon@g...>