4.2.1.7
Sharing agreement: Negotiation - Negotiating sharing agreement
Assessment: Verify that the system outputs logs detailing the sharing agreement process. Rank higher if the logs provide business information under a standard format.
The description of Test 4.2.1.7 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? No
-
Related KPIs:
- Security: [Integrity] The system provides observability records of the sharing agreement states (privacy terms of observability are out of scope here).
-
Evaluation Criteria:
N/A
Results
- Fiware
- protoEMDS Final Stack (EDC-based)
- EDC+VC
TODO: This test is not done yet for this testing facility. Last checked at 2026-06-24 15:45:38 UTC.
The results for Test 4.2.1.7 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 | Observability / logging |
| Existing test ID | 4.2.1.7 |
| Level | Technical |
| ISO/IEC 25010 mapping | Reliability, Maintainability |
| Owner (tentative) | Carlos (i2CAT) |
| 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
Verify that the system outputs logs detailing the sharing agreement process. Rank higher if the logs provide business information under a standard format.
Expected Output
The test aims to verify that the system generates logs detailing the sharing agreement process. A higher rank will be given if these logs include business information in a standardized format.
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
| Requirement | Measured KPI | Evidence | Notes |
|---|---|---|---|
Test-specific requirement from test.md | TBD | TBD | Pending protoEMDS Final Stack assessment. |
Functional Suitability Quality Metric: TBD
Notes
This result introduces an protoEMDS Final Stack perspective for the existing test 4.2.1.7 under the KPI1 area Observability / logging.
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.
The results for Test 4.2.1.7 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
- The test leverages the EDC MVD commit 8da0c4e.
- It uses EDC version 0.8.2-SNAPSHOT.
- The test is performed on an Ubuntu environment with IntelliJ.
Tested quality metric and method
The quality metric for this test is based on the criteria outlined in iso27001_kpis_subkpis.xlsx. In Phase 1, the focus is on the Functional Suitability metric. For detailed information, please refer to the Evaluation Criteria section in the test description.
Comparative criteria (checklists, ...)
[TODO] Describe the comparative criteria used for the test / assessment. If possible, align with the criteria used for the same test in the other stack(s).
Expected output
The test aims to verify that the system generates logs detailing the sharing agreement process. A higher rank will be given if these logs include business information in a standardized format.
Results
Assessment
When executing a sharing agreement negotiation within EDC MVD commit 8da0c4e, the connector logs status updates as follows:
In the provider log for ContractNegotiation 1bb59a3e-692a-40d5-b6d4-a8a223f5d0e9, the process is detailed through various stages:
DEBUG 2024-08-19T13:38:27.005955896 DSP: Incoming ContractRequestMessage for class org.eclipse.edc.connector.controlplane.contract.spi.types.negotiation.ContractNegotiation process
DEBUG 2024-08-19T13:38:27.153020832 [PROVIDER] ContractNegotiation 1bb59a3e-692a-40d5-b6d4-a8a223f5d0e9 is now in state REQUESTED.
DEBUG 2024-08-19T13:38:28.088552426 [ProviderContractNegotiationManagerImpl] ContractNegotiation 1bb59a3e-692a-40d5-b6d4-a8a223f5d0e9 is now in state AGREEING
DEBUG 2024-08-19T13:38:28.088734016 ContractNegotiation: ID 1bb59a3e-692a-40d5-b6d4-a8a223f5d0e9. [Provider] send agreement
DEBUG 2024-08-19T13:38:28.99746865 ContractNegotiation: ID 1bb59a3e-692a-40d5-b6d4-a8a223f5d0e9. [Provider] send agreement
DEBUG 2024-08-19T13:38:28.997585967 [ProviderContractNegotiationManagerImpl] ContractNegotiation 1bb59a3e-692a-40d5-b6d4-a8a223f5d0e9 is now in state AGREED
DEBUG 2024-08-19T13:38:30.024040375 DSP: Incoming ContractAgreementVerificationMessage for class org.eclipse.edc.connector.controlplane.contract.spi.types.negotiation.ContractNegotiation process: 1bb59a3e-692a-40d5-b6d4-a8a223f5d0e9
DEBUG 2024-08-19T13:38:30.13703795 [PROVIDER] ContractNegotiation 1bb59a3e-692a-40d5-b6d4-a8a223f5d0e9 is now in state VERIFIED.
DEBUG 2024-08-19T13:38:30.141847687 [ProviderContractNegotiationManagerImpl] ContractNegotiation 1bb59a3e-692a-40d5-b6d4-a8a223f5d0e9 is now in state FINALIZING
DEBUG 2024-08-19T13:38:30.141963485 ContractNegotiation: ID 1bb59a3e-692a-40d5-b6d4-a8a223f5d0e9. [Provider] send finalization
DEBUG 2024-08-19T13:38:30.350142882 ContractNegotiation: ID 1bb59a3e-692a-40d5-b6d4-a8a223f5d0e9. [Provider] send finalization
DEBUG 2024-08-19T13:38:30.35023427 [ProviderContractNegotiationManagerImpl] ContractNegotiation 1bb59a3e-692a-40d5-b6d4-a8a223f5d0e9 is now in state FINALIZED
In the consumer log, the identifier 5204e110-a899-44fa-8199-87f2b7d7b32c corresponds to the consumer side of the negotiation for 1bb59a3e-692a-40d5-b6d4-a8a223f5d0e9 and tracks its progress:
DEBUG 2024-08-19T13:38:26.050906687 [ConsumerContractNegotiationManagerImpl] ContractNegotiation 5204e110-a899-44fa-8199-87f2b7d7b32c is now in state INITIAL
DEBUG 2024-08-19T13:38:26.785097428 [ConsumerContractNegotiationManagerImpl] ContractNegotiation 5204e110-a899-44fa-8199-87f2b7d7b32c is now in state REQUESTING
DEBUG 2024-08-19T13:38:26.855357612 ContractNegotiation: ID 5204e110-a899-44fa-8199-87f2b7d7b32c. [Consumer] send request
DEBUG 2024-08-19T13:38:27.258747111 ContractNegotiation: ID 5204e110-a899-44fa-8199-87f2b7d7b32c. [Consumer] send request
DEBUG 2024-08-19T13:38:27.258883088 [ConsumerContractNegotiationManagerImpl] ContractNegotiation 5204e110-a899-44fa-8199-87f2b7d7b32c is now in state REQUESTED
DEBUG 2024-08-19T13:38:28.190560002 DSP: Incoming ContractAgreementMessage for class org.eclipse.edc.connector.controlplane.contract.spi.types.negotiation.ContractNegotiation process: 5204e110-a899-44fa-8199-87f2b7d7b32c
DEBUG 2024-08-19T13:38:28.824549175 [DEMO] Node filter: skipping node 'did:web:localhost%3A7083' for participant 'did:web:localhost%3A7083'
DEBUG 2024-08-19T13:38:28.985700927 [CONSUMER] ContractNegotiation 5204e110-a899-44fa-8199-87f2b7d7b32c is now in state AGREED.
DEBUG 2024-08-19T13:38:29.972298702 [ConsumerContractNegotiationManagerImpl] ContractNegotiation 5204e110-a899-44fa-8199-87f2b7d7b32c is now in state VERIFYING
DEBUG 2024-08-19T13:38:29.972997128 ContractNegotiation: ID 5204e110-a899-44fa-8199-87f2b7d7b32c. [consumer] send verification
DEBUG 2024-08-19T13:38:30.137937195 ContractNegotiation: ID 5204e110-a899-44fa-8199-87f2b7d7b32c. [consumer] send verification
DEBUG 2024-08-19T13:38:30.138071291 [ConsumerContractNegotiationManagerImpl] ContractNegotiation 5204e110-a899-44fa-8199-87f2b7d7b32c is now in state VERIFIED
DEBUG 2024-08-19T13:38:30.190656705 DSP: Incoming ContractNegotiationEventMessage for class org.eclipse.edc.connector.controlplane.contract.spi.types.negotiation.ContractNegotiation process: 5204e110-a899-44fa-8199-87f2b7d7b32c
DEBUG 2024-08-19T13:38:30.349225751 [CONSUMER] ContractNegotiation 5204e110-a899-44fa-8199-87f2b7d7b32c is now in state FINALIZED.
The logs capture the detailed sequence of the sharing agreement (contract negotiation) process, using a "log4j-style" logging format. This format, while not officially standardized, is a commonly used pattern in software development. The Java library is available at: https://logging.apache.org/log4j/2.x/.
Measured results
As detailed above, EDC provides a comprehensive logging solution that accurately captures the sharing agreement process in a widely adopted format. Based on the criteria outlined in the Evaluation Criteria section of the test description, the test is assigned the following score:
Functional Suitability Quality Metric: 4
Notes
EDC is a pluggable ecosystem primarily targeting Java/Kotlin developers. Some extensions are available on the market for plug-and-play, but for certain specific use cases, developers need to create their own extensions.