diff --git a/documentation/CAMARA-API-access-and-user-consent.md b/documentation/CAMARA-API-access-and-user-consent.md index 26fe7f1..4e119b1 100644 --- a/documentation/CAMARA-API-access-and-user-consent.md +++ b/documentation/CAMARA-API-access-and-user-consent.md @@ -65,7 +65,7 @@ A purpose declares what the application intends to do with a set of personal inf ### Purpose definition -The purpose definition (naming + description) and format for CAMARA follows the W3C [Data Privacy Vocabulary](https://www.w3.org/community/dpvcg/)​ (DPV). The way in which purposes are organised within the DPV is specified in [Purpose taxonomy in DPV](https://w3c.github.io/dpv/dpv/#vocab-purposes). +The purpose definition (naming + description) and format for CAMARA follows the W3C [Data Privacy Vocabulary](https://w3c.github.io/dpv/)​ (DPV). The way in which purposes are organised within the DPV is specified in [Purpose taxonomy in DPV](https://w3c.github.io/dpv/2.0/dpv/#vocab-purposes). ### Applying purpose concept in the authorization request diff --git a/documentation/CAMARA-Security-Interoperability.md b/documentation/CAMARA-Security-Interoperability.md index 36f84fd..7744060 100644 --- a/documentation/CAMARA-Security-Interoperability.md +++ b/documentation/CAMARA-Security-Interoperability.md @@ -222,7 +222,7 @@ Purpose is one of the scope parameter's values. There MUST be exactly one purpos The Authorization Server identifies the purpose using the prefix `dpv:`. -This scope MUST have the following format: `dpv:` where `` is coming from [W3C DPV purpose definition](https://w3c.github.io/dpv/dpv/#vocab-purpose) +This scope MUST have the following format: `dpv:` where `` is coming from [W3C DPV purpose definition](https://w3c.github.io/dpv/2.0/dpv/#vocab-purposes) @@ -267,7 +267,7 @@ Camara recommends that implementations run the OIDF interoperability suite and a ## References -* [Data Privacy Vocabulary (DPV)](https://w3c.github.io/dpv/dpv/) +* [Data Privacy Vocabulary (DPV)](https://w3c.github.io/dpv/2.0/dpv/) * [E.164 - The international public telecommunication numbering plan](https://www.itu.int/rec/T-REC-E.164-201011-I/en) * [OpenID Connect Core 1.0 specification](https://openid.net/specs/openid-connect-core-1_0.html) * [OpenID Connect Client-Initiated Backchannel Authentication Flow - Core 1.0](https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html)