Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The eDelivery team is opening a public consultation on the updated draft specification of the eDelivery SMP profile 2.0, available here. The proposed specification was designed to work together with the updated new draft specification specifications of the eDelivery AS4 profile 2.0, which is equally open for public consultation.The pervious version of the draft profile supports OASIS SMP version 2.0, allowed publishing multiple certificates (signing, encryption, key exchange) for a transport and supports both eDelivery AS4 profiles 1.x and 2.0eDelivery BDXL profile 2.0 and ebCore Party Id profile 2.0, all equally open for public consultation.

The version of the new draft specification is set to 2.0 to illustrate that this is a backwards-incompatible evolution of the profile in that SMP data compatible with profile version 2.0 cannot be consumed by legacy clients. It is noted that the backward incompatibility at the profile level does not preclude implementations of both SMP servers and/or clients from supporting, using different endpoints, both profile versions and/or other metadata protocols. Compared to the previous draft version, this new draft specification underwent significant revisions based on feedback received during the consultation. Apart from adjustments to improve clarity and structure, the new draft has been adapted

The first draft of the eDelivery SMP 2.0 profile included updates to support OASIS SMP version 2.0, to allow publishing multiple certificates (signing, encryption, key exchange) for a transport and to support both eDelivery AS4 profiles 1.x and 2.0. In response to the public review comments on this first draft and further internal analysis, several changes were made in the second draft:

  • The section on eDelivery ebCore Party Identifiers was updated to mandate the use of the schemeID attribute of the ParticipantID element in SMP 2.0 documents and to allow for both the “::” and “:” separators when dealing with OASIS ebCore PartyId Type

...

  • .
  • The use of

...

  • the Process element in ProcessMetadata was profiled to define clear semantics for when it is absent.
  • Improvements to clarity and structure and editorial changes.

To fully address the feedback received, the eDelivery BDXL and eDelivery ebCore Party Id Profiles were also upgraded and are now open for public consultation

The proposed updated draft specification requires changes in

...

.


Please post your comments on this page or send them to EC-EDELIVERY-SUPPORT@ec.europa.eu with  with [Updated eDelivery SMP profile version 2.0] in the title of the email.

...