Update How-to-conclude-Data-Exchange-Contracts document #151
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 suggestion.
Comments skipped due to low confidence (2)
docs/regulatory-framework/10000ft/data-exchange-contracts.md:27
- The word 'facili-tates' is incorrectly split. It should be 'facilitates'.
The RC facili-tates the conclusion of data exchange contracts and the subsequent exchange of data.
docs/regulatory-framework/10000ft/data-exchange-contracts.md:49
- [nitpick] The phrase 'specifying certain Technical Policies (including who may view and use which data set and engage with DP's RC: "Access and Usage Policies")' is awkwardly phrased and should be reworded for clarity.
DP will specify the data set it wishes to exchange with one or several DC, by referencing a Predefined Policy, specifying certain Technical Policies (including who may view and use which data set and engage with DP's RC: "Access and Usage Policies") as well as related legal terms.
|
|
||
| Data providers & data consumer have the option of concluding bilateral contracts (supplier contract, ...) within the confines of Predefined Use Case Frameworks that clarify additional terms that the two parties want to specify. These bilateral contracts should be referenced in the policies used with the RC. Moreover, when using Catena-X to exchange data outside a given Use Case and thus Predefined Use Case Framework, bilateral contracts outside of Catena-X are strongly recommended. | ||
| Where DP and DC are free to conclude any contracts in compliance with the Governance Framework. In such case, they should pref-erably reference those contracts in the policies used with the RC, whereas the parties have full discretion how they refer to such poli-cies in their contracts. |
There was a problem hiding this comment.
The words 'pref-erably' and 'poli-cies' are incorrectly split. They should be 'preferably' and 'policies'.
Suggested change
| Where DP and DC are free to conclude any contracts in compliance with the Governance Framework. In such case, they should pref-erably reference those contracts in the policies used with the RC, whereas the parties have full discretion how they refer to such poli-cies in their contracts. | |
| Where DP and DC are free to conclude any contracts in compliance with the Governance Framework. In such case, they should preferably reference those contracts in the policies used with the RC, whereas the parties have full discretion how they refer to such policies in their contracts. |
Copilot is powered by AI, so mistakes are possible. Review output carefully before use.
|
@AnnKaCatX shouldn't these changes be done in the private repository and then synced via the script? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added How-to-conclude-Data-Exchange-Contracts document.