Purpose for Access Request - Revision history

Tom: /* Current Standard Request Messages */

2022-08-26T16:27:06Z

‎Current Standard Request Messages

2022-08-11T00:59:17Z

‎References

2022-08-05T23:36:46Z

‎Example Schema

2022-08-05T23:33:34Z

‎Normative Specification

2022-08-05T23:31:28Z

‎Normative Specification

2022-08-05T23:29:01Z

‎Example Schema

2022-08-05T23:25:36Z

‎Example Schema

2022-08-05T23:23:49Z

‎Example Schema

2022-08-05T23:19:24Z

‎Current Standard Request Messages

2022-08-05T23:16:10Z

‎Example Schema

@@ Line 32: / Line 32: @@
   user ==> responds with signed consent to rp winch MUST include All required purposes plus opt-in optional purposes
   user <==  rp response with ANCR signed by data controller (who may not be the rp)
 ==Current Standard Request Messages==

← Older revision		Revision as of 00:59, 11 August 2022
Line 159:		Line 159:

	==References==		==References==
		+	* See wiki page for [[User-centric Consent]].

	[[Category: Consent]]		[[Category: Consent]]

@@ Line 98: / Line 98: @@
        "@id": "https://www.w3.org/2018/consents#consent",
        "@context": {
-         "@version": 1.1,
+         "@version": 1.0,
          "@protected": true,

@@ Line 82: / Line 82: @@
 * The '''Purpose''' MUST be included in all requests for [[User Information]] (aka PII). The schema for the Purpose SHOULD be included in a @context element as a URL to the appropriate schema.
 * The '''Purpose''' MUST include an indication if it is REQUIRED, otherwise it will be considered to be an OPT-IN request.
 ==Non-normative Information==

@@ Line 80: / Line 80: @@
 ==Normative Specification==
-The '''Purpose''' MUST be included in all requests for [[User Information]] (aka PII). The schema for the Purpose SHOULD be included in a @context element as a URL to the appropriate schema.
+* The '''Purpose''' MUST be included in all requests for [[User Information]] (aka PII). The schema for the Purpose SHOULD be included in a @context element as a URL to the appropriate schema.
 ==Non-normative Information==

@@ Line 123: / Line 123: @@
+           {
            "consentPurpose": {"@id": "consent:consentPurpose", "@type": "@id"},
            "consentRequired": {"@id": "consent:consentRequired", "@type": "@id"},
            "evidence": {"@id": "consent:evidence", "@type": "@id"},

@@ Line 142: / Line 142: @@
                "ManualRefreshService2018": "consent:ManualRefreshService2018"
+             }
            },
            "termsOfUse": {"@id": "consent:termsOfUse", "@type": "@id"},
            "validFrom": {"@id": "consent:validFrom", "@type": "xsd:dateTime"},
            "validUntil": {"@id": "consent:validUntil", "@type": "xsd:dateTime"}
      },
      "Consent" {

@@ Line 124: / Line 124: @@
            "consentPurpose": {"@id": "consent:consentPurpose", "@type": "@id"},
            "consentSubject": {"@id": "consent:consentSubject", "@type": "@id"},
            "evidence": {"@id": "consent:evidence", "@type": "@id"},
            "expirationDate": {"@id": "consent:expirationDate", "@type": "xsd:dateTime"},

@@ Line 34: / Line 34: @@
 ==Current Standard Request Messages==
-These are all call [[Authorization]] Requests rather than Access Requests, which is the typical current transaction type.
+The standards all call these [[Authorization]] Requests rather than Access Requests, which is the typical current transaction type and the only one addressed here.
 ===OAUTH Authorization Request===
 From RFC 6749                        OAuth 2.0                   October 2012