Subject: FW: Sample cpp.xml for payload signature profile. Many details st illup in the air...
Forgot to post to tp list. See below for info on enclosed sample cpp capability. > -----Original Message----- > From: Moberg, Dale > Sent: Wednesday, November 29, 2000 12:34 PM > To: email@example.com > Subject: Sample cpp.xml for payload signature profile. Many details > still up in the air... > > > Hi > > I am enclosing some sample xml to characterize one capability > within a cpp, where the capability involves message/document level > security packaging (digital signature only) > for the payload. The payload, together with its detached signature, > is wrapped up as a multipart/signed. Then the ebXML header is joined > with the multipart/signed and wrapped up as a > multipart/related following > the conventions of TRP (or really what may become the TRP > conventions for > one security option). > > The xml is supposed to support twin functions: First, to be detailed > enough to "drive a runtime" by providing declarative specifications > of the packaging that is used at the message service layer. Second, > to indicate the crucial interoperability factors present so that > a decision can be made by two potential collaborators that their > capabilities are sufficient to interoperably implement a selected > business process. > > Dale Moberg > > >
eList eXpress LLC