Repository navigation
docs(provenance): remove the unscoped compliance claim - #282
Closed
dimitri-yatsenko wants to merge 1 commit into
Closed
dimitri-yatsenko wants to merge 1 commit into
dimitri-yatsenko wants to merge 1 commit into
Conversation
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.
Member
Author
|
Closing. The sentence is there so the page doesn't claim that the DataJoint library ensures compliance by itself: compliance comes from the Platform, not the library alone. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
Removes one sentence from
explanation/comparison-to-provenance-systems.md:What an exported account carries depends on what the deployment captured. Data computed with DataJoint's library defaults carries no job metadata or code version, tables declared before
add_job_metadatawas enabled receive no job metadata during populate, and manually entered rows carry no attribution. The page cannot promise compliance across those cases.The paragraph now ends on the preceding sentence, which states the supported behavior: DataJoint's lineage maps to industry standards such as OpenLineage or W3C PROV.
Test plan
Prose-only change; no links or anchors affected.