W3C home > Mailing lists > Public > public-credentials@w3.org > August 2021

Re: WoN Re: Public consultation on EU digital principles

From: Bob Wyman <bob@wyman.us>
Date: Fri, 13 Aug 2021 14:13:21 -0400
Message-ID: <CAA1s49WLGSchjGsRtbnzSxZkvzW6fMhU-NoDxg3Qwm7Ei5ZsUA@mail.gmail.com>
To: Christopher Allen <ChristopherA@lifewithalacrity.com>
Cc: "Ward, David" <dward@pcgus.com>, "public-credentials@w3.org" <public-credentials@w3.org>
Given that there appears to be no general method to discover VC's
concerning a subject, or VC's which refer to other VC's, I wonder if it
would be reasonable to use the W3C Annotation Protocol
<https://www.w3.org/TR/annotation-protocol/> as a means to provide
discoverable VC's?

Is there any reason that annotations do not provide a reasonable mechanism
for satisfying these needs in a general way? If so, how do annotations fall
short? What needed capabilities would not be provided by an
annotation-based system? (Note: I recognize that discoverability would be
limited by the inevitable scope limitations of individual annotation
servers or federations of servers.)

bob wyman

On Thu, Aug 12, 2021 at 5:46 PM Christopher Allen <
ChristopherA@lifewithalacrity.com> wrote:

> On Thu, Aug 12, 2021 at 1:47 PM Ward, David <dward@pcgus.com> wrote:
>> Is there a method to discover "public" VCs about a subject?  Being able
>> to publish such a VC would only be useful if others can find it (I'm
>> assuming the comment would be a VC).
> Not in any general way, but there can be method specific ones.
> In did:btcr 0.1 you can retrieve an optional “extended” did object data
> (as you can only fit 80 chars in a Bitcoin transaction), which is merged
> with the blockchain derived data to make the final did object.
> By convention, you can append self-signed verifiable credentials to the
> extended did object if you are using JSON-LD. Alternatively, you can add to
> the extended data object a link to an array of self-signed claims.
> — Christopher Allen [via iPhone]
Received on Friday, 13 August 2021 18:14:45 UTC

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