Skip to main content

2.1.1.3

Data product publication: Provision - Data source endpoint provisioning

Assessment: Assess the availability of multiple data planes that support multiple protocols. Refer to D2.1 for an overview of the most used protocols. The higher the coverage, the higher the ranking.

note

The description of Test 2.1.1.3 was extracted from this page in the GitHub repository.
This file was last modified at 2025-06-02 13:59:00 UTC.

Information​

  • Phase 1

  • Minimal? Yes

  • Related KPIs:

    • Functional suitability: Can the provider integrate different data source methods (APIs, data bases, file systems, etc.)

  • Evaluation Criteria:

N/A

Results​

note

The results for Test 2.1.1.3 for EDC+VC were extracted from this page in the GitHub repository.
This file was last modified at 2025-06-02 13:59:00 UTC.

Environment​

EDC Connector v.0.7.1 within a local testbed. The tests are available in this Postman workspace.

Tested quality metric and method​

If an asset can represent a data source X, then data source X can be provisioned.

Expected output​

Evaluate the level of support for the following data formats

Also access through APIs. Access to private APIs is tested using the AMB mobilitat endpoint.

Results​

Assessment​

All the tests are stored under this folder. A single, parameterized call is used for the entire batch of tests. Execute this tests by running the entire folder at once.

Measured results​

The EDC-VC stack fully supports all 6 types of data planes explained in this test. As such, it is evaluated with the highest score in each of the criteria used to evaluate this test as shown in the table below.

CriterionDescriptionScore (0-4)Explanation
Functional CompletenessTechnical requirements cover all the specified tasks and user objectives.4Artifacts can store a URL to any file format. The URL is stored by setting the field dataAddress.baseUrl.
Functional CorrectnessTechnical requirements meet results with the needed degree of precision.4Both publicly-accessible as well as private artifacts are supported. For the latter, different authentication methods are also provided, such as access through API keys which is supported through the attribute privateProperties.privateKey
Functional AppropriatenessTechnical requirements facilitate the accomplishment of specified tasks and objectives.4All artifacts were created easily through a single API call passing the required information.

Overall score calculation: (4 + 4 + 4) / 3 = 4

Functional Suitability Quality Metric Score: 4