← Prev in month ← Prev in thread
Next in thread → Next in month →

Groups - cppa3.xsd uploaded

From
Pim van der Eijk
Date
2017-09-29T14:22:00+00:00
ID
Thread
Groups - cppa3.xsd uploaded
Submitter's message
#21
 -  Incremental documentation improvements.
 -  Generalized extensibility to include toplevel, party info, service bindings and action bindings,
 -  Administrative contact type added
 -  PayloadProfileId element
 -  WebSocket transport added
 -  Matches CPPA3 v0.33 updates, EASEE-gas and ENTSOG portal requirements.

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

 #21
 -  Incremental documentation improvements.
 -  Generalized extensibility to include toplevel, party info, service  bindings and action bindings,
 -  Administrative contact type added
 -  PayloadProfileId element
 -  WebSocket transport added
 -  Matches CPPA3 v0.33 updates, EASEE-gas and ENTSOG portal requirements.

 #20
 -  Typo in request channel ID
 -  changed NMTOKEN to token for some structure.
 -  allow a CPP to have no service specification (a  opt out  CPP)

 #19
 -  Support for Certificate Policy Sets and references to them
 -  Renamed TrustAnchor to TrustAnchorSet,  same for references
 -  ebBP time to perform attribute
 -  New elements *CertificateRequired,  to express that a leaf certificate  is required for CPA formation

 #18
 - added a missing ebBP attribute
 - new optional EncryptionFormat, for protocols that support different  encryption formats.
 - optional version attribute on EncryptionFormat and SignatureFormat
 - Updated S/MIME reference to current 3.2
 - Added element to specify type of party contact
 - Editorial 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-09-29 07:21:29
Revision : 21
← Prev in month ← Prev in thread
Next in thread → Next in month →