MHonArc v2.5.0b2 -->

















ebxml-msg message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: Re: [ebxml-msg] Discussion: payload reference for use in SOAP body.Survey of options before writing this up.




From: Matthew MacKenzie <mattm@adobe.com>
To: Dale Moberg <dmoberg@cyclonecommerce.com>
Date: Thu, 20 May 2004 22:26:24 -0300






hex-escaped-cid-value-minus-opening-and-closing-brackets



??



On May 20, 2004, at 8:44 PM, Dale Moberg wrote:


I am following up with the namespace qualification for the URI-reference fragment using�an xpointer scheme-based approach,



CID:hex-escaped-cid-value-minus-opening-and-closing-brackets#xmlns(s12=http://www.w3.org/2003/05/soap-envelope) xpointer(/s12:envelope/s12:body)�


[This is how the fragment indicates the namespace qualification for soap12. Note this doesn't mean that the prefix in the soap message has to be s12 but only that whatever prefix�was�actually�used is associated with the URI given in the xmlns() pointer-part.]


This is from the http://www.w3.org/TR/xptr-xmlns/�which basically�writes up�the above piece of syntax for the xmlns() pointer-part.. The namespace value has to be escaped.�The framework�allows�an optional�whitespace�string�between the items in the�fragment's pointer-parts.


�


�


___________________________

Matthew MacKenzie

Senior Architect

IDBU Server Solutions

Adobe Systems Canada Inc.

http://www.adobe.com/products/server/

mattm@adobe.com

+1 (506) 871.5409








References:

RE: [ebxml-msg] Discussion: payload reference for use in SOAP body. Survey of options before writing this up.
From: "Dale Moberg" <dmoberg@cyclonecommerce.com>






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]