B) EDC Policy: Revise the description of how bilateral contracts can be used
C) PCF Request: Review the description and revise it to eliminate misunderstandings and possibly also inconsistencies
(e.g. with regard to synchronous/and or asynchronous operation, currently only asynchronous operation is possible, but the description looks like a synchronous retrieval of the PCF data)
What's the benefit?
A) Create a better understanding of the content.
B) To have an explicit use case for the contracts >> enablement of the users
C) Clear and concise description
What are the Risks/Dependencies ?
A) There are none.
B) Incorrect use of bilateral contracts.
C) Missing functionality.
Detailed explanation
Current implementation
Proposed improvements
Feature Team
Contributor
Multiple contributers from expert group Architecture and Interoparbility
Committer
@stephanbcbauer
User Stories
New members who can not fully understand the content of the PCF Kit.
Acceptance Criteria
A) Include payload description into semantic model
B) Having an understandable explanation, revised by users.
C) Having an understandable explanation, revised by users.
Architectural Relevance
The following items are ensured (answer: yes) after this issue is implemented:
[ ] This feature aligns with our current architectural guidelines
[x] The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
[x] Potential risks or conflicts with existing architecture has been assessed
Justification:(Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)
Additional information
[x] I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)
Explain the topic in 2 sentences
A) PCF DatenModel: Include the payload keys in the PCF DataModel Details table and revise the technical names accordingly. https://eclipse-tractusx.github.io/docs-kits/kits/PCF%20Exchange%20Kit/Adoption%20View#introduction-pcf-data-model
B) EDC Policy: Revise the description of how bilateral contracts can be used
C) PCF Request: Review the description and revise it to eliminate misunderstandings and possibly also inconsistencies (e.g. with regard to synchronous/and or asynchronous operation, currently only asynchronous operation is possible, but the description looks like a synchronous retrieval of the PCF data)
What's the benefit?
A) Create a better understanding of the content.
B) To have an explicit use case for the contracts >> enablement of the users
C) Clear and concise description
What are the Risks/Dependencies ?
A) There are none.
B) Incorrect use of bilateral contracts.
C) Missing functionality.
Detailed explanation
Current implementation
Proposed improvements
Feature Team
Contributor
Committer
User Stories
Acceptance Criteria
Architectural Relevance
The following items are ensured (answer: yes) after this issue is implemented:
Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)
Additional information