W3C home > Mailing lists > Public > www-ws-desc@w3.org > June 2004

Re: Issues 225: new proposals

From: Roberto Chinnici <Roberto.Chinnici@Sun.COM>
Date: Mon, 21 Jun 2004 16:28:22 -0700
To: Mark Nottingham <mark.nottingham@bea.com>
Cc: www-ws-desc@w3.org
Message-id: <40D76F16.3000009@sun.com>

Mark Nottingham wrote:
> OK, in an attempt to consolidate discussion and make the changes 
> crisper, so as not to make WSDL more vague, while still addressing the 
> issue, I make the following proposals (split up for convenience):
> Five direct text changes, (a) through (e).
> Section 2.1.1:
> a) "Type system components are element declarations drawn from some type 
> system. They define the [local name], [namespace name], [children] and 
> [attributes] properties of an element information item."
> -->
> "Type system components describe the constraints on a message's content. 
> By default, these constraints are expressed in terms of the XML Infoset 
> (i.e., they define the [local name], [namespace name], [children] and 
> [attributes] properties of an element information item). Type systems 
> based upon other data models may be accommodated by extensions to WSDL; 
> see Section 3."
> Section 2.5.1:
> b) "A Message Reference component associates to a message exchanged in 
> an operation an XML element declaration that specifies its message 
> content."
>  -->
> "A Message Reference component associates a defined type with a message 
> exchanged in an operation. By default, the type system is based upon the 
> XML Infoset."
> c) "If a non-XML type system is in use..." --> "If a type system not 
> based upon the XML Infoset is in use..."
> Section 3:
> d) "At the abstract level, the {element declarations} property of the 
> Definitions component is a collection of imported and embedded schema 
> components. By design, WSDL supports any schema language for which the 
> syntax and semantics of import (i.e., the ability to import some schema 
> by reference) or embed (i.e., the ability to embed a schema directly 
> into another document) have been defined. However, only the XML Schema 
> implementation is defined in this specification. Instances of WSDL 
> (i.e., WSDL documents) MAY require support for an alternative schema 
> language by using the standard wsdl:required attribute information item 
> (any imported or embedded XML Schema element information items may be 
> regarded as having this attribute information item set)."
> -->
> """The content of messages and faults may be constrained using type 
> system components. These constraints are based upon a specific data 
> model, and expressed using a particular schema language.
> Although a variety of data models can be accommodated (through WSDL 
> extensions), this specification only defines a means of expressing 
> constraints based upon the XML Infoset. Furthermore, although a number 
> of alternate schema languages can be used to constrain the XML Infoset 
> (as long as they support the semantics of either embedding or importing 
> schema), this specification only defines the use of XML Schema.
> Specifically, the {element declarations} of the Definitions component is 
> a collection of imported and embedded schema components that describe 
> Infoset Element Information Items.
> When extensions are used to enable the use of a non-Infoset data model, 
> or a non-Schema constraint language, the wsdl:required attribute 
> information item MAY be used to require support for that extension.
> """
> e) "The types element information item encloses data type definitions 
> used to define messages..." --> "The types element information item 
> encloses data type definitions based upon the XML Infoset..."

+1, although I like my formulation better for (a) -- it provides more
explanation inline instead of referring the reader to a different section.
> Change the "types" element's name to "elements".

> Ask the part 3 editors to identify the data models that defined bindings 
> are compatible with.



Roberto Chinnici
Java Web Services
Sun Microsystems, Inc.
Received on Monday, 21 June 2004 19:26:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:41 UTC