Why and where¶
Buneman, P., Khanna, & Tan, W. -. (2001). Why and where: A characterization of data provenance. Database Theory — ICDT 2001.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Provenance
- This asymmetry implies that metadata preservation is an investment decision: if I do not document now, verification later becomes probabilistic, costly, or impossible, an implication Buneman, Khanna, and Tan (2001) make precise in their why-and-where formal model of database provenance.
This sourceDistinguishes "why" provenance (source data influencing existence) from "where" provenance (location of extraction); foundational separation of provenance claims from their underlying evidence structures.
- This asymmetry implies that metadata preservation is an investment decision: if I do not document now, verification later becomes probabilistic, costly, or impossible, an implication Buneman, Khanna, and Tan (2001) make precise in their why-and-where formal model of database provenance.
- Traceability
- It operates as both an operational capability and an audit trail: manufacturing lot tracking, code-to-requirements matrices, supply chain mapping, scientific data lineage, legal chain of custody, version control history, and pharmaceutical batch tracing all follow the same bidirectional linking logic.
This sourceDistinguishes "why" provenance (source data influencing existence) from "where" provenance (location of extraction); foundational separation of provenance claims from their underlying evidence structures.
- It operates as both an operational capability and an audit trail: manufacturing lot tracking, code-to-requirements matrices, supply chain mapping, scientific data lineage, legal chain of custody, version control history, and pharmaceutical batch tracing all follow the same bidirectional linking logic.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:fc02fea8378c · see in the full table