W3C home > Mailing lists > Public > public-xsd-databinding@w3.org > March 2007

RE: untestable assertions

From: <paul.downey@bt.com>
Date: Tue, 20 Mar 2007 15:43:32 -0000
Message-ID: <2A7793353757DB4392DF4DFBBC9522550A20177E@I2KM11-UKBR.domain1.systemhost.net>
To: <paul@wso2.com>
Cc: <public-xsd-databinding@w3.org>

Hi Paul!

I should reassure you that the assertions are all testable,
just not all expressible in XPath:


testing for a pattern where element A has an element B of ComplexType C which references A isn't easy in XPath, even when they're in the same schema document ..


-----Original Message-----
From: Paul Fremantle [mailto:paul@wso2.com]
Sent: Tue 3/20/2007 1:45 PM
To: Downey,P,Paul,XSL3 R
Cc: public-xsd-databinding@w3.org
Subject: Re: untestable assertions
I'm significantly concerned at the philosophical implications of 
untestable assertions. I suggest we need to address the 
http://en.wikipedia.org/wiki/Falsifiability of the whole realm :-)


paul.downey@bt.com wrote:
> In our document text, we have a number of assertions which aren't readily expressible as an XPath expression. Jon's latest constraint to disallow cyclic references being one, requiring UTF-8/UTF-16 being another.
> Something we could consider is adding assertions as placeholders to our pattern detector, as suggested by Rick, here:
> http://www.oreillynet.com/xml/blog/2007/03/expressing_untested_and_untest.html
> Paul

Paul Fremantle
VP/Technology and Partnerships, WSO2

(646) 290 8050

"Oxygenating the Web Service Platform", www.wso2.com
Received on Tuesday, 20 March 2007 15:47:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:58 UTC