[Bug 8775] New: [XQuery 1.1] Private functions in module namespace

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8775

           Summary: [XQuery 1.1] Private functions in module namespace
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 1.1
        AssignedTo: jonathan.robie@redhat.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


The specification states:

Every function name declared in a library module must (when expanded) be in the
target namespace of the library module

This seems an unnecessary constraint in the case of private functions: we
should not impose restrictions that serve no useful purpose. Many users might
find it more natural to use the "local:" namespace for private functions.

Incidentally, I also checked to see what the uniqueness rules were for private
functions. I noticed it says: 

It is a static error [err:XQST0034] if the expanded QName and arity (number of
arguments) of the declared function are equal (as defined by the eq operator)
to the expanded QName and arity of another function in *function signatures*.

and the definition of "function signatures" is: "the set of functions that are
available to be called from within an expression". Like other aspects of the
static context, it is defining the static context in relation to an expression;
but for the uniqueness rules, it's not obvious what this expression is. It
might be better to say "equal () to the expanded QName and arity of another
function declared or imported in the containing Prolog".


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Sunday, 17 January 2010 21:38:05 UTC