W3C home > Mailing lists > Public > public-credentials@w3.org > September 2017

Re: Verifiable Text-based Claims

From: Adam Sobieski <adamsobieski@hotmail.com>
Date: Thu, 14 Sep 2017 01:50:07 +0000
To: David Chadwick <D.W.Chadwick@kent.ac.uk>, "public-credentials@w3.org" <public-credentials@w3.org>
Message-ID: <DM5PR01MB32759BDE405A61148B6602B5C56F0@DM5PR01MB3275.prod.exchangelabs.com>

Thank you. At https://w3c-ccg.github.io/verifiable-news/sketchpad.html#http-based-revocation , I describe a system where Not found (404, 410) means revoked and Ok (200) means not revoked. I see what you’re saying about Not found meaning not revoked and Ok with a credential ID meaning revoked as well as the feature of retrieving lists of revoked credentials. I think that we should have both HTTP-based approaches. I updated the document with these ideas.

Best regards,

From: David Chadwick<mailto:D.W.Chadwick@kent.ac.uk>
Sent: ‎Wednesday‎, ‎September‎ ‎13‎, ‎2017 ‎3‎:‎21‎ ‎PM
To: public-credentials@w3.org<mailto:public-credentials@w3.org>

Hi Adam

I notice that you are also including a revocation mechanism in your
claims. I produced an IETF draft 10 years ago which proposed something
very similar for X.509 certificates
( See https://www.ietf.org/archive/id/draft-chadwick-webdav-00.txt).
Conceptually they are the same: the credential contains the URL where
the revocation information can be found. If Not found is returned the
credential has not been revoked, otherwise Ok is returned along with a
CRL of length 1 containing the ID of the revoked credential. My ID
contains other features as well, such as the ability to retrieve all the
revoked credentials of a particular issuer. You might wish to consider
this as well



On 12/09/2017 22:13, Adam Sobieski wrote:
> I’m exploring and sketching some ideas with regard to verifiable
> text-based claims.
> https://w3c-ccg.github.io/verifiable-news/sketchpad.html

> Questions, comments and suggestions welcomed.
> Best regards,
> Adam Sobieski

Received on Thursday, 14 September 2017 01:50:36 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:45 UTC