Skip to content

docs: scope the provenance-compliance claim to platform-managed computation #277

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ttngu207 wants to merge 1 commit into from
Closed

docs: scope the provenance-compliance claim to platform-managed computation #277

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions src/explanation/comparison-to-provenance-systems.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,8 +74,14 @@ This integration is opt-in and configured explicitly; it is not automatic.
Interchange in either direction uses the standards the surrounding ecosystem
speaks. DataJoint's lineage is expressed in its own schema; where it is exchanged
with external governance, audit, and cataloging systems, it maps to industry
lineage and provenance standards such as OpenLineage or W3C PROV. Compliance with
industry provenance standards is ensured by the DataJoint Platform.
lineage and provenance standards such as OpenLineage or W3C PROV.

The DataJoint Platform supports compliance with industry provenance standards for
the computation it manages. What an exported account can carry depends on what was
captured: platform-managed computation records the code version, the worker, and
timings for every computed row, while data entered or populated outside the
platform carries less. Compliance is a property of the deployment, not of the
format.

## See also

Expand Down
Loading