22 |
35 |
36 |
23 |
34 | Credential Handler API Demo (Issuer)
24 | 25 |26 | By clicking 'Accept' on page load, you have registered this page with your 27 | browser, and now it can act as a test wallet. 28 |
29 |30 | You can now test the Credential Handler API by requesting to be issued a 31 | credential, below. 32 |
33 |
37 |
119 |
120 |
168 |
169 |
170 |
171 |
--------------------------------------------------------------------------------
/docs/chapi/install.js:
--------------------------------------------------------------------------------
1 | /*!
2 | * Copyright (c) 2019 Digital Bazaar, Inc. All rights reserved.
3 | */
4 | /* global navigator, window, document */
5 | 'use strict';
6 |
7 | const workerUrl = 'https://identity.foundation/interoperability/chapi/worker.html'
8 |
9 | async function installHandler() {
10 | console.log('Loading polyfill...');
11 |
12 | try {
13 | await credentialHandlerPolyfill.loadOnce();
14 | } catch(e) {
15 | console.error('Error in loadOnce:', e);
16 | }
17 |
18 | console.log('Polyfill loaded.');
19 | // document.getElementById('loadingText').innerHTML = 'Polyfill loaded.';
20 |
21 | const registration = await WebCredentialHandler
22 | .installHandler({url: workerUrl})
23 |
24 | await registration.credentialManager.hints.set(
25 | 'test', {
26 | name: 'TestUser',
27 | enabledTypes: ['VerifiablePresentation', 'VerifiableCredential', 'AlumniCredential']
28 | });
29 | }
30 |
31 | function ready(fn) {
32 | if (document.readyState !== 'loading'){
33 | fn();
34 | } else {
35 | document.addEventListener('DOMContentLoaded', fn);
36 | }
37 | }
38 |
--------------------------------------------------------------------------------
/docs/chapi/wallet-ui-receive.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
38 |
117 |
118 |
18 |
89 |
90 |
116 |
117 |
118 |
119 |
--------------------------------------------------------------------------------
/docs/chapi/wallet-ui-store.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
19 |
39 |
20 |
35 |
36 |
37 |
38 | Wallet UI (demo)
21 | 22 |As an Issuer, you have no control over what this UI looks like.
23 | 24 |Would you like to store this Credential?
25 |26 | When the user is issued a credential, the wallet confirms this operation 27 | with the user. 28 |
29 | 30 |31 | When you click Store, this Credential will be stored in your 32 | digital wallet. 33 |
34 |
40 |
88 |
41 |
84 |
85 | Store Credential
86 |
87 |
18 |
40 |
41 |
71 |
72 |
73 |
74 |
--------------------------------------------------------------------------------
/docs/chapi/worker.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
19 |
28 |
20 |
22 | store() event
21 |
23 | Reply:
24 | 25 | 26 |
27 | 24 | 25 | 26 |
29 |
36 |
30 | from:
32 |
33 | hint key:
35 |
37 |
38 |
39 | 
37 |
--------------------------------------------------------------------------------
/documentation.md:
--------------------------------------------------------------------------------
1 | # Interoperability WG Documentation Guidelines
2 |
3 | [](https://hackmd.io/K5BWQ_rvSTKJ-BxeWINYfw)
4 |
5 | [**Homepage of WG**](https://identity.foundation/inteorperability/) | [**Issues**](https://github.com/decentralized-identity/interoperability/issues) | [**Meeting Recordings/Transcripts**](https://dif.groups.io/g/interop-wg)
6 |
7 | ## Agendas and minutes
8 |
9 | Agendas for future meetings and minutes of past meetings are assembled in a running [document](agenda.md) in the root of the group's github repository. It is "live-edited" during workinggroup meetings (turning that meeting's agenda into minutes) in a collaboration tool that supports markdown and simultaneous editing (at time of press, that's hackmd.io).
10 |
11 | Although the group is not IPR protected and is entirely open to the public, we still strive to create an environment of respect and attribution, so if you feel the chairs are not crediting speakers or putting enough detail into the minutes, attendees are encouraged to contribute, embellish the minutes with links, fix typos, etc etc.
12 |
13 | ## Archival multi-media completeness
14 |
15 | When in-meeting discussion involves screensharing videos, images, slideshows, task boards, diagrams, etc, we will do our best to get a copy of these files and upload them to the archival record of the group by copying these input documents to the /assets/ folder where appropriate and linking to them from the minutes. As above, feel free to email the chairs if you notice an oversight or a lapse in this policy!
16 |
17 | ## Recordings of meetings
18 |
19 | As per DIF general policy, all meetings should be recorded and hosting on DIF web space to allow members and non-members alike to watch them at their leisure. The link above should lead you to the recordings to date.
20 |
--------------------------------------------------------------------------------
/parking-lot.md:
--------------------------------------------------------------------------------
1 | # Discussion Items for next Chairs meeting
2 | * We have source for demos and proofs of concepts, the most recent substantive change being Feb 2020 across all of them.
3 | We are continuously getting security warnings from GitHub because of issues with these projects.
4 | We should externalize code projects in our repo (and likely archive). DW is reaching out to authors to determine if they prefer another option (such as pointing to a maintained authoritative version, or investigate creating a work item for it underneath the Interop WG)
5 | * (done) Talked with Orie, agreed they should just be deleted. The projects actually predate the formation of the WG, so they likely have ambiguous IPR.
6 | * Go over core documentation in our repo to remove things which are not a focus/not true anymore
7 | * Replace main "notion" page for Interop WG with content either on the DIF page or Github main page
8 | * Create a skeleton agenda for meetings, e.g.
9 | * Call to order
10 | * Current meeting topic and agenda
11 | * Announcement of future interoperability meetings and recap of previous week
12 | * (Call for) announcements of other interoperability-related topics
13 | * Main meeting agenda
14 | * DW: Status on PoC of github infrastructure revisions
15 |
16 | # "Parking lot" for future/recurring agenda items
17 |
18 | ## Fresh topics
19 |
20 | * Kaliya: WACI what WACI how?
21 | * IIW Discussion on what we want to do there and potentially cancelling the meeting that week, or merge into agenda at IIW.
22 | * IIW interop AMA session, what can we do to make things better for the community
23 | * DIDComm realease on IIW, do we want to play off of that?
24 |
25 | ## Educational presentations
26 |
27 | * Disposable Identities (Adam Burns is on the hook)
28 | * Revocable Anonymity
29 | * What the heck is a synthetic identity? (Michael Shea is up to date on fraud research) - Ping Identity might want to speak to it? or Jan Lindquist's privacy and risk WG in ToIP
30 | * Interop liabilities and new attack surfaces
31 | * VC Auth versus ZCap-LD (CCG), ACDC TF (& some day spec?) ToIP -
32 | * x509 worldwide - Finema, Spherity, Discipl, ...?
33 | * eIDAS roundtable - Nacho Alamillo, Gataca, Peter Wagner, Erik van Zuuren...?
34 | * EDV Use Cases v2 - Manu?
35 | * Cloud Wars and [Gaia-X](https://www.gaia-x.eu/) - ...?
36 | * What's the BlueSky of LinkedIn? EuroPass, Affinidi, LER...
37 | * Ongoing interop efforts
38 | - `JWS test suite` - https://blog.identity.foundation/dif-grant-1-jws-test-suite/
39 | - `vc-jwt-interop` - https://github.com/w3c-ccg/community/issues/198
40 | - `VC-HTTP-API` -
41 | - Aries-interop.info -
42 |
43 | ## Meta-topics, potential quarter-wide or year-long goals
44 |
45 | * Venn diagram of interop goals, and scopes/definitions of interop (contextual)
46 | * Don't lose focus on the map model! [link](https://github.com/decentralized-identity/decentralized-identity.github.io/blob/master/assets/crosscommunity-architecture-survey-oct-2020.pdf)
47 | * Parallelize (and promote) interop work on totally different scopes
48 | * Proposed Work Item: **Architectural guidelines**: "if your role in the ecosystem includes X, looks at ABC specs and make sure you speak D and F to maximize interoperability (and/or future-compatibility)"
49 | * Incorporate/consider [ToIP TIPs](https://github.com/trustoverip/technology-stack-wg/blob/master/TIP_LIFECYCLE_MANAGEMENT.md) and [OIX interop study](https://twitter.com/pamelarosiedee/status/1339223733303570432)
50 | * Human-centric interop as roadmap and business strategy (+ UX?)
51 | * Further afield usecases (VC-free, DID-free, human-free, LEI, etc)
52 | * Non-human decentralized identity?
53 | * Interop test suites and harness infrastructure (after March when SVIP/CCG interop sprint ends)
54 | * Notary models and adoption hacks? (governance?)
55 |
56 | * VCs versus VPs - is habituating individuals to exchanging strong credentials a dark pattern per se? how to keep VPs ephermal and useless to traffic analysis?
57 | * Revocable anonymity? Court orders?
58 | * Adrian's question: do too many VC mental models and specs *assume* VCs going straight from issuer to holder, never issuer to verifier on direct behalf of holder?
59 | * Periodic checkins on the multi-ledger (and possible multi-method!?) Indyverse
60 |
61 | * --- **TEST SUITEAPALOOZA 2020** --- [**F2F? align with SVIP and/or ESSIF?**]
62 | * Later in December?
63 | * Status update on SVIP's past and future suite maintenance
64 | * Aries and/or BCGov test suites
65 | * Can someone from Danube or IBM show the smoke tests run against driver updates to the universal resolver?
66 | * Any volunteers have internal compliance/smoke tests they want to show? (A quick video recording would also be great if timezones are brutal!)
67 |
--------------------------------------------------------------------------------