Re: Idea for a Proposal: Notation for resolving a DID identifier directly to the underlying object or collection of objects associated with the DID identifier

Yes Charles, that syntax appears to be functionally the equivalent the proposed "*" indirection operator.

My gentle feedback is that it's too bad that it's spec'ed to be part of the syntax of the DID URL. 🙂 That being said, it certainly has its valid use cases.

At a more formal level, I'd propose that the *foo notation *not* be part of the DID URL syntax but rather the beginning of a "DID algebra" that operates on DID Identifiers and DID Documents and DID Objects.
That is, something like...
*did:example:12345 = *(did:example:12345)
...where additional operators could be identified over time until an entire object algebra was realized.

FFT. Thank you for making the connection.

Michael

p.s. Maybe...
*did:example:12345 returns the DID Document
**did:example:12345 returns the underlying DID Object
... or something like that 🙂

Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Charles E. Lehner <charles.lehner@spruceid.com>
Sent: Saturday, December 18, 2021 9:56:29 PM
To: public-credentials@w3.org <public-credentials@w3.org>
Subject: Re: Idea for a Proposal: Notation for resolving a DID identifier directly to the underlying object or collection of objects associated with the DID identifier

Hi Michael,

On Sun, 19 Dec 2021 03:21:18 +0000
"Michael Herman (Trusted Digital Web)" <mwherman@parallelspace.net> wrote:

> What is a suitable notation to short circuit all of the above steps
> to simply return the underlying object or collection of objects
> associated with a particular DID identifier in a more direct way?

There is a "resource" DID URL parameter specified by ToIP - could that work?

  https://www.w3.org/TR/did-spec-registries/#resource

  https://wiki.trustoverip.org/display/HOME/DID+URL+Resource+Parameter+Specification


> If a DID method specification supports this parameter, and if a DID URL using that method includes the parameter with a valid value (either true or a valid media type name), then when a resolver calls the associated VDR using that DID URL, the VDR returns the identified digital resource, not the DID document.

Regards,
Charles E. Lehner