Re: JSON-only impls of DID core?

Daniel,

proprietary implementations are fine if they are willing to shere with us publicly the results of their implementations running our test suite (details to be discussed, of course).

Ivan

----
Ivan Herman, W3C
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: https://orcid.org/0000-0003-0782-2704
On 30 Jun 2020, 19:57 +0200, Daniel Hardman <daniel.hardman@evernym.com>, wrote:
> I wasn't at today's meeting, but I understand that people were looking for public impls that take the abstract data model down the JSON-only path?
>
> I'm not sure what qualifies as an impl, but here are some that I am aware of.
>
> https://pypi.org/project/peerdid/ (This is a python impl of peer DIDs that has no DNA at all in common with my normal Indy work. It's not super robust, but it does include logic to parse DID docs and to emit them. It also includes a JSON-only extension in that it expects an `authorization` key to exist and it handles it in non-JSON-LD fashion. There are various forks with different statuses, so I'm forgetting at the moment which features manifest where.)
>
> Dave Huseby did a Rust-based crate that implements JSON-only DID doc parsing from scratch. I'm not remembering the name at the moment; it's NOT https://crates.io/crates/caelum-diddoc.
>
> The code in indy-node emits JSON-only DID docs. (It consumes updates to DID docs more granularly, so it doesn't parse said docs; the docs are just a view or transform of underlying ledger details.)
>
> I think aries-framework-go and aries-framework-python both have parts of DID doc support in them; not sure about how much.
>
> I am also aware of some proprietary impls, but I think we're not looking for those, right?