...
| Page properties | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
|
Communication
The eDelivery team is opening a Public Consultation on a new Draft Specification public consultation on the updated draft specification of the eDelivery BDXL profile 2.0, available here. The proposed specification was designed to work together with the Draft Specification new draft specifications of the updated eDelivery AS4 profile 2.0 and the updated , eDelivery SMP profile 2.0 . These profiles have been updated based after an initial public consultation, and they are now open for a second and eDelivery ebCore Party Id profile 2.0, all equally open for public consultation.
In direct response to feedback received during the initial consultation process concerning the eDelivery AS4 and SMP 2.0 profiles, the eDelivery team introduced significant updates to also upgraded the eDelivery BDXL profile , now designated as BDXL to version 2.0 draft. These enhancements directly address stakeholder concerns and suggestions to use to support using different service field values for the in U-NAPTR records , proposing referring to OASIS SMP 1.0 and OASIS SMP 2.0 documents. The new draft proposes the use of the value “Meta:SMP2” for publishing links to OASIS SMP 2.0 documents. Considering that multiple DNS records may need to be published during the network transition from SMP 1.0 to SMP 2.0, the network can decide to refrain from adding the duplicate “Meta:SMP2” records and use the “Meta:SMP” record for both SMP 1.0 and SMP 2.0. This approach provides for a more canonical profiling of the standards without preventing practical operational alternatives where needed. In addition, the new draft now mentions that separate ebCore Party Id Type and identifier value must be concatenated into an ebCore Party Identifier for use with BDXL.
Please post your comments on this page or send them to EC-EDELIVERY-SUPPORT@ec.europa.eu with with [eDelivery BDXL profile version 2.0] in the title of the email.
...