W3C home > Mailing lists > Public > xmlp-comments@w3.org > August 2001

RE: Issue 24

From: David Fallside <fallside@us.ibm.com>
Date: Mon, 27 Aug 2001 12:03:27 -0700
To: xmlp-comments@w3.org
Message-ID: <OFD814C0F3.9DC24163-ON88256AB5.00686615@boulder.ibm.com>
It appears that the identity of the originator of issue 24 has been lost.
However, the proposed resolution appears to satisfy at least one randomly
chosen external evaluator.

............................................
David C. Fallside, IBM
Ext Ph: 530.477.7169
Int  Ph: 544.9665
fallside@us.ibm.com

----- Forwarded by David Fallside/Santa Teresa/IBM on 08/27/2001 12:00 PM
-----
                                                                                                                  
                    "Erik                                                                                         
                    Christensen"         To:     David Fallside/Santa Teresa/IBM@IBMUS                            
                    <erikc@microso       cc:     "Paul Cotton" <pcotton@microsoft.com>, "Frystyk"                 
                    ft.com>               <frystyk@microsoft.com>                                                 
                                         Subject:     RE: Issue 24                                                
                    07/25/2001                                                                                    
                    09:55 AM                                                                                      
                                                                                                                  
                                                                                                                  



David,

Well, I think I understand the issue from reading your description
below, and the issue does concern me, but I must admit I was not aware
of the issue until I received this mail.  I'm kind of wondering how the
issue was associated with me in the first place.  But, if you still want
my opinion, I think the proposed solution looks great.  :-)

-Erik
-----Original Message-----
From: David Fallside [mailto:fallside@us.ibm.com]
Sent: Tuesday, July 24, 2001 3:22 PM
To: Erik Christensen
Cc: Paul Cotton; Frystyk
Subject: Issue 24


Erik, have you had a chance to think about our proposal?
David

............................................
David C. Fallside, IBM
Ext Ph: 530.477.7169
Int  Ph: 544.9665
fallside@us.ibm.com

----- Forwarded by David Fallside/Santa Teresa/IBM on 07/24/2001 03:20
PM
-----


                    David Fallside

                                         To:     erikc@microsoft.com

                    07/20/2001           cc:     marting@develop.com

                    09:24 PM             From:   David Fallside/Santa
Teresa/IBM@IBMUS
                                         Subject:     Issue 24










Erik, I am writing on behalf of the W3C XML Protocol working group. We
recorded an issue #24 [1] which is attributed to you, the text of which
is:

"It should be allowed to have multiple headers using the same namespace
(multiple signatures for example) in a single SOAP message. The current
SOAP envelope schema doesn't allow this."

We propose to resolve the issue as follows:

The SOAP envelope schema [2] defines the type for the Header element as
having a content model of: <xs:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> This allows multiple
qualified elements from any namespace except
http://www.w3.org/2001/06/soap-envelope to appear.

Please let me know by email whether or not this proposed resolution
meets the issue. Thanks, David

[1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x24
[2] http://www.w3.org/2001/06/soap-envelope
............................................
David C. Fallside, IBM
Ext Ph: 530.477.7169
Int  Ph: 544.9665
fallside@us.ibm.com
Received on Monday, 27 August 2001 15:03:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:42:26 GMT