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

Re: Issues 223, 224: Component Model definition (proposal)

From: Mark Nottingham <mark.nottingham@bea.com>
Date: Fri, 11 Jun 2004 16:02:36 -0700
Message-Id: <6E192F26-BBFB-11D8-88CB-000A95BD86C0@bea.com>
To: www-ws-desc@w3.org

It would also be good to add text to this effect:

"""New properties can be defined by other specifications using the  
extensibility mechanisms described in Section 6. Such properties SHOULD  
identify the components they are relevant to, and their names SHOULD  
NOT conflict with those of already-defined properties."""

(I'm a little worried about name space management of properties; has  
there any been any discussion of this?)


On Jun 10, 2004, at 4:30 PM, Mark Nottingham wrote:

>
> Issues 223 [1] and 224 [2] have to do with the definition of the  
> component model. I propose the following changes:
>
> * Change the introduction text from Section 2 of part one from:
>
> """This section describes the conceptual model for WSDL as a set of   
> components with properties, each aspect of a Web service that WSDL   
> can describe having its own property. In addition an XML Infoset   
> representation for these components is provided, along with a  mapping  
> from that representation to the various component  properties. How the  
> XML Infoset representation of a given set of  WSDL components is  
> constructed is outside the scope of this  specification."""
>
> to:
>
> """This section describes the conceptual model of WSDL as a set of  
> components with attached properties, which collectively describe a Web  
> service. Each subsection herein describes a different type of  
> component, its defined properties, and its representation as an XML  
> Infoset.
>
> Components are named collections of properties that correspond to  
> different aspects of Web services. Properties are unordered and unique  
> with respect to the component they are associated with. Individual  
> properties' definitions may constrain their content (e.g., to a typed  
> value, another component, or a set of typed values or components), and  
> components may require the presence of a property to be considered  
> conformant.
>
> In addition to the direct XML Infoset representation described here,  
> the component model allows components external to the Infoset through  
> the mechanisms described in section 4.
>
> A component model can be extracted from a given XML Infoset which  
> conforms to the WSDL XML Schema [ref] by recursively mapping  
> Information Items to their identified components, starting with the  
> wsdl:description element information item. This includes the  
> application of the mechanisms described in Section 4.
>
> This document does not specify a means of producing an XML Infoset  
> representation from a given set of WSDL components."""
>
>
> * Add to Notational Conventions of part one (and others as  
> appropriate):
>
> """This specification uses curly brackets (e.g., {property}) to  
> indicate a property in the WSDL component model, as defined in section  
> 2."""
>
>
> 1.  
> http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/issues/wsd- 
> issues.html#x223
> 2.  
> http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/issues/wsd- 
> issues.html#x224
>
> --
> Mark Nottingham   Principal Technologist
> Office of the CTO   BEA Systems
>
>

--
Mark Nottingham   Principal Technologist
Office of the CTO   BEA Systems
Received on Friday, 11 June 2004 19:02:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:31 GMT