Objective

 XML business document headers and bodies, message protocol headers, X.509 certificates and service metadata registries use formal identifiers as references to parties. Such references typically consist of an identifier value within a particular identifier scheme. The scheme identifier may be prefixed to the identifier, or used separately as a value for a type or scheme attribute. The e-SENS Addressing ABB provides a standard notation for party identifiers and party identifier types that allows existing identification schemes to be reused. The related ABB Specification specifies a URN-based notation for party identifiers based on the ISO 6523 and OASIS ebCore Party ID Type standards. The ABB leverages existing party identification schemes and registries in use in Member States or internationally.

Version1.5

Interoperability

Level

Generic Requirements

The requirements for the Addressing of Entities ABB were first identified in D6.1, based on input from CC6.1 experts, experience from previous LSPs, and initial input from WP5 domains.

For D6.2 and D6.3, the updated WP5 domain pilot plans have been reviewed and the following list of requirements is found to be still valid.

Requirement
ID

Requirement description

Source

R-AddEnt-B1

Ability to identify private and public sector legal entities in Europe and internationally in a standardized and platform independent way

R5.1-UC1-11,

R5.1-UC1-16,

R5.1-UC4-4,

R5.1-UC4-6,

R5.2-UC1-7,

R5.3-UC1-4,

R5.3-UC4-4,

R5.4-UC1-16,

R5.4-UC2-16

R-AddEnt-T1

Ability to support existing (standardized) identification schemes and scheme registries

R5.1-UC4-2

R-AddEnt-T2

Ability to encode sending and receiving end entity identifiers consistently and unambiguously, uniquely, independent from business process or payload

R5.1-UC1-11,

R5.1-UC4-4,

R5.1-UC4-6,

R5.2-UC1-7,

R5.3-UC1-4,

R5.3-UC4-4,

R5.4-UC1-16,

R5.4-UC2-16

R-AddEnt-T3

Ability to encode sending and receiving end entity identifiers in a standardized and machine-process able format

 

R-AddEnt-T4

Decoupled from transport protocol or discovery

 

Provided Services

Provided ServicesPurposeOutcome
Identity Resolution

Service Location ABB and Capability Lookup ABB use the Identity Resolution service for identifying sender and receiving parties uniquely. There are two types of identity in eSENS;

  1. Identifier of an end-entity which stands in C1 or C4,
  2. Identifier of a delivery agent which stands in C2 or C3.

Respectively;

  1. The service returns the unique identifier of the end-entity.
  2. The service returns the unique identifier of the delivery agent (sending agent or receiving agent).

 

 

Application View

Figure 1. Service realization view for Addressing of End-Entities ABB.


Information View

Figure 2. Information structure view for Addressing of End-Entities ABB.


ABB Capability Realization

ABB SpecificationChoice CriteriaSustainability Assessment
PR - ebCore Party IDDecision Log - Addressing of EntitiesCompleted

Contributors

Name

Surname

Organisation

Country

Iva

Milutinovic

Ministry of Justice, North Rhine Westphalia

Germany

Carmen

Rotuna

ICI – National Institute for Research and Development in Informatics

Romania

Pim

Van der Eijk

Ministry of Justice, North Rhine Westphalia

Germany

Melis Ozgur

Cetinkaya Demir

TUBITAK

Turkey

Muhammet

Yildiz

TUBITAK

Turkey

 

 

History 

 

Version

Date

Changes made

Modified by

0.1

30.04.2014

(part of e-Delivery chapter with transport)

Iva Milutinovic

0.2

11.05.2014

(part of e-Delivery chapter with transport)

Carmen Rotuna,

Pim van der Eijk

0.3

13.05.2014

(part of e-Delivery chapter with transport)

Carmen Rotuna,

Pim van der Eijk

0.31

19.06.2014

(part of e-Delivery chapter with transport)

Carmen Rotuna

0.4

16.07.2014

Requirements are updated.

Archimate views are created and added.

Melis Ozgur Cetinkaya Demir, Muhammet Yildiz

0.5

21.07.2014

  • Adapted to ABB template:
  • Addressing separated from transport.

Pim van der Eijk

0.6

23.07.2014

Minor editorial updates

Pim van der Eijk

0.7

04.09.2014

Minor editorial updates

Muhammet Yildiz,

Melis Ozgur Cetinkaya Demir,

1.011.02.2015D6.2 Comments Processed

Pim van der Eijk

Iva Milutinovic

 

1.126.03.2015Structured according to the eSENS BB Descriptions.Melis Ozgur Cetinkaya Demir
1.231.03.2015

Generated the contents of the sections "Provided Services",

"Related ABBs" and "ABB Capability Realization".

Melis Ozgur Cetinkaya Demir
1.303.04.2015Information View ArchiMate updated.Melis Ozgur Cetinkaya Demir
1.408.04.2015

Editorial fixes

Changed status to Transition

Changed description to be technology-neutral.

Added WP5 to requirements sources

Removed Status as per email KVP.

Removed sustainability assessment, as that applies to the
ABB Specification.

Pim van der Eijk
1.522.04.2015

The Message Exchange requirements are matched to the domain specific requirements of

  • WP5.1
  • WP5.2
  • WP5.3
  • WP5.4

Editorial:

  • Fixed link to related ABBs and ABB Capabiltiy realization
  • Bumped version
Melis Ozgur Cetinkaya Demir
  • No labels