Answers are grounded in this paper and cite their sources.
Technical specification demonstrates standardized interchange for operational-provenance evidence, highlighting conservative link resolution and deterministic schema migration.
EACP Profile 1.3 is an implementable candidate interchange specification for operational-provenance evidence. It defines a typed evidence tuple, scoped service and actor identities, typed and multivalued links, source pointers with optional representation digests, deterministic migration from the EACP 1.2 13-column projection, and conservative exact-link resolution that abstains when the selected identifier is missing or ambiguous. This citation edition preserves the profile text released with the annotated Git tag v1.3.0 at commit 537799bd2b292ce6e78004de22f4ab6df1b4feda and includes three JSON Schemas, a valid example, the dependency-free Python reference validator/migrator/resolver, and its 19-test suite. The Profile represents evidence and associations; it does not authenticate sources, establish source truth, prove causation, or guarantee collision-free identifiers. Specification, schemas, example, and documentation are CC BY 4.0; Python reference tool and tests are Apache-2.0.
No takes yet. Share an insight, caveat, or question.
Obede Bessa Rocha da Silva (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: