Orie Steele

@samuelgoto its a normative property of the w3c vc data model: https://w3c.github.io/vc-data-model/#dfn-type In the case of `IdentityCredential` as "a more specific verifiable credential type"... is "IdentityCredential" also an RDF Class...

In that case `IdentityCredential` would be some abstract class, not an RDF class... and the web APIs would not need to know anything about the interface, beyond that it was...

The traditional solution I've seen to this problem is to mandate "application specific identifiers", and then to try to design the protocols to always mix the application context... at least...

Not recommending any of these, just surfacing them for inspiration: - https://www.w3.org/TR/json-ld11-framing/ - https://www.w3.org/TR/sparql11-query/ - https://www.gqlstandards.org/what-is-a-gql-standard - https://neo4j.com/developer/cypher/ - https://datatracker.ietf.org/doc/html/rfc6901

Addition context regarding the interaction between query languages and credential formats: - https://github.com/WICG/identity-credential/issues/12 - https://w3c-ccg.github.io/vp-request-spec/#query-by-frame vp request spec supports multiple "query languages" including query by (JSON-LD) frame. Finding a query...

is `nonce` the same as WebAuthN `challenge`? or can `nonce` be an arbitrary length string (like a JWS or JWE). are the params always limited to the "holder" concept, or...

I think people enjoy the feeling of safety, knowing their fingerprint is required to present a credential, because similar to imagining someone forging an ink signature, it feels safer to...

I suggest removing this, and allowing it to be handled in "decentralized extensions".

This PR is ancient and should be closed.

This PR should be closed.