You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Public Consultation

Status

OPEN

Consulted Expert Group / StakeholdereDelivery community
OutcomeComments for input
Launch date

 

Due date

 

Main contact addressEC-EDELIVERY-SUPPORT@EC.EUROPA.EU

Communication:

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 draft specification 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.0.

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 to allow for both the “::” and “:” separators when dealing with OASIS ebCore PartyId Type and recommends the use of second usage in line with OASIS 2.0 standard.

The proposed updated draft specification requires changes in the eDelivery BDXL profile, which is open for public consultation as well. 

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


  • No labels