Please see:
https://github.com/decentralized-identity/presentation-exchange/issues/234
The TLDR, JSON-LD frame's are used to derive credentials in both:
The VC-HTTP-API:
https://github.com/w3c-ccg/vc-http-api/blob/cffd942b53ce92c9fb3d86ced62e6cb70e4f276a/holder.yml#L120
and in ACA-py:
https://github.com/hyperledger/aries-cloudagent-python/blob/34c554440c6eb05c671ffa827b3a72075486e0ae/aries_cloudagent/protocols/present_proof/dif/pres_exch_handler.py#L504
The DIF Presentation Exchange Specification is taking feedback from the
OIDF and other communities on the current version of the spec:
https://identity.foundation/presentation-exchange
I am writing this list to ask for your support in adding frame as an
optional member to the presentation definition object, described by the
JSON schema in the first link (issue-234).
JSON-LD frames are also being supported in "CHAPI request by frame flows"
using the https://w3c-ccg.github.io/credential-handler-api/ and the
"VC-HTTP-API cross trust domain presentation exchange endpoints".
Adding support for frames in Presentation Exchange is an important aspect
of standardizing privacy preserving selective disclosure of verifiable
credentials that conform to the W3C VC Data Model.
Regards,
OS
--
*ORIE STEELE*
Chief Technical Officer
www.transmute.industries
<https://www.transmute.industries>