ANCR–DPV GitHub Issue Drafting
26-feb
Purpose
Canonical submission register for ANCR’s DPV / DPV-27560 comments.
Table of Comments
ID | Priority | Title / topic | Finding (short) | Requested change (comment-ready) | Target artefact | Evidence / authority | Approved for submission | Status | Submission batch |
|---|---|---|---|---|---|---|---|---|---|
C1 | P0 | Identifier governance | Mandatory principal identifiers create linkability risk in open-network contexts. | See comment-ready text in ANCR-DPV Comments (C1 row). | DPV-27560 Guide |
|
| Draft | V2 |
C2 | P1 | Sequence integrity | Records/receipts can be generated after processing begins (notice-after risk). | See comment-ready text in ANCR-DPV Comments (C2 row). | DPV-27560 Guide |
|
| Draft | V2 |
C3 | P0 | Recipient transparency | Implicit/unnamed third parties can appear without accountable roles. | See comment-ready text in ANCR-DPV Comments (C3 row). | DPV-27560 Guide |
|
| Draft | V2 |
C5 | P2 | Notice version binding | Notice references are not evidence-grade bindings to presented notice version. | See comment-ready text in ANCR-DPV Comments (C5 row). | DPV-27560 Guide |
|
| Draft | V2 |
C8 | P0 | International baseline | GDPR-forward framing undermines cross-border baseline interoperability. | See comment-ready text in ANCR-DPV Comments (C8 row). | DPV-27560 Guide |
|
| Draft | V2 |
C17 | P1 | Receipt vs record semantics | Receipt-as-copy framing normalises controller post-hoc exports as evidence. | See comment-ready text in ANCR-DPV Comments (C17 row). | DPV-27560 Guide |
|
| Draft | V2 |