Re: Comment on Part 2, Section 5.9.3

John,

Yes, the HTTP Header problem is CR036 [1].

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

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca



"John Kaputin (gmail)" <jakaputin@gmail.com> 
05/24/2006 02:27 PM

To
Arthur Ryman/Toronto/IBM@IBMCA
cc
www-ws-desc@w3.org
Subject
Re: Comment on Part 2, Section 5.9.3






Arthur,
That's how I interpreted the spec when implementing SOAPHeaderBlock in 
Woden. i.e. the getElementDeclaration() method returns an 
ElementDeclaration, not a QName.  I agree it would be more consistent with 
other parts of the spec to change the description from xs:QName to 
ElementDeclaration.

A similar problem exists in the HTTP Header component:

{type definition} REQUIRED. An xs:QName, being a reference to a Type 
Definition component in the {type definitions} property of the Description 
component

regards,
John Kaputin.


On 5/9/06, Arthur Ryman <ryman@ca.ibm.com> wrote:

The {element declaration} property of SOAP Header Block is defined as a 
QName but it should be an Element Declaration component. 

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca