W3C home > Mailing lists > Public > www-ws-desc@w3.org > November 2006

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

From: Ramkumar Menon <ramkumar.menon@gmail.com>
Date: Mon, 13 Nov 2006 12:02:07 -0800
Message-ID: <22bb8a4e0611131202o2728fbe8icd020975b45d870d@mail.gmail.com>
To: www-ws-desc@w3.org
Gurus,


{element declaration} for a SOAP header block component is defined in Part 2
as follows.
"The element declaration from the {element
declarations<http://www.w3.org/TR/2006/CR-wsdl20-20060327#property-Description.elementdeclarations>}
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 {element
declarations<http://www.w3.org/TR/2006/CR-wsdl20-20060327#property-Description.elementdeclarations>}
property of the
Description<http://www.w3.org/TR/2006/CR-wsdl20-20060327#component-Description>component.
† <http://www.w3.org/TR/wsdl20-adjuncts/#SOAPHeaderBlock-5052-summary>"
The assertion SOAPHeaderBlock-5052<http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#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 Monday, 13 November 2006 20:02:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:42 GMT