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

RE: Part 2: Mapping from XML Representations to Component Properties

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Thu, 15 Sep 2005 12:09:07 -0700
Message-ID: <37D0366A39A9044286B2783EB4C3C4E81A28C3@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 LC313 [1].  The Working Group agreed to fix the
problem 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#LC313

> -----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 2:55 AM
> To: public-ws-desc-comments@w3.org
> Subject: Part 2: Mapping from XML Representations to Component
> Properties
> 
> A number of properties in Part 2 are optional, but their mapping from
> XML says "otherwise empty", which means that that they would always be
> present, but sometimes empty, which is different from not being
> present.
> 
> I am proposing to remove this "otherwise empty" from the mapping for
> the following properties to make them really optional:
> - {soap fault subcodes}
> - {soap action}
> - {http location}
> - {http error reason phrase}
> - {http transfer coding}
> 
> This would mean replacing certain "if empty" in their definition by
> "if not present".
> 
> {soap fault code} and {http error status code} suffer from the
> same problem but should not as I mentioned in another issue I have
> raised.
> 
> --
> Hugo Haas - W3C
> mailto:hugo@w3.org - http://www.w3.org/People/Hugo/
Received on Thursday, 15 September 2005 19:09:47 GMT

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