W3C home > Mailing lists > Public > www-ws-desc@w3.org > July 2002

RE: Issue 51: Should soap:header@part be nmtokens?

From: Liu, Kevin <kevin.liu@sap.com>
Date: Sat, 20 Jul 2002 03:42:46 +0200
Message-ID: <99CA63DD941EDC4EBA897048D9B0061DA95257@uspalx20a.pal.sap-ag.de>
To: "'Jacek Kopecky'" <jacek@systinet.com>
Cc: Web Services Description mailing list <www-ws-desc@w3.org>

Hi Jacek,

Overall I agree with you to reformulate the issue to "soap:body doesn't specify a message while soap:header does", and thanks for the good points. 

A few comments inline marked as <kevin></kevin>


-----Original Message-----
From: Jacek Kopecky [mailto:jacek@systinet.com]
Sent: Monday, July 15, 2002 6:08 AM
To: Liu, Kevin
Cc: Web Services Description mailing list
Subject: RE: Issue 51: Should soap:header@part be nmtokens?

(this message proposes a reformulation of issue 51)

 parts of messages are not reused because they just simply 
specify a type or element - the type and element definitions can 
be reused. So your 2 cannot be done and it's not a bug, it's a 

 As for header/@parts, the difference between the Body and a 
Header is that the Body may contain multiple XML elements, while 
a header IS AN XML element. What you are asking for may be a 
facility to specify groups of headers, but I personally don't 
think this is necessary - it doesn't make sense to group headers 
which will not be grouped in the actual messages anyway.


I am not that familiar with SOAP, but I think you are right. Given the fact that each header block may have different value for "role" and "mustUnderstand", it doesn't make sense to specify a list of parts as header blocks.

This remind me some related issues: current soap:header does NOT have construct to express role, and mustUnderstand (see the following example from soap 1.2 primer, seems current soap:header can not express it).   Have these issues already been raised before?

<?xml version='1.0' ?>
<env:Envelope xmlns:env="http://www.w3.org/2002/06/soap-envelope"> 
  <m:reservation xmlns:m="http://travelcompany.example.org/reservation" 
  <n:passenger xmlns:n="http://mycompany.example.com/employees"
   <n:name>John Q. Public</n:name>

Received on Friday, 19 July 2002 21:45:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:54:39 UTC