Re: PROPOSED WORK ITEM: DID-Linked Resources Specification

I don't think they are the same.

The proposed work item is about dereferencing independent of an underlying
storage system.

DWNs are a more complicated spec which makes some use of DID URLs.

I don't think the simpler work item should be inhibited or slowed down by
combining it or taking a dependency on DWNs.

We tried that with EDVs and the precursor to DWNs called Identity Hubs, and
it did not go well.

There is a connection point between this work item, the did resolution spec
at CCG and the DID Core spec.

Happy to discuss on an upcoming CCG call.

OS



On Tue, Dec 6, 2022, 8:15 PM Daniel Buchner <dbuchner@tbd.email> wrote:

> I'll note that the goal of this proposed work item is the very crux of
> what we're building in the joint DIF/W3C Decentralized Web Nodes work item,
> which enables all objects, file types, schemas, etc., to be addressed in a
> DID-relative way that delivers an implicit, inferrential API without any
> need to craft things specific to a given set of objects/files. Given this
> is already a joint work item of the the two orgs, can we first examine it
> and do a call about how it delivers on the stated goals of this proposal,
> and/or modify it to do so?
>
> There will be 1:1 overlap if we spin up a new work item to do the same
> thing, and it would be unfortunate if we created competing efforts almost
> immediately as a solution/spec is in the later stages of development.
>
> How about a call to review sometime before the holidays or just after in
> January?
>
> - Daniel
>
> On Tue, Dec 6, 2022, 7:56 PM Alex Tweeddale <alex@cheqd.io> wrote:
>
>> Dear CCG,
>>
>> The formal new work item proposal is in the GitHub issue below:
>> https://github.com/w3c-ccg/community/issues/236
>>
>> We are proposing to establish a new work item focussed on creating a W3C
>> specification for DID-Linked Resources, which will tie in closely with the
>> existing DID Resolution spec.
>>
>> This work aims to create a standardized way of referencing,
>> dereferencing and fetching digital resources (schemas, trust & status
>> lists, visual representations of Verifiable Credentials, governance
>> documents, logos).
>>
>> We aim to achieve this by associating digital resources with
>> Decentralized Identifiers (DIDs) and organizing in DID-Linked Collections,
>> where each individual resource is identifiable through its own DID URL.
>>
>> Previous work on this topic, leading to this new work item:
>>
>> - (cheqd) Context for DID-Linked Resources
>> <https://docs.cheqd.io/identity/guides/did-linked-resources/technical-composition-of-did-linked-resources>
>> - (cheqd) Technical composition of DID-Linked Resources
>> <https://docs.cheqd.io/identity/guides/did-linked-resources/technical-composition-of-did-linked-resources>
>> - (ToIP) Trust over IP Draft Specification on DID-Linked Resources, to
>> be superseded by the W3C work item
>> <https://wiki.trustoverip.org/display/HOME/DID-Linked+Resources+Specification>
>>
>>
>> Looking forward to getting this kicked off!
>>
>> Alex
>>
>> Alex Tweeddale
>>
>> Product Manager & Governance Lead
>>
>> Schedule a meeting
>> <https://calendly.com/alex-tweeddale/introductory-call>
>>
>> cheqd.io <https://www.cheqd.io/> | Twitter <https://twitter.com/cheqd_io>
>> | LinkedIn <https://linkedin.com/company/cheqd-identity> | Telegram
>> <https://t.me/cheqd>
>>
>