For some reason the XML from the Kavi form was stripped. This is
the example again:
<cppa:PayloadProfile id="_YGJ7">
<cppa:PayloadPart maxOccurs="1" requireSignature="true">
<cppa:PartName>businessdocument</cppa:PartName>
<cppa:MIMEContentType>application/xml</cppa:MIMEContentType>
<cppa:Schema namespace="urn:example.org:bd"
location="http://schemas.example.org/bd.xsd"/>
<cppa:Signature>
<cppa:SignatureAlgorithm>http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha256</cppa:SignatureAlgorithm>
<cppa:SigningCertificateRef certId="asigningcert"/>
</cppa:Signature>
</cppa:PayloadPart>
</cppa:PayloadProfile>
On 14-11-16 14:38, Pim van der Eijk
wrote:
Submitter's message
This version of the schema provides a minor enhancement to the
schema to allow specification of payload parts that are signed
and/or encrypted by a business application.
CPPA2 had a similar feature called ApplicationCertificateRef,
which was intended to allow CPPA to be used to exchange keys for
(legacy) applications that sign or validate signatures.
For CPPA3, the same requirement came up in a project where there
is end-to-end signing or encryption of (some) payloads, and for
sharing the certificates.
The above is separate from message level signing and encryption by
e.g. WS-Security.
-- Mr. Pim van der Eijk
Document Name:
cppa3.xsd
Description
Draft CPPA 3 specification and schema.
Including embedded documentation but excluding generated
HTML
documentation.
Download
Latest Revision
Public
Download Link
Submitter:
Mr. Pim van der Eijk
Group: OASIS ebXML Core (ebCore) TC
Folder: Contributions
Date submitted: 2016-11-14 05:37:55
Revision: 7
|