Skip to content

WG 2022 08 01

Jump to bottom
Stephen Curran edited this page Aug 1, 2022 · 2 revisions

Agenda

Time: 7:00 Pacific (fixed), 16:00 CET

Zoom Link: https://us02web.zoom.us/j/85188125213?pwd=UHRUVlgweFJ0T0g4SVdDUytYSkxJUT09

Recording: https://youtu.be/RqOjresLfI4

Preliminaries

Main Agenda

  • Open PRs Review
    • Ledger Agnostic AnonCreds -- AnonCreds Objects Methods Registry
      • Add section on registering/resolving AnonCreds Objects and adding a Method Registry
      • Make identifiers URIs
        • Yes, but...we have to deal with legacy identifiers. Try to dance a line on future identifiers being URIs, but the Indy AnonCreds identifiers are permitted.
      • Update the spec. to v1.0 since our goal with the 1.0 spec. is ledger agnosticism.
        • Good idea, but important to have a v0.1 spec.
        • Challenge working on two versions of the spec at once, when so much is the same -- especially the hard stuff - the cryptography.
        • Compromise: working on the v1.0 spec, but we'll derive and publish a v0.1 spec. after completing the v1.0 spec.
          • Use an issue to track the changes needed to derive a v0.1 spec. -- @swcurran to create issue and PR to do the change.
      • AnonCreds Objects as DIDDocs?
        • Not the current plan, as that is not easy to do. Rather, to have them as "resources" associated with a ledger and document the AnonCreds Objects method for registering/resolving those resources, perhaps in the DID Method, perhaps in a separate document.
        • Ankur and Drummond working on "DIDs for resources" that might resolve this.
      • While it will be relatively easy (it appears) to update the Aries Framework implementations of AnonCreds to add a resolver, current controllers do take advantage of the overloading of the identifiers to included the name and version of the schema in the schemaID, and the tag of the CredDef in the CredDef Id. Those are used in displaying credentials.
        • Ankur to look at whether those values are in the objects themselves, and if not, how to add them.
    • New terminology section - to be reviewed and (if appropriate) merged
    • New section on verifiable presentations being derived from verifiable credentials. Needs to be updated after the terminology PR merge.
  • Action Items
    • @swcurran - PR for AnonCreds Data Flow section updates.
    • @swcurran - extending AnonCreds Objects Methods section to cover general "ledger agnostic" updates in spec.
    • Ankur on ensuring the data from the legacy identifiers are available to the controller.
  • What's left?
    • To Dos:
      • Cred Def Generation + PRIVATE_CRED_DEF -- non revocation, and plus revocation
      • Revocation data elements -- definition
      • Security and Privacy
        • Propose start from those in the indy-did-method specification -- Not applicable.
        • @hkny to do a first cut of this.
      • Normative/Non-normative references
        • Collect from documents mentioned below (under action items) and from previous meetings
        • @ale-linux to do a first cut of this.

Action Items From Previous Meetings:

Clone this wiki locally