Groups - cppa3.xsd uploaded

Submitter's message
#17,  minor updates
 - Made ebMS security a channel feature, so it can be reused.
 - Activation and Expiration can be specified at service binding level. This allows different (versions of) services to have different validity intervals.
 - Removed the MinimumStrength element.  This value is not normally separately specifiable, but determined by the algorithm.  For e.g. AES, there are different algorithm URIs for different key lenghts.

--
Mr. Pim van der Eijk
Document Name :  cppa3.xsd
Description
Draft CPPA 3 schema. Including embedded documentation but excluding  generated HTML documentation.

 #17,  minor updates
 - Made ebMS security a channel feature, so it can be reused.
 - Activation and Expiration can be specified at service binding level. This  allows different (versions of) services to have different validity  intervals.
 - Removed the Minimum Strenght element.  This value is not normally  separately specifiable, but determined by the algorithm.  For e.g. AES,  there are different algorithm URIs for different key lenghts.
Download Latest Revision
Public Download Link
Submitter : Mr. Pim van der Eijk
Group : OASIS ebXML Core (ebCore)

TC
Folder : Contributions
Date submitted : 2017-06-08 06:47:06
Revision : 17