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).
The description of Test 5.1.1.2 was extracted from this page in the GitHub repository.
This file was last modified at 2025-06-02 13:59:01 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
- EDC+VC
- Fiware
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 2025-06-02 13:59:01 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
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 2025-06-02 13:59:01 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