W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > December 2006

[resend] Part 2 - {element declaration} property for SOAP Header Block component

From: Jonathan Marsh <jonathan@wso2.com>
Date: Thu, 21 Dec 2006 15:31:55 -0800
To: "'Ramkumar Menon'" <ramkumar.menon@gmail.com>
Cc: <public-ws-desc-comments@w3.org>
Message-ID: <005701c72558$35680df0$3401a8c0@DELLICIOUS>
Thanks for your comment.  The WS Description Working Group tracked this
issue as a CR095 [1].

 

Re your first question, yes indeed the syntax does not allow #any for a SOAP
header block.

 

Re your second question, the Working Group flipped it and posited why should
#any be allowed?  The WSDL description does not preclude SOAP headers from
being added in addition to those not described explicitly with wsoap:header.
Using #any in this case is by definition a no-op.  Making a specific
allowance in the language serves no purpose other than to complicate the
language.

 

With these decisions, the Working Group closed the issue with no change to
the existing language of the spec.

 

Unless you let us know otherwise by mid-January, we will assume you agree
with the resolution of this issue.

 

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

 

 

Jonathan Marsh -  <http://www.wso2.com> http://www.wso2.com -
<http://auburnmarshes.spaces.live.com> http://auburnmarshes.spaces.live.com

 

  _____  

From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of Ramkumar Menon
Sent: Monday, November 13, 2006 12:02 PM
To: www-ws-desc@w3.org
Subject: Part 2 - {element declaration} property for SOAP Header Block
component

 

Gurus,

 

 

{element declaration} for a SOAP header block component is defined in Part 2
as follows.

"The element declaration from the {
<http://www.w3.org/TR/2006/CR-wsdl20-20060327#property-Description.elementde
clarations> element declarations} resolved to by the value of the element
attribute information item. It is an error for the element attribute
information item to have a value and that value does not resolve to a global
element declaration from the {
<http://www.w3.org/TR/2006/CR-wsdl20-20060327#property-Description.elementde
clarations> element declarations} property of the
<http://www.w3.org/TR/2006/CR-wsdl20-20060327#component-Description>
Description component.
<http://www.w3.org/TR/wsdl20-adjuncts/#SOAPHeaderBlock-5052-summary>  " 
The assertion
<http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#SOAPHeaderBlock-5052
> SOAPHeaderBlock-5052  has been defined to enforce this. 

 

My Question is - Does this prevent the header blocks to be defined using
"#any" as opposed to an explicit element declaration ?  

If the answer is a yes, should we prevent this in first place ? If so, what
are the known issues in allowing such a definition ?

 

rgds,

Ram

 

-- 
Shift to the left, shift to the right!
Pop up, push down, byte, byte, byte!

-Ramkumar Menon
A typical Macroprocessor 
Received on Thursday, 21 December 2006 23:31:38 GMT

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