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: ebxml-msg@lists.oasis-open.org
Date: Fri, 21 May 2004 13:14:15 -0300






Ok, so in the case of the SOAP Body, do we allow an arbitrary CID, e.g.


cid:some@crap#xmlns(s12=http://www.w3.org/2003/05/soap-envelope) xpointer(/s12:envelope/s12:body)�


<some@crap%??xmlns%??=http%??%??%??www.w3.org%??2003%??05%??soap-envelope%??xpointer%??s12%??envelope%??s12%??body%??



I don't really like this....


How about we use xml:id?


xmlid:invoiceA


...


<soap:Body>

<Invoice xml:id="invoiceA" />

</soap:Body>



On May 21, 2004, at 1:32 AM, Dale Moberg wrote:


From RFC� 2392

�


���� Notes: In Internet mail messages, the addr-spec in a Content-ID


���� [MIME] or Message-ID [822] header is enclosed in angle brackets


���� (<>).� Since addr-spec in a Message-ID or Content-ID might contain


���� characters not allowed within a URL; any such character (including


���� "/", which is reserved within the "mid" scheme) must be hex-encoded


���� using the %hh escape mechanism in [URL].


�


��  A "cid" URL is converted to the corresponding Content-ID message


��  header [MIME] by removing the "cid:" prefix, converting the % encoded


�� character to their equivalent US-ASCII characters, and enclosing the


�� remaining parts with an angle bracket pair, "<" and ">".� For


��  example, "cid:foo4%25foo1@bar.net" corresponds to


�


���� Content-ID: <foo4%25foo1@bar.net>


�


�� Reversing the process and converting URL special characters to their


��  % encodings produces the original cid.


�


[I think there�is a typo. I think it�should read


�


���� Content-ID: foo4%foo1@bar.net


�


%25 == "%"]


�


�


�


�