5.1.1.2

Data sharing: Data sharing request - Request data transfer

Test: Coverage test: for each data plane available, test a minimal data sharing and identify possible inconsistencies with the original data product protocol endpoint (e.g., during data querying, we aren’t allowed to send http headers to the data source).

note

The description of Test 5.1.1.2 was extracted from this page in the GitHub repository.
This file was last modified at 2026-06-24 15:37:50 UTC.

Information

• Phase 1

• Minimal? Yes

• Related KPIs:

  • Functional suitability: The system supports multiple protocols and the ability to perform queries against the data products endpoint when the endpoint offers that capability.

• Evaluation Criteria:

N/A

Results

Fiware

note

The results for Test 5.1.1.2 for Fiware were extracted from this page in the GitHub repository.
This file was last modified at 2026-06-24 15:37:50 UTC.

Environment

Tested quality metric and method

The respective issue #258 additionally mentions the following protocols to be tested: GTFS GTFS-RT DATEX-II DATX II Light GBFS WMS/WFS

Comparative criteria (checklists, ...)

Expected output

Regarding the protocols mentioned in #258, all these protocols describe the data format. Eg. GTFS provides data in a zip file and the file contains multiple text files in a comma separated style. Or e.g. GBFS specifies the data format to be Json.

None of the protocol specifies a data exchange protocol other then HTTP GET requests. Since data sources can be naturally provided with an HTTP Proxy like APISIX, the Fiware connector supports all of these formats.

Results

Assessment

Measured results

Characteristic	Score
Functional completeness	4
Functional correctness	4
Functional appropriateness	4
Total	4

Functional Suitability Quality Metric Score: 4

Notes

protoEMDS Final Stack (EDC-based)

note

The results for Test 5.1.1.2 for protoEMDS Final Stack (EDC-based) were extracted from this page in the GitHub repository.
This file was last modified at 2026-06-24 15:37:50 UTC.

Environment

This section identifies the technical context in which the protoEMDS Final Stack assessment is performed.

Field	Value
Assessment context	Integration phase assessment of the EMDS final technical infrastructure
Result perspective	protoemds_final_stack
Stack under assessment	protoEMDS Final Stack (EDC-based)
KPI1 area	Minimal data transfer
Existing test ID	5.1.1.2
Level	UC + Technical
ISO/IEC 25010 mapping	Functional suitability, Compatibility, Reliability
Owner (tentative)	Casper (imec)
Reviewer	Carlos
Deployment model assessed	TBD
Target environment	TBD
EDC version / release	TBD
Connector deployment reference	TBD
Assessment evidence	TBD

The assessment should be completed using the deployment model for which evidence is realistically available. It is not mandatory to execute the same test in both CaaS and on-premise environments.

If only one deployment model is assessed, the other one should be marked as Not assessed.

Tested quality metric and method

This result reuses the existing stack-agnostic test definition in test.md and adds an protoEMDS Final Stack integration-assessment perspective.

It does not replace the historical stack-specific result files, such as result_edc_vc.md or result_fiware.md.

The quality metric, expected output and comparative criteria remain those defined by the original test. This result file should only capture the evidence and assessment outcome for the selected protoEMDS Final Stack deployment.

Test-specific assessment scope

Coverage test: for each data plane available, test a minimal data sharing and identify possible inconsistencies with the original data product protocol endpoint (e.g., during data querying, we aren’t allowed to send http headers to the data source).

Expected Output

Evaluate the support of a minimal data sharing for the following data formats

• GTFS - Public dataset with direct download via HTTPS
• GTFS-RT - Public dataset via APIs
• DATEX-II - Public dataset via APIs
• DATX II Light - No available datasets for this data format, tests are skipped
• GBFS - Public dataset via APIs
• WMS/WFS - Public dataset via APIs

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

Results

Assessment

Pending.

The assessment should be completed once consolidated technical evidence is available for the protoEMDS Final Stack deployment.

The result should clearly indicate which deployment model was assessed. It is acceptable to assess only one deployment model if evidence for the other deployment model is not available.

Deployment model assessed

Deployment model	Status	Evidence	Consolidated assessment
CaaS / IONOS-managed deployment	TBD	TBD	Complete this row only if evidence is collected from the IONOS-managed deployment. Otherwise mark as Not assessed.
On-premise deployment	TBD	TBD	Complete this row only if evidence is collected from an on-premise or locally managed deployment. Otherwise mark as Not assessed.

Measured results

Test	Functional Completeness	Functional Correctness	Functional Appropriateness	Explanation
GTFS	TBD	TBD	TBD	TBD
GTFS-RT	TBD	TBD	TBD	TBD
DATEX-II	TBD	TBD	TBD	TBD
GBFS	TBD	TBD	TBD	TBD
WMS/WFS	TBD	TBD	TBD	TBD
Private key	TBD	TBD	TBD	TBD
Overall	TBD	TBD	TBD	TBD

Functional Suitability Quality Metric Score: TBD

Notes

This result introduces an protoEMDS Final Stack perspective for the existing test 5.1.1.2 under the KPI1 area Minimal data transfer.

This result should not be interpreted as part of the original Phase 1 / Phase 2 stack-comparison campaign. It is intended as an integration phase assessment of the current EMDS final technical infrastructure.

The assessment should be completed using consolidated technical evidence, such as endpoint responses, logs, screenshots, Postman/curl executions, GitHub issues, pull requests, repository references, deployment status or confirmation from the relevant component owner.

This result file was generated from the local test.md and, where available, the local result_edc_vc.md structure. EDC+VC-specific evidence, values and scores were intentionally not reused.

EDC+VC

note

The results for Test 5.1.1.2 for EDC+VC were extracted from this page in the GitHub repository.
This file was last modified at 2026-06-24 15:37:50 UTC.

Environment

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

Expected output

Evaluate the support of a minimal data sharing for the following data formats

• GTFS - Public dataset with direct download via HTTPS
• GTFS-RT - Public dataset via APIs
• DATEX-II - Public dataset via APIs
• DATX II Light - No available datasets for this data format, tests are skipped
• GBFS - Public dataset via APIs
• WMS/WFS - Public dataset via APIs

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 simple http server is used as destination of the artifact (consumer data plane). The server receives a file and logs its content in the standard output. Note that while most artifacts point to plain text files, GTFS and GTFS-RT use binary files that can't be properly printed in standard output. This is not a limitation of the EDC+VC stack per se, but rather of the sample consumer data plane used in these tests, and thus this did not affect the evaluation score.

Measured results

Test	Functional Completeness	Functional Correctness	Functional Appropriateness	Explanation
GTFS	4	4	4	-
GTFS-RT	3	4	4	Can't perform queries against the data product
DATEX-II	3	4	4	Can't perform queries against the data product
GBFS	3	4	4	Can't perform queries against the data product
WMS/WFS	3	4	4	Can't perform queries against the data product
Private key	1	1	1	Transfer process status is TERMINATED, logs are empty
Overall	(4+3*4+1)/6 = 2.83	(4*5+1)/6 = 3.5	(4*5+1)/6 = 3.5

Overall score calculation: (2.83 + 3.5 + 3.5) / 3 = 3.28

Functional Suitability Quality Metric Score: 3.28