From 3ebfe17a2641c0adacb99a613b6cab137fa0607c Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Tue, 16 Apr 2024 15:59:06 -0400 Subject: [PATCH] Clarify language around statusPurpose. Co-authored-by: Dave Longley --- index.html | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/index.html b/index.html index 92f7e2b..02aeccb 100644 --- a/index.html +++ b/index.html @@ -663,14 +663,17 @@

BitstringStatusListEntry

-Status list entries can be used to associate many status types with a -[=verifiable credential=] by using the `message` status purpose. The set of -messages associated with a particular entry is committed to by the [=issuer=] -by using the `statusSize`, `statusMessage`, and optional `statusReference` -properties. This commitment is done at the time of issuance to ensure that +The use of `message` as the status purpose enables an issuer to +define an arbitrary number of custom, descriptive messages about +the status of the [=verifiable credential=]. The [=issuer=] commits to +the set of messages that may be associated with a particular entry +(i.e., with a particular [=verifiable credential=]) through the +`statusSize`, `statusMessage`, and optional `statusReference` properties, +at the time of [=verifiable credential=] issuance. This is to ensure that the [=holder=] knows what sort of information might be associated with a -particular [=verifiable credential=] that is in their possession, and would -then be discoverable by a [=verifier=] that receives that credential. +particular [=verifiable credential=] they keep in their possession, that +could then be discoverable by a [=verifier=] that later receives that +credential.