Objective

Capability Lookup is a technical service to accommodate a dynamic and flexible interoperability community. A capability lookup can provide metadata about the communication partner’s interoperability capabilities on all levels defined in the European Interoperability Framework (Legal, Organizational, Process, Semantic and Technical interoperability levels). The metadata can be used to dynamically set interoperability parameters and ambitions between the sender and receiver. 


A Capability Lookup service is owned by the communication receiver and it expresses the receiver's interoperability capabilities e.g.: 

  • which business processes the receiver can participate in
  • which eDocuments can be received
  • the security setup
  • the evidence setup
  • the communication protocol setup
  • the location of receiver's gateway 
Version1.6

Interoperability

Level

In the context of setting up an interoperability connection with a Business partner, the sender needs to dynamically resolve the settings e.g. Legal, Organizational, Semantic and Technical capabilities and constraints. The recipient has already stated "Defined" or "Entered" instead of "stated" these in the Capability_LookUp service and by requesting the meta data, the sender can adopt and choose the most optimal settings and capabilities. 

An example would be several ambitions levels for Business Processes e.g.:

  • Exchange of an order
  • Exchange of an order, followed by an order response
  • Exchange of an order, followed by an order response and an invoice

In this case, the sender can choose the ambition level that corresponds to its Business Process capability. 

 

Generic Requirements

The requirements for the Capability Lookup 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-CapLoo-S1

May provide metadata about receivers legal requirements for interoperability

R5.1-UC1-11,

R5.1-UC1-16,

R5.1-UC1-17,

R5.1-UC4-6,

R5.2-UC1-7,

R5.3-UC1-4,

R5.3-UC4-4,

R5.4-UC1-16

R-CapLoo-S2

May provide metadata about receivers organizational requirements for interoperability

R5.1-UC1-11,

R5.1-UC1-16,

R5.1-UC1-17,

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-CapLoo-S3

May provide metadata about which standardized Business Processes (eProcess)
is supported by receiver

R5.1-UC1-11,

R5.1-UC1-16,

R5.1-UC1-17,

R5.1-UC4-6,

R5.2-UC1-7,

R5.3-UC1-4,

R5.3-UC4-4

R-CapLoo-S4

May provide metadata about which standardized Business Documents
(eDocument) is supported by receiver

R5.1-UC1-11,

R5.1-UC1-16,

R5.1-UC1-17,

R5.1-UC4-6,

R5.2-UC1-7,

R5.3-UC1-4,

R5.3-UC4-4

R-CapLoo-S5

May provide metadata about required and/or supported technical settings:

  • Security
  • Evidence e.g. non-repudiation
  • Communication protocol
 

R-CapLoo-T1

May resolve receiver's communication address, based on receiver's other capabilities

R5.1-UC1-11,

R5.1-UC1-17,

R5.1-UC4-6,

R5.2-UC1-7,

R5.3-UC1-4,

R5.3-UC4-4

R-CapLoo-T2

Ability for receiver to change its own capability settings within the agreed interoperability
framework of the specific interoperability community

 

R-CapLoo-T3

Ability for an entity to control the visibility of its metadata

 

R-CapLoo-T4

Ability to verify authenticity and validity of metadata

 

R-CapLoo-T5

Ability to partition metadata information across communities
(with community-specific terms and conditions, governance models etc.)

R5.1-UC1-11,

R5.1-UC1-16,

R5.1-UC1-17,

R5.1-UC4-6,

R5.2-UC1-7,

R5.3-UC1-4,

R5.3-UC4-4

R-CapLoo-T6

Ability to parametrize metadata for separate environments (production, test)

 

 

 

Provided Services

Provided ServicesPurposeOutcome
Capability Resolution

There are two types of access to Capability Resolution Service;

  1. Originator of the message stands in C1 or C4 and uses "Backend Integration" ABB to reach the Capability Resolution Service of Capability Lookup ABB. The service returns the metadata of the end-entity.
  2. Sender agent stands in C2 or C3 and uses Capability Resolution Service of Capability Lookup ABB directly. The service returns the metadata of the recipient agent.

Respectively;

  1. The service returns the metadata of the end-entity.
  2. The service returns the metadata of the recipient agent.

 

 

Application View

Figure 1. Service realization view for Capability Lookup ABB.


Information View

Figure 2. Hierarchical information structure view for Capability Lookup ABB.


ABB Capability Realization

ABB SpecificationChoice CriteriaSustainability Assessment
PR - SMP - 1.6.0Decision Log - Service Location and Capability LookupCompleted

Contributors

 

Name

Surname

Organisation

Country

Iva

Milutinovic

Ministry of Justice, North Rhine Westphalia

Germany

Muhammet

Yildiz

TUBITAK

Turkey

Melis Ozgur

Cetinkaya Demir

TUBITAK

Turkey

Pim

van der Eijk

Ministry of Justice, North Rhine Westphalia

Germany

KlausVilstrup PedersenDIFINorway

 

 

History

Version

Date

Changes made

Modified by

0.2

17.03.2014

Template

Klaus Vilstrup Pedersen

0.3

22.07.2014

Capability Lookup content added 
Archimate modelling integrated.

Iva Milutinovic, 
Melis Ozgur Cetinkaya Demir,

Muhammet Yildiz

0.4

23.07.2014

Minor editorial updates

Pim van der Eijk

0.5

26.08.2014

Additions and changes in structures

Klaus Vilstrup Pedersen

1.012.02.2015D6.2 Comments Processed

Pim van der Eijk

Iva Milutinovic

1.113.03.2015Archimate views Updated WRT D6.2 Reviews

Melis Ozgur Cetinkaya Demir,

Muhammet Yildiz

1.226.03.2015Structured according to the eSENS BB Descriptions.Melis Ozgur Cetinkaya Demir
1.331.03.2015

Generated the contents of the sections "Provided Services",

"Related ABBs" and "ABB Capability Realization".

Melis Ozgur Cetinkaya Demir
1.403.04.2015Application View and Information View ArchiMate updated.Melis Ozgur Cetinkaya Demir
1.508.04.2015

Editorial fix

Removed status as per email KVP.

Removed sustainability assessment, as that applies to the

ABB Specification.

Pim van der Eijk
1.622.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