W3C home > Mailing lists > Public > public-credentials@w3.org > November 2022

Re: Indexing/searching a corpus of (decentralized) self-sovereign data

From: Leonard Rosenthol <lrosenth@adobe.com>
Date: Wed, 16 Nov 2022 21:11:31 +0000
To: Juan Caballero <caballerojuan@pm.me>, "public-credentials@w3.org" <public-credentials@w3.org>
Message-ID: <DM8PR02MB8181D948EA5E8235C4931904CD079@DM8PR02MB8181.namprd02.prod.outlook.com>
Thanks to Juan, Alex, and John – I have a LOT of new reading to do!   Much appreciated.

Will definitely report back as I digest all of it and think through how it might be used.


From: Juan Caballero <caballerojuan@pm.me>
Date: Wednesday, November 16, 2022 at 3:08 PM
To: public-credentials@w3.org <public-credentials@w3.org>
Subject: Re: Indexing/searching a corpus of (decentralized) self-sovereign data

EXTERNAL: Use caution when clicking on links or opening attachments.

Hey Leonard!

> how do you reference a decentralized object (e.g. something on a DLT)

There is a little prior art for cross-chain/multi-chain indexing and addressing at CASA:

I know that Sebastian from https://iscc.codes/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fiscc.codes%2F&data=05%7C01%7Clrosenth%40adobe.com%7C099a2d5640354fde16fa08dac80d6df7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C638042261227068427%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cSUvvWpzGvujjVi1nK%2FYKvlzfIByhJ4MJL5JVEPo7N4%3D&reserved=0> and others in Europe have been building on CASA standards for exactly the kind of multi-chain indexing usecases I would imagine you're thinking about.

As for IPFS, the broader Protocol Labs archipelago of companies and [mostly open-source] codebases includes many building blocks and approaches to this point.  For example, in response to the limitations of ipfs:// as a protocol (that many contexts cannot trust), the IPFS community upgraded the "ipfs URL" as we know it, the Content Identifier has been upgraded<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.ipfs.tech%2Fhow-to%2Fbest-practices-for-ipfs-builders%2F%23use-cidv1-for-future-proof-addressing-and-case-insenstive-contexts&data=05%7C01%7Clrosenth%40adobe.com%7C099a2d5640354fde16fa08dac80d6df7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C638042261227068427%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VlrCiQWE4AwjvoaPOaq13p4iwBmnURr2LRgBha6V6N8%3D&reserved=0> to a case-insensitive and prefixed new version, which enables IPFS gateways to deliver them over https:// for those use-cases where a specific IPFS gateway operator is easier to allow-list (and trust) than ipfs:// qua protocol.  (Shout out to Markus' DNSlink spec at IETF!).  Depending how far into the IPFS weeds you want to go, there are many options, and companies like Ceramic, DAG-Haus, and Web3.storage are trying to advance and popularize IPLD as a way of tracking decentralized data across contexts.

As for DID URLs, big up to Cheqd team and Markus for picking that back up, looking forward to more progress there for all these use-cases!

On 11/15/2022 9:35 PM, Leonard Rosenthol wrote:
It’s not unlike a problem that we are trying to reconcile in C2PA – how do you reference a decentralized object (e.g. something on a DLT)?   There is no standardize mechanism for referencing – ala a URL.  At least for IPFS, they standardized a model for “proxying” so that you can use an `ipfs://` URL.

DIDs, and the DID Method registry, are something for identities – but that doesn’t help for all the myriad of other things that can live on a DLT.

Hope this conversation can include that as well.


From: Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net><mailto:mwherman@parallelspace.net>
Date: Tuesday, November 15, 2022 at 2:22 PM
To: public-credentials (public-credentials@w3.org<mailto:public-credentials@w3.org>) <public-credentials@w3.org><mailto:public-credentials@w3.org>
Subject: Indexing/searching a corpus of (decentralized) self-sovereign data

EXTERNAL: Use caution when clicking on links or opening attachments.

As I started to think about this, it turns out that it is not a straightforward problem (and hence, neither is the solution).

Is anyone aware of any previous discussions on this topic, articles, papers, etc. that analyze this problem and, perhaps, characterize what a solution might look like?

Thank you,

Best regards,
Michael Herman
Far Left Self-Sovereignist
First Principles Thinker

Self-Sovereign Blockchain Architect
Trusted Digital Web
Hyperonomy Digital Identity Lab
Parallelspace Corporation


Juan Caballero, PhD. Freelance<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearningproof.xyz%2F&data=05%7C01%7Clrosenth%40adobe.com%7C099a2d5640354fde16fa08dac80d6df7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C638042261227068427%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=LHFc0bU%2FpnitYxjHKQ1rdUj0qBZ2jCNSHQjrRabJd0g%3D&reserved=0> Identity Researcher & Community Manager Berlin-based: +49 one573 59945two5 Signal/whatsapp: +1 4one5-310135one

(image/jpeg attachment: image001.jpg)

Received on Wednesday, 16 November 2022 22:07:01 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 16 November 2022 22:18:34 UTC