This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22277 - fn/format-number.xml not valid according to catalog-schema.xsd
Summary: fn/format-number.xml not valid according to catalog-schema.xsd
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Working drafts
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-05 06:24 UTC by Sorin Nasoi
Modified: 2013-06-10 14:01 UTC (History)
1 user (show)

See Also:


Attachments
Here are the errors as shown by Saxon in oXygenxml (13.37 KB, image/png)
2013-06-05 10:15 UTC, Sorin Nasoi
Details

Description Sorin Nasoi 2013-06-05 06:24:45 UTC
Because of this test-case 'Catalog002' from 'app-CatalogCheck' is failing.
Comment 1 O'Neil Delpratt 2013-06-05 10:02:06 UTC
We are getting the following errors in the validation:

"Value '
Comment 2 Sorin Nasoi 2013-06-05 10:15:45 UTC
Created attachment 1368 [details]
Here are the errors as shown by Saxon in oXygenxml

Here are the errors and their locations within the document.
Comment 3 O'Neil Delpratt 2013-06-10 14:01:46 UTC
These validation errors occur as the result of a bug in Xerces, which we cannot do anything about. I have committed a work-around in the catalog schema.

For the simple type 'one-char' we have the restriction:

        <xs:restriction base="xs:string">
            <xs:length value="1"/>
        </xs:restriction>

This we change to using a pattern whcih seems to work, please see the following:

        <xs:restriction base="xs:string">
            <xs:pattern value="." />
        </xs:restriction>