[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: XML design of ((a and b) or c)

• From: "Klotz, Leigh" <Leigh.Klotz@x...>
• To: "David Carlisle" <davidc@n...>
• Date: Fri, 15 Dec 2006 16:21:14 -0800

Let me clarify the XSLT point: XSLT defines functions such as current()
which are not in the XPath set.
Those functions are not prefixed.  XForms and XSLT bear the same
relationship to XPath.

Leigh. 

-----Original Message-----
From: David Carlisle [mailto:davidc@n...] 
Sent: Friday, December 15, 2006 4:19 PM
To: Klotz, Leigh
Cc: xml-dev@l...
Subject: Re:  XML design of ((a and b) or c)


> On the nighmare issue, originally all XForms XPath extension functions
> were in the XForms namespace, but we removed that as a result of
public
> comments that showed that the XPath 1.0 Recommendation did not allow
> qualified names, 

??? XPath1  (and now 2) specifies function names are QNames.

> and that neither XSLT nor XML Signature W3C
> recommendations specified qualified names as extension functions.  

??? XSLT 1 mandates that all extension functions use qualified names
with
a non empty prefix. xslt 1 says:

  If a FunctionName in a FunctionCall expression is not an NCName
  (i.e. if it contains a colon), then it is treated as a call to an
  extension function 

> extension functions would be namespaced in XPath 2.0.  But the botch
is
> with XPath 1.0 not allowing them.

In what way are they disallowed in XPath 1?

David

• Follow-Ups:
  • RE: XML design of ((a and b) or c)
    • From: "Michael Kay" <mike@s...>
  • Re: XML design of ((a and b) or c)
    • From: David Carlisle <davidc@n...>

• References:
  • Re: XML design of ((a and b) or c)
    • From: David Carlisle <davidc@n...>