Anil John

This perspective is familiar and prevalent in our technical community >> "We just want to build the best stuff with the best of intentions for others to use. Nothing more...

I would HIGHLY recommend thinking thru the reality that there are jurisdictions where "who is authoritative for what" is not well defined, and where they are (or will be). It...

> Most of the high value wallets will likely be tightly bound to the issuer. While this may be true for some, the U.S. Citizenship and Immigration Services, an issuer...

> Opaque, protocol-specific request strings don't allow site authors to indicate why and how each field in the request will be used, or to provide the context for a user...

Bit old school, but `requestAttributes` or `requestAttributeBundle` ?

re: Support for web-based wallets Is the question being asked too narrow? Without getting into the weeds, if the scope of this identity-credential work is to provide for an open...

From the perspective of Issuers and Verifiers of high value global credentials related to cross-border travel, employment and immigration, I've found that the scope attached to what is meant by...

>Remove `@vocab` from the core context. +1 >For the "Getting Started" section, create a "development context" ... +1 particularly if the existence of that development context is something I can...

>`@vocab` is a broadly useful feature with respect to JSON-LD ... Agree with @tplooker on this. However, also believe that having `@vocab` in the base context blinds developers to its...