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

SOAP and Tool Accommodation

From: Conner, Wesley M <Wesley.Conner@gs.com>
Date: Tue, 17 Oct 2000 11:24:28 -0400
Message-Id: <3D0E38416579D411803C00D0B7AF6B21069125@gsny47e.et.gs.com>
To: "'xml-dist-app@w3.org'" <xml-dist-app@w3.org>
I'm hoping to use SOAP (envelope and encoding) for a current project. An
initial challenge is to work with the tools at my disposal to author XML
schemas. Both Extensibility's "XML Authority (XA)" and Altova's "XmlSpy"
complain about the following aspects of the XML Schema for SOAP v 1.1 at

Item #1: Neither recognizes the 'default' attribute on the attribute

	<attribute name='root' default='0'>
		<simpleType base='boolean'>
			<pattern value='0|1'/>

Item #2: Neither cares for the 'minOccurs' attribute on the attribute

	<attributeGroup name='arrayAttributes'>
		<attribute ref='tns:arrayType' minOccurs='1' />
		<attribute ref='tns:offset'/>

I'm guessing that XA and XmlSpy simply don't support attribute qualification
(yet). Is it reasonable to copy the SOAP schema to a local web server and
weaken it ever so slightly by omitting these attributes? [That is, leverage
the xsi:schemaLocation attribute to reference my weaker copy.] This would
allow some forward motion although I'd obviously lose the desired conformity
checking on the affected attributes. If this isn't total heresy, are there
any suggestions on how best to affect this kind of tool accommodation (e.g.,
file naming)? Is there a better solution (e.g., better tool, better work

W. Conner
Received on Tuesday, 17 October 2000 11:25:06 UTC

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