- From: David Fallside <fallside@us.ibm.com>
- Date: Thu, 15 Apr 2004 17:29:32 -0700
- To: xmlp-comments@w3.org, Noah Mendelsohn <noah_mendelsohn@us.ibm.com>
- Message-ID: <OFCAD5878C.5587BCE9-ON88256E78.0001E277-88256E78.0002B47C@us.ibm.com>
The XMLP WG agreed to resolve issue 455 ( http://www.w3.org/2000/xp/Group/xmlp-issues.html#x455), which you raised, using the 4 items below. We trust they satisfy your concerns, if not, please contact the WG asap. The text describing the Representation Header will state: 1. "The type of the reinsert attribute information item is xs:boolean . When this attribute is specified on the Representation header block with a value of "true", it indicates that a SOAP forwarding intermediary node processing the header block must reinsert the header block. This means that when used in conjunction with the relay attribute, defined in [SOAP Part 1] 5.2.4 SOAP Relay Attribute, with a value of "true", the Representation header block will always be relayed by a SOAP forwarding intermediary. When this attribute is specified on the Representation header block with a value of "false", the behavior of the SOAP node processing the header block is the same as that when the attribute is not specified, and normal SOAP processing rules apply. The presence of this attribute has no effect on the processing of a Representation header by a SOAP endpoint." 2. The reinsert attribute is not namespace qualified. 3. "Such Representation header blocks SHOULD NOT have the same metadata (such as media-type). If such Representation header blocks have the same metadata then any one of them may be used." 4. Implementations MAY need to process Representation header blocks BEFORE other header blocks that might dereference URIs. ............................................ David C. Fallside, IBM Data Management Standards Tel 530.477.7169 (TL 544.9665) fallside@us.ibm.com
Received on Thursday, 15 April 2004 20:40:51 UTC