Hi Giuseppe,
The current figure in the Introduction from
draft-demarco-status-attestations-latest is:
+-++---+
|| Requests Status Attestation ||
||>||
| Wallet Instance || Credential Issuer |
|| Status Attestation||
||<---
Typo: Change:"proof _*or*_ origin of wallet instance"
into : "proof _*of*_ __origin of wallet instance".
The figure has been corrected below.
Denis
Hi Giuseppe,
The current figure in the Introduction from
draft-demarco-status-attestations-latest is:
+-++--
Ciao Denis,
thank you for the quick reply and for your contribution.
The scope of the current draft is to provide a verifiable artifact that
give the proof that a specific credential is active, then not revoked.
>From your sequence diagram I read a digital credential issuance, while this
is not i
The big problem is that standards bodies all over the spectrum are creating
attestations without even bothering to see what is happening in other
communities. The verifier will have many attestations to choose from and
will thus choose to do nothing with any of them. Perhaps it is time to ask
a ver
Giuseppe,
You are perfectly right, I read your draft too quickly.
1) The text mentions near the end:
OAuth Status List can be accessed by a Verifier when an internet
connection is present.
This does not correspond to the flows of the figure.
2) The text states:
" The proof of posses
it is very presumptuous for you to tell the verifier what they must do.
Why do you think they will pay any attention to you?
Be the change you want to see in the world ..tom
On Thu, Jan 18, 2024 at 10:39 AM Giuseppe De Marco <
gi.dema...@innovazione.gov.it> wrote:
> Hi Tom,
>
> let's try to alig
