Data Privacy Vocabulary
| Field | Value |
|---|---|
| Status | Adopt terms |
| Version pinned | DPV 2.3 (25 February 2026) |
| Source | https://w3id.org/dpv/ |
| What is taken | Purpose and provenance classes |
| Why | Interoperable purpose names rather than invented ones |
| What is extended or replaced | Maps Open Personal Context purposes to DPV terms; adds the advertising constraints |
| Specification home | A4.2, A6.2 |
Version pinned
Data Privacy Vocabulary (DPV) version 2.3, 25 February 2026, a Final Community Group Report of the W3C Data Privacy Vocabularies and Controls Community Group, read through w3id.org on 4 October 2026. A Community Group report is not a W3C Recommendation.
What is taken
- Purpose terms:
dpv:Purpose,dpv:hasPurposeand categories such asServiceProvision,PersonalisationandTargetedAdvertising. - Provenance terms:
DataSource,hasDataSource, andProvided,Collected,Observed,DerivedandInferred.
The mapping from the ten Open Personal Context purpose categories (A6.2) and the provenance kinds (A4.2) to these terms is written when grants carry purposes on the wire.
Why
Purpose and provenance names that other privacy tooling already understands make grants and receipts easier to audit and to export as consent records.
What is extended
Advertising is a separate, explicitly consented purpose with the A6.7 restrictions, which DPV's TargetedAdvertising does not itself impose.
What is replaced or not used
PDPP's example purpose URIs under pdpp.dev are not used as the purpose vocabulary (see the PDPP record, at commit 8f79a48).
Deviations
DPV's dated "This version" link returned 404 on 4 October 2026; this record pins the w3id.org address with the version number.
Conformance checks
CONSENT-01 and SCOPE-02 in the conformance manifest, with runtime evidence pending.
References to other standards and projects describe intended technical alignment only and do not imply endorsement or partnership.