Daniel Bluhm

Yep, interopathon goals are deliberately narrower than our overall ambitions. Support for more protocols will come.

I'm unable to attend ACA-PUG today so apologies if I missed important discussion items. My two cents on this, I think I'd like to see the idea of a "public...

Try adding `#Person` onto the end of the uri in the presentation definition: ```json "schema": [ { "uri": "https://w3c-ccg.github.io/citizenship-vocab/contexts/citizenship-v2.jsonld#Person" } ] ``` I haven't questioned this or looked deeply into...

I did some exploration with your examples and have recreated the scenario you described. ACA-Py is indeed "expanding" the `type` of the credential and using the `@id` from the json-ld...

I'm curious if @PatStLouis has any additional insights

Full agreement from me on switching to ruff for formatting too; it is noticeably faster than black

> Perhaps not needed yet, but I think we want that in the future. It gives the controller the choice, without having to get its hands dirty with the rules...

@jamshale heads up on the conflict in the poetry.lock

ACA-Py is defaulting to using unqualified DIDs when a did:peer:1 is received from the requester. This is probably the wrong default. While testing interop between ACA-Py and Credo, I had...

I intended to fix this with https://github.com/hyperledger/aries-cloudagent-python/pull/1851; when ACA-Py is the mediation client, to serialize the process, the controller should call the `update-keylist` endpoint before moving on to `accept-invitation` or...