W3C home > Mailing lists > Public > xml-dist-app@w3.org > January 2002

[i98] Proposed Resolution for Content Based Routing Issue

From: Paul Denning <pauld@mitre.org>
Date: Fri, 25 Jan 2002 16:37:58 -0500
Message-Id: <5.1.0.14.0.20020122143642.078246b8@mailsrv1.mitre.org>
To: xml-dist-app@w3.org
This message responds to an action item from the Nov 2001 face to face 
meeting to track down the story on issue 98 [1].

The issue description states "Content based routing of unormalized 
payloads. For example, if it is needed to specify that any payload that 
includes the term FOO-BAR be sent to a particular location, and if the 
payloads can contain unnormalized variations of FOO-BAR, then some of the 
payloads may not be routed to the right places. (At least by some definitions."

Proposed Resolution:  Routing is not within the scope of SOAP 1.2, but can 
specified using the extension mechanisms provided by SOAP 1.2.  If 
normalization is required for content-based routing extensions to work 
properly, then the specifications for content-based routing extensions must 
ensure normalization.  This appears to be feasible by defining a SOAP 
header block (with mustUnderstand="true") whose semantics would imply that 
the SOAP envelope (and its descendants) be normalized before applying a 
content-based routing function.  In addition, a related extension feature 
could use a SOAP header block to indicate explicitly that a SOAP envelope 
has not yet been normalized; such a header block can be removed after the 
envelope has been normalized.  To reiterate, extensions for routing and 
normalization are not within the scope of the SOAP 1.2 specifications.

[1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x98

Paul
Received on Friday, 25 January 2002 16:38:24 GMT

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