W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > September 2005

RE: SOAP and HTTP bindings: {parent} property for nested components

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Thu, 15 Sep 2005 12:14:38 -0700
Message-ID: <37D0366A39A9044286B2783EB4C3C4E81A28CD@RED-MSG-10.redmond.corp.microsoft.com>
To: "Hugo Haas" <hugo@w3.org>
Cc: <public-ws-desc-comments@w3.org>

Thanks for your comment.  The WS Description Working Group tracked this
as a Last Call comment LC320 [1].  The Working Group agreed to add a
parent property as you suggest.

If we don't hear otherwise within two weeks, we will assume this
satisfies your concern.

[1] http://www.w3.org/2002/ws/desc/5/lc-issues/issues.html#LC320

> -----Original Message-----
> From: public-ws-desc-comments-request@w3.org [mailto:public-ws-desc-
> comments-request@w3.org] On Behalf Of Hugo Haas
> Sent: Wednesday, August 24, 2005 3:13 AM
> To: public-ws-desc-comments@w3.org
> Subject: SOAP and HTTP bindings: {parent} property for nested
> components
> Part 2 defines a number of new components: a SOAP Module component, a
> SOAP Header Block component, a HTTP Header component.
> All of those are nested components. Part 1 states:
>   The component that contains a nested component is referred to as the
>   parent of the nested components. Nested components have a {parent}
>   property that is a reference to their parent component.
>   -- http://www.w3.org/TR/2005/WD-wsdl20-20050803/#Description_details
> It would be good to define a similar {parent} property for our nested
> components in Part 2, especially as the concept of parent is used in
> the IRI identification of those components.
> --
> Hugo Haas - W3C
> mailto:hugo@w3.org - http://www.w3.org/People/Hugo/
Received on Thursday, 15 September 2005 19:15:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:32 GMT