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

Policy people, philosophers, ethics people, people with great wisdom...

  • From: "Costello, Roger L." <costello@mitre.org>
  • To: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>
  • Date: Fri, 26 Feb 2016 12:08:14 +0000

Policy people
Hi Folks,

We have an interesting situation: one development team followed the XML Schema specification strictly, the other team recognized a flaw in the specification and instead followed its intent. Who's right? Where should we go? I am interested to hear your thoughts on this issue. 

Let's summarize:

1. Xerces reports an error with the below schema.

2. Saxon reports that the below schema is fine.

3. Xerces strictly follows the algorithm specified in the XML Schema specification.

4. Saxon does not strictly follow the algorithm because the Saxon team recognized that the algorithm is flawed.

5. We have an interoperability problem: when validating the exact same schema, system 1 using Xerces gets a different result than system 2 using Saxon.

So, where do we go from here? As I see it, there are three choices:

(a) The Xerces team modifies their code to be consistent with Saxon.

(b) The Saxon team modifies their code to be consistent with Xerces.

(c) Both the Xerces team and the Saxon team do nothing and the world remains in the current state of non-interoperability.

Thoughts?

/Roger
----------------------------------------------------------------------------------
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
    
    <xs:element name="A" type="xs:double" />
    <xs:element name="B" substitutionGroup="A" type="xs:double" />
    
    <xs:complexType name="base">
        <xs:sequence>
            <xs:element ref="A" minOccurs="0" maxOccurs="unbounded" />
        </xs:sequence>
    </xs:complexType>
    
    <xs:complexType name="derived">
        <xs:complexContent>
            <xs:restriction base="base">
                <xs:sequence>
                    <xs:element ref="B" minOccurs="0" />
                </xs:sequence>
            </xs:restriction>
        </xs:complexContent>
    </xs:complexType>
</xs:schema>


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


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.