Re: Revocation entry

Thanks Manu and Mike for your replies. They were very helpful!

Oliver

On Sat, Sep 28, 2019 at 3:17 AM Mike Lodder <mike@sovrin.org> wrote:

> The actual value in the credential is just a 256-bit number. It's not a
> URL or anything special because we encode everything as 256-bit numbers.
> Since its known who the issuer is by the DID, Sovrin allows you to know if
> there is a revocation registry associated with the issuer's public key
> since you can see both on the blockchain.
>
> Hope that helps.
>
> On Fri, Sep 27, 2019 at 7:05 AM Manu Sporny <msporny@digitalbazaar.com>
> wrote:
>
>> On 9/27/19 6:50 AM, Oliver Terbu wrote:
>> > Our current approach is:
>> >
>> > ``` "revocation": { "id":
>> > "some-identifier-that-points-to-the-instance", "type":
>> > "EIPxyzRevocationRegistry2019" }, ```
>>
>> Oliver, this is a reasonable way to structure what you're trying to do,
>> but a few suggestions based on what the VC spec says today. The `status`
>> mechanism is meant to be used for credential suspension, revocation, etc.:
>>
>> https://www.w3.org/TR/vc-data-model/#status
>>
>> So, your example above would be more like this:
>>
>> "status": {
>>    "id": "some-identifier-that-points-to-the-registry/network",
>>    "type": "EIPxyzStatusRegistry2019",
>>    ... any other data that is required for registry interaction...
>> }
>>
>> I suggest you write a tiny spec and register it here:
>>
>> https://w3c-ccg.github.io/vc-extension-registry/#status-methods
>>
>> there is a terrible example of what such a spec could look like here:
>>
>> https://w3c-ccg.github.io/vc-csl2017/
>>
>> I expect that this is a work item that will gain momentum over the next
>> year... hope that helps.
>>
>> -- manu
>>
>> --
>> Manu Sporny (skype: msporny, twitter: manusporny)
>> Founder/CEO - Digital Bazaar, Inc.
>> blog: Veres One Decentralized Identifier Blockchain Launches
>> https://tinyurl.com/veres-one-launches
>>
>>
>
> --
> Mike Lodder
> Security Maven
>
>