From 22819e96e2df451f89702d79b026fd3ceffd5554 Mon Sep 17 00:00:00 2001 From: Dimitri Yatsenko Date: Tue, 29 Sep 2026 15:42:28 -0500 Subject: [PATCH] docs(provenance): remove the unscoped compliance claim The sentence said compliance with industry provenance standards is ensured by the DataJoint Platform. What an exported account carries depends on what the deployment captured, so the page cannot promise compliance. The preceding sentence already states the supported behavior: lineage maps to OpenLineage or W3C PROV. --- src/explanation/comparison-to-provenance-systems.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/explanation/comparison-to-provenance-systems.md b/src/explanation/comparison-to-provenance-systems.md index 74b3c13f..b21205f4 100644 --- a/src/explanation/comparison-to-provenance-systems.md +++ b/src/explanation/comparison-to-provenance-systems.md @@ -74,8 +74,7 @@ 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. ## See also