W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > January to March 2009

[Bug 6541] New: Assertions and in-scope functions

From: <bugzilla@wiggum.w3.org>
Date: Sun, 08 Feb 2009 19:57:41 +0000
To: www-xml-schema-comments@w3.org
Message-ID: <bug-6541-703@http.www.w3.org/Bugs/Public/>

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

           Summary: Assertions and in-scope functions
           Product: XML Schema
           Version: 1.1 only
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: David_E3@VERIFONE.com
        ReportedBy: mike@saxonica.com
         QAContact: www-xml-schema-comments@w3.org
                CC: cmsmcq@blackmesatech.com


The current rules for assertions state that the whole of the XPath 2.0 syntax
must be implemented, but they leave the set of functions in the function
library entirely implementation-defined (3.13.6.2 clause 2.2.8).

This seems to leave an enormous interoperability hole. Users, especially
industry bodies producing schemas for an industry, need to have confidence that
their schemas will be usable across a range of schema processors. To enable
them to use assertions while achieving this level of interoperability, they
need some kind of assurance about the minumum set of functions that will be
available.

We could define the minimum set to be (a) all the constructor functions for
built in types plus (b) all the functions defined in the F+O namespace for
XPath 2.0. Or we could define a smaller set by doing some fairly arbitrary
cherry-picking from that set. But a minimum set that is empty is fairly
unusable.


-- 
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, 8 February 2009 19:57:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:09 UTC