- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Wed, 5 Oct 2005 13:36:10 -0700
- 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 LC321 [1]. The Working Group agreed to fix the problem by adopting the proposal at [2].
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#LC321
[2] http://lists.w3.org/Archives/Public/www-ws-desc/2005Sep/0011.html
> -----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 binding: clarify that the lack {soap mep} value is an
> error
>
> In Table 5-4. Mapping from XML Representation to SOAP Operation
> Component Properties from 5.8.4 Mapping from XML Representation to
> Component Properties in Part 2, we say:
>
>
> ����������������������������������������������������������������������
> ���
> � Property � Value
> �
>
> ����������������������������������������������������������������������
> ���
> � � The actual value of the wsoap:mep attribute
> �
> � � information item, if present. If not, the actual
> �
> � � value of the wsoap:mepDefault attribute
> information �
> � {soap mep} � item of the parent wsdl:binding element
> information �
> � � item, if present. If not the value as defined by
> the �
> � � default SOAP binding rules (for SOAP 1.2, see
> 5.11.3 �
> � � Default Binding Rules), if applicable.
> �
>
> ����������������������������������������������������������������������
> ���
>
> We should add "Otherwise an error" to clarify that it's not OK for
> {soap mep} not to have a value.
>
> --
> Hugo Haas - W3C
> mailto:hugo@w3.org - http://www.w3.org/People/Hugo/
Received on Wednesday, 5 October 2005 20:37:08 UTC