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: Pete Wenzel <pete@seebeyond.com>
To: ebxml-msg@lists.oasis-open.org
Date: Thu, 20 May 2004 11:10:18 -0700






Thus spoke Matthew MacKenzie (mattm@adobe.com) on Thu, May 20, 2004 at 12:54:42PM -0300:
> So, something like the following may be a good idea..:
> 
> cid:<soapBody | attachmentID>[#XPath]
> 
> Producing the following valid URIs...
> 
> cid:attachment1
> cid:attachment1#/ContainerElement/Invoice[0]
> cid:soapBody
> cid:soapBody#/Invoice[0]

The last 2 assume that we assign special meaning to the literal
"soapBody", right?  Otherwise we'd have to require an ID attribute on
the element to be referenced.  cid: really doesn't seem appropriate
for these cases.  Wouldn't a fragment with XPath automatically assume
the correct base URI (the current document)?

  #/Envelope/Body
  #/Envelope/Body/Invoice[0]

Or something like that?

--Pete
Pete Wenzel <pete@seebeyond.com>
Senior Architect, SeeBeyond
Standards & Product Strategy
+1-626-471-6311 (US-Pacific)






Follow-Ups:

Re: [ebxml-msg] Discussion: payload reference for use in SOAP body.Survey of options before writing this up.
From: Matthew MacKenzie <mattm@adobe.com>



References:

Re: [ebxml-msg] Discussion: payload reference for use in SOAP body.Survey of options before writing this up.
From: Matthew MacKenzie <mattm@adobe.com>






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

--

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