W3C home > Mailing lists > Public > xml-dist-app@w3.org > September 2000

RE: Schematron schema for SOAP 1.1 Envelopes

From: David Orchard <orchard@pacificspirit.com>
Date: Tue, 19 Sep 2000 15:12:33 -0700
To: "'Henrik Frystyk Nielsen'" <frystyk@microsoft.com>, <ricko@geotempo.com>, <xml-dist-app@w3.org>
Message-ID: <005c01c02286$b63284a0$7f06a8c0@image8100>
I made the exact same mistake that Rick made.

Why?  Because registering schema locations at a version/date-less URL is
going to cause enormous compatibility problems in the future.

Dave Orchard
XML Architect
Jamcracker, Inc.
935 Stewart Dr.
Sunnyvale, CA 94086
p: 408.830.1886
f: 408.328.0936
m: 604.908.6837

Named to Red Herring's list of 100 Most Important Companies:

Named to Fortune's list of Cool Companies 2000:

-----Original Message-----
From: xml-dist-app-request@w3.org [mailto:xml-dist-app-request@w3.org]On
Behalf Of Henrik Frystyk Nielsen
Sent: Tuesday, September 19, 2000 9:34 AM
To: ricko@geotempo.com; xml-dist-app@w3.org
Subject: RE: Schematron schema for SOAP 1.1 Envelopes

Did you try and follow the links:




They infact resolve to XSD schemas (and yes there are slight problems
because SXD schemas have changed slightly since these were published).


> The SOAP 1.1 spec suffers from not being expressed in a
> schema language.
> (RDF had the same problem.)
> I attaching a sample schema for SOAP 1.1 written using the
> Schematron[1]
> schema language. This uses Xpath expressions rather than being
> interested in issues of data or storage types. [2]
> Most of the constraints could be well-handled in XML Schemas as well.
> The only constraint that it seems that Schematron can express that XML
> Schemas could not is the one connecting use of the actor
> attribute with
> the faultfactor attribute.  Some more work could be done
> getting lexical
> schecking of data values better.
Received on Tuesday, 19 September 2000 18:11:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:10 UTC