From 5b021d19ee0ec57ab6fa096d968f0af1b46ad6a5 Mon Sep 17 00:00:00 2001 From: Ulf Bjorkengren Date: Tue, 14 Nov 2023 15:19:59 +0100 Subject: [PATCH] Purposelist consent update. Signed-off-by: Ulf Bjorkengren --- spec/VISSv2_Core.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/VISSv2_Core.html b/spec/VISSv2_Core.html index 3fb368d..6dbfebf 100644 --- a/spec/VISSv2_Core.html +++ b/spec/VISSv2_Core.html @@ -1627,7 +1627,7 @@

Purpose List

There is also a long purpose description, which may be used in the dialogue for consent, if needed. Then there is a list of the client context, i. e. the sub-actor role triplet, that can be granted this access, and last there is a list of the signals that the client is given access to for this purpose, - with the allowed access permission. The list shall use a JSON format as shown in the example below. + with the access control and consent requirements. The list shall use a JSON format as shown in the example below. 

         {"purposes":
             [{"short": "fuel-status",