Proposed resolution to issue 143

On the call last week I took an action to propose text to resolve Issue
143, about alternative type systems.

Background:

1.	We agreed on the call that the message attribute always refered
to an element declaration in the {element declarations} property of the
definitions component. 

2.	We agreed on the call that the {element declarations} property
could be populated by a variety of type systems.

3.	We agreed that references to things that were not elements would
require a new collection property, akin to {element declarations} on the
definitions component AND a new attribute in place of the message
attribute to refer to such constructs.

The spec at[1] has the diffs that cover 1. The changes are in section
2.4 (Message Reference) with identical changes to Section 2.5 (Fault
Reference).

I note that 2. is already covered by text in section 2.1.3:

"The element declaration components corresponding to all the element
declarations defined as descendants of the types element information
item, if any, plus any imported element definitions. At a minimum this
will include all the global element declarations defined by XML Schema
element element information items. It MAY also include any definition
from some other type system which describes the [local name], [namespace
name], [attributes] and [children] properties of an element information
item."

I note that 3. is already covered by text in section 3.2:

"The extension specification SHOULD, if necessary, define additional
properties of 2.1.1 The Definitions Component to hold the components of
the referenced type system. It is expected that additional extensibility
attributes for Message Reference and Fault Reference components will
also be defined, along with a mechanism for resolving the values of
those attributes to a particular imported type system component."

Gudge

[1]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.xml?rev=1
.14.2.1

Received on Thursday, 26 February 2004 07:11:59 UTC