Sharing agreement¶
A sharing agreement is a governed, versioned agreement connecting a data product's reusable promises to a specific consumer's declared intent, expectations and obligations.
Why it exists¶
Producer promises and consumer requirements are related, but they are not the same thing.
A product may serve many consumers. Each consumption relationship may involve different purposes, policy constraints, access conditions, retention obligations or semantic expectations.
The sharing agreement provides a reference point for governing that relationship without redefining the underlying product.
Important distinction¶
The producer remains authoritative for the meaning of the product it publishes.
Consumer intent may introduce requirements or expose semantic mismatches, but it does not silently redefine producer semantics. Mismatches should be made explicit and resolved or accepted through governance.
Join the argument
Agree, challenge or add evidence
Architecture improves when its assumptions are challenged. Say which kind of contribution you're making:
- Challenge I disagree because…
- Evidence We've seen this too…
- Question How would this work when…?
- Alternative Another way to approach this…
- Extension This also implies…
Please keep clients, employers and colleagues unidentifiable. Strong contributions may be quoted and credited on this site. Read the contribution guidelines and the privacy notice.
Comments are provided by giscus and stored on GitHub. Posting requires a GitHub account.