OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-iic message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [no subject]

 -----Original Message-----
From: Michael Kass [mailto:michael.kass@nist.gov]
Sent: Tuesday, June 08, 2004 2:59 PM
To: Jacques Durand; ebXML IIC - main list (E-mail) (E-mail)
Cc: tsakach@certivo.net
Subject: RE: [ebxml-iic] minutes, and next call - follow up comments
Jacques,
 
 
    One more thing that I think makes combining <SetPayload> into the
<MessageDeclaration> is that, because an XSLT processor can only output one
stream (and can only use one stylesheet at a time I believe).. multiple
Payloads cannot be mutated (each with their own <Mutator> stylesheet) and
attached to the outgoing message.  So combining multiple <SetPayload>
operations (or even one) inside of a <MessageDeclaration> will not work, and
I would think any workaround would be inefficient.   Comments from
implementers?
 
Mike
 
 
-----Original Message-----
From: Michael Kass [mailto:michael.kass@nist.gov]
Sent: Tuesday, June 08, 2004 5:42 PM
To: Jacques Durand; ebXML IIC - main list (E-mail) (E-mail)
Subject: RE: [ebxml-iic] minutes, and next call - follow up comments
 
Jacques and all,
 
  Here's my comments from yesterdays' minutes.
 
Mike
 
 
 
3. TestFramework 1.1 Follow-up on latest discussions:
- Comments on Use Case #1:  why still SetPayload() used? Cant we manipulate
payload directly
via the XML representation of the entire message, as we did for
GetPayload()? Mike: yes 
 
[MIKE] -  I say "yes" with reservations:  The current XML (using
<SetPayload> ) separates message envelope
construction from payload construction and inclusion.  It really requires no
more XML code, and allows any type 
of payload (GIF image, executable code, XML file, EDI file) to be attached,
agnostic of the messaging protocol being
used.  (if we eliminate the "content-ID" and "content-Location" attributes,
and simply substitute "id".
 
[MIKE] - Combining <SetPayload> into the <MessageDeclaration> makes sense,
however it puts a burden on an XSLT processor, that cannot process non-xml
content, cannot generate multiple output streams ( i.e. multiple payloads ),
and cannot interface with the messaging API.  XSLT is a text processor only.
Trying to make it perform attachment construction (I believe) is beyond the
scope of what was intended when Drake Certivo suggested using XSLT as a
mutator to message envelope and payloads. 
 
[MIKE] - It "can" be done, but that means a "2 pass" parse of the
<MessageDeclaration>. Once to construct the message envelope (via XSLT), and
a second pass to interpret the transport and messaging envelope declaration,
as well as to interpret the <SetPayload> instruction, find the appropriate
attachment ( via URI ), and bind the attachment to the message ( apriori,
knowing the transport and messaging binding ) This is defined in the
<ConfigurationGroup> with the <Transport> and <Envelope> configuration
parameters.
 
 
 
Comments?
 
 
In any event, here is what a "merged" <MessageDeclaration> might look like:
 
<MessageDeclaration>
<mime:MessageContainer>
<soap:Envelope>
<soap:Header>
<eb:MessageHeader>
</soap:Header>
<soap:Body>
<eb:Manifest>
</soap:Body>
</soap:Envelope>
</mime:MessageContainer>
 
<SetPayload id="PORequest" >  (attachment of an "inlined" XML document)
<PurchaseOrderRequest xmlns="xxx">
...
</PurchaseOrderRequest>
 
<SetPayload id="BusinessAck"  fileURI="BusinessAck.xml">  (attachmen of an
external file)
</SetPayload>
 
</MessageDeclaration>
 
 
 
Advantage: knowledge on the message envelope (MIME here) does not have to be
hard coded in a
Test Driver operation.
 
[MIKE] - That is true.  Placing <SetPayload> inside of the
<MessageDeclaration> instead of external to it has no influence on whether
the Test Driver is agnostic to MIME or not.  Removing the mime:Content-ID
and mime:Content-Location attributes, combined with providing a
<ConfigurationGroup> element of 
 
<Transport>HTTP1.1</Transport>
                   or 
<Transport>SMTP</Transport>
                   or 
<Transport>FTP</Transport>
                  with
<Envelope>SOAP1.2</Envelope>
                   or 
<Envelope>ebXML2.0</Envelope>
                   or
<Envelope>none</Envelope>
 
 
....  should provide the Test Driver with the knowledge it needs to
construct a payload and attach it accordingly, given a generic XML
declaration such as 
 
<SetPayload id="abc" fileURI="def"/>
 
 
 Instead, we only have to define how the canonical XML representation of
any message, binds to a particular envelope (MIME or other) and also
transport.
 
[MIKE] - We've done that with MIME and SOAP declarations for ebMS testing,
although that requires the Test Driver to 
 
1)       parse the XML <MessageDeclaration> and construct the MIME parts,
then 
2)   again parse the <MessageDeclaration> with an XSLT processor to mutate
the <MessageDeclaration> and generate the proper SOAP envelope and ebXML
content.  
 
That means, if anyone wants to create an FTP test suite, the must define a
canonical XML representation of the FTP envelope and transport declaration,
and submit it as a schema to the IIC, so that a standard XML test suite can
be generated for that particular protocol.   Any IIC compliant Test Driver
MUST be able to interpret that and mutate and generate the appropriate
message envelope and payloads based upon that schema.
 
-          that will keep us independent from a particular attachment
representation (SwA, or other).
 
[MIKE] - As long as we define the underlying bindings between our XML
representation and the particular messaging protocol, and provide
<ConfigurationGroup> parameters that list those protocols as enumerated
types .. yes..
 
- Pete: that amounts to defining extensibility points. We can handle future
envelope formats
by just adding bindings / env types. Instead of having to redefine the
semantics of SetPayload plus
having to define the binding anyway (as replacement of GetPayload).
 
 
 
- Monica: current small changes in BPSS will not mandate changes in use
cases. WSDL support may
need be considered in new use cases. Multi-party collab will also define
"segments", which in turn
define some context visibility. Can we still define these scopes of
visibility?
- Monica will review current use Cases, and check if (1) they cover enough
of BPSS reqs, (2) check
if there is any need for "loops" (e.g. retries, and while-do- )
- removal of Test Step concept: as long as threads can compose as well, is
OK.
- Assertion op is loosing its context (FilterResult). But we can assign
FilterResults to parameters,
so we can then reference them in Assertions. Several of them may need be
referenced anyway, not just
the latest produced.
 
[MIKE] - This is true.
 
 
-----Original Message-----
From: Jacques Durand [mailto:JDurand@us.fujitsu.com]
Sent: Monday, June 07, 2004 9:03 PM
To: ebXML IIC - main list (E-mail) (E-mail)
Subject: [ebxml-iic] minutes, and next call
 
 
1. Minutes attached, confirming the approval of Mike as secretary:
congratulations! 
2. Next call: 
Time: Monday June 14, 2004, 2pm PT 
Host: Fujitsu 
Toll only : 1-512-225-3050 
Participant code: 716071 
Agenda will follow, mostly a  follow-up on previous one. 
Regards, 
jacques 
<<IIC_June_07_04_minutes.txt>> 

------_=_NextPart_001_01C45196.18B2C5D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40"; xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>minutes, and next call</TITLE>

<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C450A3.D1C55B80"; rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; =
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto
}
SPAN.EmailStyle17 {
	COLOR: navy; mso-style-type: personal; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle18 {
	COLOR: #993366; mso-style-type: personal; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle19 {
	COLOR: #003300; mso-style-type: personal-reply; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in">
<DIV><FONT size=3D2>
<P><FONT face=3D"Courier New"><FONT size=3D2><SPAN =
class=3D091431622-13062004>This=20
call:</SPAN></FONT></FONT></P>
<P><FONT face=3D"Courier New"><FONT size=3D2><SPAN=20
class=3D091431622-13062004></SPAN></FONT></FONT>&nbsp;</P>
<P><FONT face=3D"Courier New"><FONT size=3D2><SPAN =
class=3D091431622-13062004>Note:=20
dure to some contraints, I am likely to attend only 30mn (2pm-2:30) of =
the=20
call.</SPAN></FONT></FONT></P>
<P><FONT face=3D"Courier New"><FONT size=3D2><SPAN=20
class=3D091431622-13062004></SPAN>Time: Monday June 14, 2004, 2pm PT =
<BR>Host:=20
Fujitsu </FONT></FONT><BR><FONT face=3D"Courier New" size=3D2>Toll only =
:=20
1-512-225-3050 </FONT><BR><FONT face=3D"Courier New" =
size=3D2>Participant code:=20
716071 </FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D091431622-13062004>Agenda:</SPAN></FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D091431622-13062004>1.=20
Review of IIC TestPlan for ETSI, and possible vote as Committee=20
Draft.</SPAN></FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D091431622-13062004>2.=20
</SPAN></FONT><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D091431622-13062004>Follow-up on Test Framework upgrades for =
Busienss=20
Process:</SPAN></FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D091431622-13062004>- the=20
PutMessage() call, and way to build a message.</SPAN></FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D091431622-13062004>-=20
comments on Use Cases #2, #3, and refining test case=20
scripting.</SPAN></FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</P>
<P><SPAN class=3D091431622-13062004><FONT face=3DArial color=3D#0000ff=20
size=3D2>Regards,</FONT></SPAN></P>
<P><SPAN class=3D091431622-13062004><FONT face=3DArial color=3D#0000ff=20
size=3D2>Jacques</FONT></SPAN></P>
<P>--------&nbsp;<SPAN class=3D091431622-13062004>Jacques: =
</SPAN>comments<SPAN=20
class=3D091431622-13062004> on latest scripting of Use Cases #2 and #3=20
:</SPAN></P>
<P>Use Case #2:</P>
<P>- SHouldn't we wrap the entire case script in a "main" thread?<SPAN=20
class=3D091431622-13062004> (as best practice)</SPAN></P>
<P>-&nbsp; I assume we don't have to wrap entire threads in a =
&lt;split&gt;=20
element<SPAN class=3D091431622-13062004>, although that is =
OK.</SPAN></P>
<P>Also, split can have as many "thread" arguments as we want.</P>
<P>- thread_02 needs to wait 300sec before doing the check.</P>
<P>- I assume that we can define threads separately (not have to embed =
them)</P>
<P>So I assume the case could also be coded as (approximate =
syntax):</P>
<P>&lt;!-- ********* main thread ******** --&gt;</P>
<P>&lt;thread name=3D"main"&gt;</P>
<P>&lt;putMessage&gt;...&lt;/putMessage&gt;</P>
<P>&lt;split&gt;&lt;threadref =
nameRef=3D"checkErrors"/&gt;&lt;/split&gt;</P>
<P>&lt;getMessage&gt;... (purchaseOrder)...&lt;/getMessage&gt;</P>
<P>&lt;assertion&gt;...messageCount =3D 1...&lt;/assertion&gt;</P>
<P>&lt;join&gt;&lt;ThreadRef =
nameRef=3D"checkErrors"/&gt;&lt;/join&gt;</P>
<P>&lt;/thread&gt;</P>
<P>&lt;!-- ********* checkErrors thread ******** --&gt;</P>
<P>&lt;thread name=3D"checkErrors"&gt;</P>
<P>&lt;sleep&gt;300&lt;/sleep&gt;</P>
<P>&lt;getMessage&gt;...&lt;/getMessage&gt;</P>
<P>&lt;assertion&gt;...FilterResult//*[not(eb:ErrorList...&lt;/assertion=
&gt;</P>
<P>&lt;/thread&gt;</P>
<P>Use Case #3:</P>
<P>- The embedding is confusing: why is a full thread embedded into an=20
"Assertion" element?</P>
<P>If an assertion is just an operator, and if we have now the =
attributes:=20
when_true and when_false</P>
<P>,e.g. when_true=3D"split(thread)", then we shouldn't need this =
embedding. </P>
<P>- If we define a "main" thread, then we can assume this is the one =
that gets=20
executed.</P>
<P>We can define other threads outside, and just reuse /reference =
them.</P>
<P>&lt;!-- ********* main thread ******** --&gt;</P>
<P>&lt;thread name=3D"main"&gt;</P>
<P>&lt;putMessage&gt;..m1..&lt;/putMessage&gt;</P>
<P>&lt;split&gt;&lt;threadref =
nameRef=3D"checkErrors"/&gt;&lt;/split&gt;</P>
<P>&lt;getMessage&gt;... m2...&lt;/getMessage&gt;</P>
<P>&lt;assertion&gt;...when_true=3D"split(approvalthread)"../approval..&=
lt;/assertion&gt;</P>
<P>&lt;assertion&gt;...when_true=3D"split(rejectionthread)"../rejection.=
.&lt;/assertion&gt;</P>
<P>&lt;join jointype=3D"or" &gt;</P>
<P>&lt;ThreadRef nameRef=3D"approvalthread"/&gt;</P>
<P>&lt;ThreadRef nameRef=3D"rejectionthread"/&gt;</P>
<P>&lt;/join&gt;</P>
<P>&lt;join jointype=3D"and" &gt;</P>
<P>&lt;ThreadRef nameRef=3D"checkErrors"/&gt;</P>
<P>&lt;/join&gt;</P>
<P>&lt;/thread&gt;</P>
<P>&lt;!-- ********* approval thread ******** --&gt;</P>
<P>&lt;thread name=3D"approvalthread"&gt;</P>
<P>&lt;getMessage&gt;... m3...&lt;/getMessage&gt;</P>
<P>&lt;assertion&gt;...FilterResult//...&lt;/assertion&gt;</P>
<P>&lt;putMessage&gt;..m4..&lt;/putMessage&gt;</P>
<P>&lt;getMessage&gt;... m5...&lt;/getMessage&gt;</P>
<P>&lt;assertion&gt;...when_true=3D"continue" 
FilterResult//...&lt;/assertion&gt;</P>
<P>&lt;/thread&gt;</P>
<P>&lt;!-- ********* rejection thread ******** --&gt;</P>
<P>&lt;thread name=3D"rejectionthread"&gt;</P>
<P>&lt;getMessage&gt;... m6...&lt;/getMessage&gt;</P>
<P>&lt;assertion&gt;...when_true=3D"continue"=20
FilterResult//...&lt;/assertion&gt;</P>
<P>&lt;/thread&gt;</P>
<P>&lt;!-- ********* checkErrors thread ******** --&gt;</P>
<P>&lt;thread name=3D"checkErrors"&gt;</P>
<P>&lt;sleep&gt;300&lt;/sleep&gt;</P>
<P>&lt;getMessage&gt;...&lt;/getMessage&gt;</P>
<P>&lt;assertion&gt;...FilterResult//*[not(eb:ErrorList...&lt;/assertion=
&gt;</P>
<P>&lt;/thread&gt;</P></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Michael Kass=20
  [mailto:michael.kass@nist.gov]<BR><B>Sent:</B> Saturday, June 12, =
2004 2:37=20
  PM<BR><B>To:</B> Jacques Durand; ebXML IIC - main list (E-mail)=20
  (E-mail)<BR><B>Cc:</B> tsakach@certivo.net<BR><B>Subject:</B> RE: =
[ebxml-iic]=20
  minutes, and next call - follow up comments<BR><BR></FONT></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DTahoma =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Jacques=20
  Durand [mailto:JDurand@us.fujitsu.com]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Saturday, June 12, 2004 =
3:07=20
  PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> 'Michael =
Kass';=20
  Jacques Durand; ebXML IIC - main list (E-mail) (E-mail)<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> =
tsakach@certivo.net<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ebxml-iic] =
minutes, and=20
  next call - follow up comments</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Mike:</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">I see=20
  your point. Agree that the inclusion of the payload(s) might be best=20
  supported</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">by a=20
  separate SetPayload operation in the script, that may map to =
different APIs=20
  specific to message packaging and protocols,</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">and=20
  which will do what it takes to properly insert paylaods in the =
message=20
  envelope.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">(so the=20
  binding of SetPayload to the proper message packaging, e.g. ebXML, is =
a=20
  configuration/implementation issue).</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">I think=20
  however that we are facing two conflicting Test Driver requirements, =
for=20
  building messages,</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">in=20
  addition to the requirement of accommodating several messaging =
formats (ebXML,=20
  AS2...)&nbsp;:</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Req 1:=20
  we need a lot of insight and fine-grain control in building a message =

  envelope, </SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">as we=20
  need to create various errors and singularities. This means bypassing =
the=20
  available messaging APIs .</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Req 2:=20
  we need to provide a convenient, high-level way to build a message, =
for test=20
  case writers.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">This=20
  means basically leveraging available APIs, and just defining their =
input, like=20
  an application would do.</SPAN></FONT><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; =
mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">[MIKE2]=20
  - Not necessarily.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>I =
can define a=20
  "high level" XML &lt;MessageDeclaration&gt; , then &lt;Mutate&gt; it =
using=20
  XSLT into a proper<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">message=20
  envelope, without the use of any API.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
  </SPAN>(For example, a SOAP envelope containing ebXML content).<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </SPAN>We are doing that=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">with=20
  the NIST implementation, without the use of a SOAP or ebXML Message=20
  API.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;(although we=20
  even need to abstract these APIs, and just "declare" input=20
  material).</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; =
mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">[MIKE2]=20
  - We do that now.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>Actually,=20
  anyone can "declare" ( via the &lt;MessageDeclaration&gt; content ) =
their=20
  envelope any way they want.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">The=20
  corresponding &lt;Mutator&gt; XSL Stylesheet then interprets that=20
  &lt;MessageDeclaration&gt; content and generates the message=20
  envelope.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">So a=20
  &lt;MessageDeclaration&gt; "could" be just name/value pairs.. and the =

  &lt;Mutator&gt; XSL stylesheet would interpret them and construct=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">An=20
  ebXML message inside a SOAP =
envelope.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">That=20
  makes it impossible to manipulate the packaging of the=20
  messages.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; =
mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">So we=20
  might have to support two ways to build a message:</SPAN></FONT><FONT =

  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">(A) the=20
  "intrusive" way, that we do today, where we can manipulate fairly =
well the=20
  MIME content (e.g. to create errors),</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">but use=20
  high-level payload setting operations, as we do =
today.</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; =
mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">[MIKE2]=20
  - I'm not sure what you mean by "high level payload setting =
operations".=20
  Anyone who writes a Test Driver likely interprets=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;SetPayload&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
</SPAN>&lt;Content-Id&gt;cid:PurchaseOrder&lt;/Content-Id&gt;<o:p></o:p>=
</SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;/SetPayload&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  </SPAN>to be a call to the MIME "setContentId" method for that MIME=20
  container.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">(B) the=20
  "orthodox" way, where we assume that a full messaging API for =
building the=20
  message envelope</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">is=20
  available for a specific transport/packaging. This way is practical =
when we=20
  just want to generate regular messages</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">teh way=20
  an application would do.</SPAN></FONT><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; =
mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">[MIKE2]=20
  - Actually, we can generate "erroneous" messages using a MIME API as =
well=20
  (supplying erroneous MIME header =
content).<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">The test=20
  case script would just provide the "parameter" =
input</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">that=20
  will be interpreted by a sequence of calls to this API (of course the =
API is=20
  out of scope).</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">So in=20
  this option, we would just describe in the input parameter items in =
the most=20
  neutral way, say a flat (XML) list of</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">name -=20
  value pairs that an interpretor (say for ebXML) would now how to =
interpret to=20
  generate the proper message,</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">like any=20
  application code would do. (even the "names" would be specific to a =
message=20
  format, say ebXML,</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">and not=20
  necessarily the same as the corresponding envelope elements). =
Defaults=20
  parameter values can be specified apart.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Payload=20
  material to be used by the interpretor, would either be directly =
assigned as=20
  values for </SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">the=20
  appropriate parameter, or just referenced. They may result from =
additional=20
  specified</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">mutations=20
  (Mutator).</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">That=20
  could be somthing like:</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&lt;</SPAN></FONT><SPAN=20
  class=3DEmailStyle17><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">MessageDeclaration&gt;</SPAN></FONT></SPAN><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;MessageHeader&gt;</SPAN></FONT></SPAN><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">...</SPAN></FONT></SPAN><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;parameter=20
  name=3D"FromPartyId"&gt;ACME&lt;</SPAN></FONT></SPAN><FONT =
face=3DArial color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">parameter&gt;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;parameter=20
  name=3D"ToPartyId2"&gt;NIST&lt;</SPAN></FONT></SPAN><FONT =
face=3DArial color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">parameter&gt;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;parameter=20
  name=3D"COnversationId"&gt;123&lt;</SPAN></FONT></SPAN><FONT =
face=3DArial=20
  color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">parameter&gt;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">...</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">&lt;/MessageHeader&gt;</SPAN></FONT><SPAN=20
  class=3DEmailStyle19><FONT face=3DArial color=3D#003300 =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;MessagePayloads&gt;</SPAN></FONT></SPAN><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">...</SPAN></FONT></SPAN><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;payload=20
  id=3D"PurchaseOrder1" &gt; </SPAN></FONT></SPAN><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; =
</SPAN>&lt;value&gt;(RosettaNet=20
  purchase order) &lt;value&gt;</SPAN></FONT></SPAN><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;/payload=20
  &gt;</SPAN></FONT></SPAN><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt">&lt;payload=20
  id=3D"PurchaseOrder2" &gt; </SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT 
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; =
</SPAN>&lt;value&gt;(RosettaNet=20
  purchase order) &lt;value&gt;</SPAN></FONT></SPAN><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;=20
  </SPAN>&lt;mutator&gt;...&lt;/mutator&gt;</SPAN></FONT></SPAN><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;/payload=20
  &gt; </SPAN></FONT></SPAN><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;payload=20
  id=3D"BusinessAck"<SPAN style=3D"mso-spacerun: yes">&nbsp;=20
  </SPAN>fileURI=3D"BusinessAck.xml" /&gt;<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
  </SPAN></SPAN></FONT></SPAN><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">...</SPAN></FONT></SPAN><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;./MessagePayloads&gt;</SPAN></FONT></SPAN><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&lt;/</SPAN></FONT><SPAN=20
  class=3DEmailStyle17><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">MessageDeclaration&gt;</SPAN></FONT></SPAN><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">So for=20
  an ebXML binding, we just have to define the list of parameter names =
for=20
  ebXML.</SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">From=20
  specification viewpoint, that is not hard to =
support...</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Opinion?</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; =
mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">[MIKE2]<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </SPAN>- The use of &lt;parameter =
name=3D=20
  ""<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>&gt;&lt;/Parameter&gt; is=20
  fine.<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN>The =
&lt;Mutator&gt;=20
  XSLT stylesheet would interpret that, and generate an appropriate =
ebXML=20
  &lt;MessageHeader&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">XSLT=20
  however, is NOT capable of constructing MIME envelopes and their =
content.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </SPAN>That is best left to an =
API, so=20
  placing:<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;payload&gt;&lt;/payload&gt;=20
  inside of a &lt;MessageDeclaration&gt; is problematic.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </SPAN>It is best left "outside" =
of=20
  &lt;MessageDeclaration&gt;.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;=20
  </SPAN>Perhaps a way to make it clearer is to change=20
  the<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">name=20
  of &lt;MessageDeclaration&gt; to =
&lt;MessageEnvelopeDeclaration&gt;.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </SPAN>XML message envelope =
declarations are=20
  easily manipulated via XSLT. MIME (or other) payloads are not.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </SPAN>We "could"=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">put=20
  &lt;payload&gt; elements inside of &lt;MessageDeclaration&gt; .. but =
it just=20
  means that we must ignore them during XSLT processing, then reparse=20
  &lt;MessageDeclaration&gt; again so =
that<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">we can=20
  do "API-level" manipulation of attachments, based upon the =
&lt;payload&gt;=20
  element content.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Why =
not keep=20
  payload processing separate from message envelope processing?=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3D#003300=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Comments?<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Jacques</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 0.5in; MARGIN-RIGHT: 0in; =
mso-margin-top-alt: 0in"><FONT=20
  face=3DTahoma color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: =
Tahoma"><BR></SPAN></FONT><FONT=20
  face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Michael=20
  Kass [mailto:michael.kass@nist.gov]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, June 08, 2004 =
2:59=20
  PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Jacques =
Durand; ebXML=20
  IIC - main list (E-mail) (E-mail)<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> =
tsakach@certivo.net<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ebxml-iic] =
minutes, and=20
  next call - follow up comments</SPAN></FONT><FONT color=3Dblack><SPAN =

  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><SPAN =
class=3DEmailStyle18><FONT=20
  face=3DArial color=3D#993366 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Jacques,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><SPAN =
class=3DEmailStyle18><FONT=20
  face=3DArial color=3D#993366 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><SPAN =
class=3DEmailStyle18><FONT=20
  face=3DArial color=3D#993366 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><SPAN =
class=3DEmailStyle18><FONT=20
  face=3DArial color=3D#993366 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </SPAN>One more thing =
that I=20
  think makes combining &lt;SetPayload&gt; into the =
&lt;MessageDeclaration&gt;=20
  is that, because an XSLT processor can only output one stream (and =
can only=20
  use one stylesheet at a time I believe).. multiple Payloads cannot be =
mutated=20
  (each with their own &lt;Mutator&gt; stylesheet) and attached to the =
outgoing=20
  message.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>So combining =
multiple=20
  &lt;SetPayload&gt; operations (or even one) inside of a=20
  &lt;MessageDeclaration&gt; will not work, and I would think any =
workaround=20
  would be inefficient.<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
  </SPAN>Comments from =
implementers?<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><SPAN =
class=3DEmailStyle18><FONT=20
  face=3DArial color=3D#993366 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><SPAN =
class=3DEmailStyle18><FONT=20
  face=3DArial color=3D#993366 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Mike<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><SPAN =
class=3DEmailStyle18><FONT=20
  face=3DArial color=3D#993366 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1in"><SPAN =
class=3DEmailStyle18><FONT=20
  face=3DArial color=3D#993366 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><FONT face=3DTahoma =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Michael=20
  Kass [mailto:michael.kass@nist.gov]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, June 08, 2004 =
5:42=20
  PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Jacques =
Durand; ebXML=20
  IIC - main list (E-mail) (E-mail)<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ebxml-iic] =
minutes, and=20
  next call - follow up comments</SPAN></FONT><FONT color=3Dblack><SPAN =

  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Jacques=20
  and all,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </SPAN>Here's my comments from =
yesterdays'=20
  minutes.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Mike<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">3.=20
  TestFramework 1.1 Follow-up on latest=20
  discussions:<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">-=20
  Comments on Use Case #1:<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>why=20
  still SetPayload() used? Cant we manipulate payload=20
  directly<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">via=20
  the XML representation of the entire message, as we did for =
GetPayload()?=20
  Mike: yes <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">[MIKE]=20
  -<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>I say "yes" with=20
  reservations:<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>The =
current XML=20
  (using &lt;SetPayload&gt; ) separates message=20
  envelope<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">construction=20
  from payload construction and inclusion.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
  </SPAN>It really requires no more XML code, and allows any type=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">of=20
  payload (GIF image, executable code, XML file, EDI file) to be =
attached,=20
  agnostic of the messaging protocol =
being<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">used.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </SPAN>(if we eliminate the =
"content-ID" and=20
  "content-Location" attributes, and simply substitute=20
  "id".<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">[MIKE]=20
  - Combining &lt;SetPayload&gt; into the &lt;MessageDeclaration&gt; =
makes=20
  sense, however it puts a burden on an XSLT processor, that cannot =
process=20
  non-xml content, cannot generate multiple output streams ( i.e. =
multiple=20
  payloads ), and cannot interface with the messaging API.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </SPAN>XSLT is a text processor =
only.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </SPAN>Trying to make it perform =
attachment=20
  construction (I believe) is beyond the scope of what was intended =
when Drake=20
  Certivo suggested using XSLT as a mutator to message envelope and =
payloads.=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">[MIKE]=20
  - It "can" be done, but that means a "2 pass" parse of the=20
  &lt;MessageDeclaration&gt;. Once to construct the message envelope =
(via XSLT),=20
  and a second pass to interpret the transport and messaging envelope=20
  declaration, as well as to interpret the &lt;SetPayload&gt; =
instruction, find=20
  the appropriate attachment ( via URI ), and bind the attachment to =
the message=20
  ( apriori, knowing the transport and messaging binding ) This is =
defined in=20
  the &lt;ConfigurationGroup&gt; with the &lt;Transport&gt; and =
&lt;Envelope&gt;=20
  configuration parameters.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Comments?<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">In any=20
  event, here is what a "merged" &lt;MessageDeclaration&gt; might look=20
  like:<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;MessageDeclaration&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;mime:MessageContainer&gt;<o:p></o:p></SPAN></FONT></SPAN></P=
>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;soap:Envelope&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;soap:Header&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;eb:MessageHeader&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;/soap:Header&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;soap:Body&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;eb:Manifest&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;/soap:Body&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;/soap:Envelope&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;/mime:MessageContainer&gt;<o:p></o:p></SPAN></FONT></SPAN></=
P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;SetPayload=20
  id=3D"PORequest" &gt;<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>(attachment=20
  of an "inlined" XML document)<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;PurchaseOrderRequest=20
  xmlns=3D"xxx"&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">...<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;/PurchaseOrderRequest&gt;<o:p></o:p></SPAN></FONT></SPAN></P=
>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;SetPayload=20
  id=3D"BusinessAck"<SPAN style=3D"mso-spacerun: yes">&nbsp;=20
  </SPAN>fileURI=3D"BusinessAck.xml"&gt;<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
  </SPAN>(attachmen of an external =
file)<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;/SetPayload&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;/MessageDeclaration&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.75in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Advantage:=20
  knowledge on the message envelope (MIME here) does not have to be =
hard coded=20
  in a<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Test=20
  Driver operation.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">[MIKE]=20
  - That is true.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>Placing=20
  &lt;SetPayload&gt; inside of the &lt;MessageDeclaration&gt; instead =
of=20
  external to it has no influence on whether the Test Driver is =
agnostic to MIME=20
  or not.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Removing the=20
  mime:Content-ID and mime:Content-Location attributes, combined with =
providing=20
  a &lt;ConfigurationGroup&gt; element of =
<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;Transport&gt;HTTP1.1&lt;/Transport&gt;<o:p></o:p></SPAN></FO=
NT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>or <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;Transport&gt;SMTP&lt;/Transport&gt;<o:p></o:p></SPAN></FONT>=
</SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;</SPAN>or=20
  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;Transport&gt;FTP&lt;/Transport&gt;<o:p></o:p></SPAN></FONT><=
/SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>with<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;Envelope&gt;SOAP1.2&lt;/Envelope&gt;<o:p></o:p></SPAN></FONT=
></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>or <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;Envelope&gt;ebXML2.0&lt;/Envelope&gt;<o:p></o:p></SPAN></FON=
T></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>or<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;Envelope&gt;none&lt;/Envelope&gt;<o:p></o:p></SPAN></FONT></=
SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">....<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </SPAN>should provide the Test =
Driver with=20
  the knowledge it needs to construct a payload and attach it =
accordingly, given=20
  a generic XML declaration such as =
<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&lt;SetPayload=20
  id=3D"abc" fileURI=3D"def"/&gt;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;</SPAN>Instead, we only have to =
define how the=20
  canonical XML representation of<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">any 
  message, binds to a particular envelope (MIME or other) and also=20
  transport.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">[MIKE]=20
  - We've done that with MIME and SOAP declarations for ebMS testing, =
although=20
  that requires the Test Driver to <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 2in; TEXT-INDENT: -0.25in; tab-stops: list =
1.0in"><SPAN=20
  class=3DEmailStyle17><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">1)</SPAN></FONT></SPAN><SPAN=20
  class=3DEmailStyle17><FONT color=3Dnavy size=3D1><SPAN=20
  style=3D"FONT-SIZE: 7pt; mso-ascii-font-family: 'Times New Roman'; =
mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times =
New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN></FONT></SPAN><SPAN class=3DEmailStyle17><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">parse=20
  the XML &lt;MessageDeclaration&gt; and construct the MIME parts, then =

  <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.75in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">2)<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN>again parse the=20
  &lt;MessageDeclaration&gt; with an XSLT processor to mutate the=20
  &lt;MessageDeclaration&gt; and generate the proper SOAP envelope and =
ebXML=20
  content.<SPAN style=3D"mso-spacerun: yes">&nbsp;=20
  </SPAN><o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.75in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.75in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">That=20
  means, if anyone wants to create an FTP test suite, the must define a =

  canonical XML representation of the FTP envelope and transport =
declaration,=20
  and submit it as a schema to the IIC, so that a standard XML test =
suite can be=20
  generated for that particular protocol.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN>Any IIC compliant =
Test Driver=20
  MUST be able to interpret that and mutate and generate the =
appropriate message=20
  envelope and payloads based upon that=20
  schema.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 2in; TEXT-INDENT: -0.25in; tab-stops: list =
1.0in"><SPAN=20
  class=3DEmailStyle17><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times =
New Roman'; mso-bidi-font-family: 'Times New =
Roman'">-</SPAN></FONT></SPAN><SPAN=20
  class=3DEmailStyle17><FONT color=3Dnavy size=3D1><SPAN=20
  style=3D"FONT-SIZE: 7pt; mso-ascii-font-family: 'Times New Roman'; =
mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times =
New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN></FONT></SPAN><SPAN class=3DEmailStyle17><FONT face=3DArial =
color=3Dnavy=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">that=20
  will keep us independent from a particular attachment representation =
(SwA, or=20
  other).<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.75in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.75in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">[MIKE]=20
  - As long as we define the underlying bindings between our XML =
representation=20
  and the particular messaging protocol, and provide =
&lt;ConfigurationGroup&gt;=20
  parameters that list those protocols as enumerated types ..=20
  yes..<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.75in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">-=20
  Pete: that amounts to defining extensibility points. We can handle =
future=20
  envelope formats<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">by=20
  just adding bindings / env types. Instead of having to redefine the =
semantics=20
  of SetPayload plus<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">having=20
  to define the binding anyway (as replacement of=20
  GetPayload).<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">-=20
  Monica: current small changes in BPSS will not mandate changes in use =
cases.=20
  WSDL support may<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">need=20
  be considered in new use cases. Multi-party collab will also define=20
  "segments", which in turn<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">define=20
  some context visibility. Can we still define these scopes of=20
  visibility?<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">-=20
  Monica will review current use Cases, and check if (1) they cover =
enough of=20
  BPSS reqs, (2) check<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">if=20
  there is any need for "loops" (e.g. retries, and while-do-=20
  )<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">-=20
  removal of Test Step concept: as long as threads can compose as well, =
is=20
  OK.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">-=20
  Assertion op is loosing its context (FilterResult). But we can assign =

  FilterResults to parameters,<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">so we=20
  can then reference them in Assertions. Several of them may need be =
referenced=20
  anyway, not just<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">the=20
  latest produced.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">[MIKE]=20
  - This is true.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 1.5in"><SPAN =
class=3DEmailStyle17><FONT=20
  face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 2in"><FONT face=3DTahoma =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Jacques=20
  Durand [mailto:JDurand@us.fujitsu.com]<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, June 07, 2004 =
9:03=20
  PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> ebXML IIC - =
main list=20
  (E-mail) (E-mail)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B>=20
  [ebxml-iic] minutes, and next call</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 2in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 2in"><FONT face=3D"Times =
New Roman"=20
  color=3Dblack size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: black">&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P style=3D"MARGIN-LEFT: 2in"><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">1. =
Minutes attached,=20
  confirming the approval of Mike as secretary:=20
  congratulations!</SPAN></FONT><FONT color=3Dblack><SPAN =
style=3D"COLOR: black">=20
  </SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P style=3D"MARGIN-LEFT: 2in"><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">2. Next=20
  call:</SPAN></FONT><FONT color=3Dblack><SPAN style=3D"COLOR: black">=20
  <BR></SPAN></FONT><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">Time: Monday=20
  June 14, 2004, 2pm PT </SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black"><BR></SPAN></FONT><FONT face=3D"Courier New" =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">Host:=20
  Fujitsu </SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black"><BR></SPAN></FONT><FONT face=3D"Courier New" =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">Toll only :=20
  1-512-225-3050 </SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black"><BR></SPAN></FONT><FONT face=3D"Courier New" =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">Participant=20
  code: 716071 </SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P style=3D"MARGIN-LEFT: 2in"><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Agenda =
will follow,=20
  mostly a&nbsp; follow-up on previous one.</SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black"> </SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P style=3D"MARGIN-LEFT: 2in"><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><FONT=20
  color=3Dblack><SPAN style=3D"COLOR: black"> </SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
  <P style=3D"MARGIN-LEFT: 2in"><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">jacques</SPAN></FONT><FONT=20
  color=3Dblack><SPAN style=3D"COLOR: black"> <BR></SPAN></FONT><FONT =
face=3DArial=20
  color=3Dblack size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&lt;&lt;IIC_June_07_04_minutes.txt&gt;&gt;=20
  </SPAN></FONT><FONT color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTM=
L>

------_=_NextPart_001_01C45196.18B2C5D0--

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]