XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] 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



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS