The W3C Credentials Community Group

Meeting Transcriptions and Audio Recordings (2014-today)

Go Back

Verifiable Credentials HTTP API Telecon

Minutes for 2021-08-24

Agenda
https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0348.html
Topics
  1. Authorization Requirements
  2. Call next week
  3. Trinsic API Presentation
  4. VC HTTP API Renaming Poll Results
Organizer
Wayne Chang, Heather Vescent, Mike Prorock
Scribe
Present
Mahmoud Alkhraishi, Joe Andrieu, Adrian Gropper, Michael Herman, Manu Sporny, Mike Prorock, Sudesh, Justin Richer, Michael Boyd, Sze Wong, Eric Schuh, Markus Sabadello, Rolson Quadras, Ted Thibodeau, Brent Zundel, David Chadwick, Juan Caballero, Marty Reed, Charles E. Lehner, Adrian Hope-Bailie
Audio Log
<justin_richer> Request to the chairs to add an item to the agenda about authorization language.
Justin Richer: :+1:
<michael_herman_(trusted_digital_web)> I might have been firsst
Manu Sporny: Welcome everyone to the VC HTTP API call, Markus is scribing.. Today on the agenda: [scribe assist by Markus Sabadello]
<justin_richer> 5 min
Manu Sporny: Agenda review, introductions, request by Justin on authorization language, then presentation by Trinsic with walkthrough of their API [scribe assist by Markus Sabadello]
Manu Sporny: At the end of the call, we'll go over the renaming poll results (without making a final decision) [scribe assist by Markus Sabadello]
Manu Sporny: Any updates/changes to the agenda? [scribe assist by Markus Sabadello]
Manu Sporny: Let's do introductions.. Michael? Others? [scribe assist by Markus Sabadello]
Michael Boyd: I have been in decentralized identity for about 3 years, first with Nathan George at Sovrin. Some of us met and founded Trinsic and have been building tools for developers to easily add SSI into their applications. [scribe assist by Markus Sabadello]
Michael Boyd: I'm an engineer at Trinsic, I like bicyling and cooking. [scribe assist by Markus Sabadello]
Manu Sporny: Anyone else? [scribe assist by Markus Sabadello]
Markus Sabadello: Sudesh: I'm from SecureKey, working on Trustbloc and Aries, been working in digital identity for 3 years, interested in VC HTTP API, wallets, and Aries protocol.
Markus Sabadello: Rolson_Quadras: Working on HL Aries Framework Go, I've used VC HTTP API, this is my first time in the call.
Manu Sporny: Let's get into the agenda, Justin what do you want to talk about? [scribe assist by Markus Sabadello]

Topic: Authorization Requirements

Justin Richer: I dropped a link, I spend some time writing up text on resolutions that were being passed around, and people arguing about what MUST meant. [scribe assist by Markus Sabadello]
Justin Richer: It's always confusing when there is normative text for spec writers but not implementers [scribe assist by Markus Sabadello]
Justin Richer: If you read through the text, the top paragraph says since it's an HTTP API, you are allowed to use any technology that can protect such an API. It's recommended to use standard delegation technologies rather than direct authentication. [scribe assist by Markus Sabadello]
Justin Richer: Every endpoint would define a set of elements that describe the kinds of access. I talked about this when I introduced RAR/GNAP [scribe assist by Markus Sabadello]
Justin Richer: Neither of those are required to implement or deploy or use. But it says IF you are doing this or that, then you have to support a specific profile. [scribe assist by Markus Sabadello]
Justin Richer: In addition to text in that branch, I also looked into what it takes to add parameters to endpoint specifications. [scribe assist by Markus Sabadello]
Justin Richer: It turns out Redoc does not allow for extensibility. [scribe assist by Markus Sabadello]
Justin Richer: I found no way to put in extensions in the way that OpenAPI allows you to do it. [scribe assist by Markus Sabadello]
Justin Richer: If the group continues to use Redoc, this will be a limitation [scribe assist by Markus Sabadello]
Justin Richer: The text tells you, this is the authorization type field, these are the actions and what it means. [scribe assist by Markus Sabadello]
Justin Richer: This is the full extent that the specification should define, it does not talk about concrete technical details. [scribe assist by Markus Sabadello]
Mike Prorock: NB: Redoc has limitations, there are multiple options for rendering openapi docs
Justin Richer: I've been arguing that this will really help interoperability [scribe assist by Markus Sabadello]
Manu Sporny: Thanks for writing up something concrete that the group can discuss. [scribe assist by Markus Sabadello]
Manu Sporny: My expectation is that the group will discuss this [scribe assist by Markus Sabadello]
Manu Sporny: We will be picking up the authorization discussion in the future, that should not stop people from talking about it e.g. in Github. [scribe assist by Markus Sabadello]
Justin Richer: I could turn it into a PR, but hesitated due to discussion [scribe assist by Markus Sabadello]
<tallted> +1000 -- written text is awesome step in right direction
<mprorock> DRAFT PR might be helpful
Manu Sporny: It would be helpful if people can comment directly on the lines [scribe assist by Markus Sabadello]
<mprorock> Manu I can run it
Manu Sporny: Moving on to the next item.. I won't be able to run the call next week. Any volunteers to run the call next week? [scribe assist by Markus Sabadello]
Mike Prorock: +1 Coordination - probably issues and PRs

Topic: Call next week

Justin Richer: @Mprorock: I noticed that. I actually hacked ReDoc to do the display of the additional fields so I know it's at least possible to represent in the data model.

Topic: Trinsic API Presentation

Manu Sporny: Next topic is Trinsic API presentation. Michael you can screenshare, etc. however you want it. We should timebox 15 min, then have Q&A. [scribe assist by Markus Sabadello]
<mprorock> @Justin yeah, it is pretty slick but requires a bit of hacking for some things
Michael Boyd: I want to talk about our API and some decisions we have made. [scribe assist by Markus Sabadello]
Michael Boyd: Trinsic is a developer-focus company that has built a set of APIs and SDKs and a developer dashboard that we call "Credential Studio". People can create organizations that then can operate as Issuers and Verifiers. [scribe assist by Markus Sabadello]
Michael Boyd: We implement HL Aries .net framework to enable all of this, and we have also built a mobile wallet. [scribe assist by Markus Sabadello]
Michael Boyd: There is also a Trinsic Wallet API. [scribe assist by Markus Sabadello]
Michael Boyd: This technoloy enables a really easy way for Issuers, Verifiers and Holders to get up and running with credentials, without any configuration required. [scribe assist by Markus Sabadello]
Michael Boyd: E.g. I can create a connection invitation and then scan it with a mobile wallet. [scribe assist by Markus Sabadello]
Michael Boyd: I can create HL Indy credential definitions, on the Sovrin ledger. [scribe assist by Markus Sabadello]
Michael Boyd: I can create this, then issue it to a wallet. [scribe assist by Markus Sabadello]
Michael Boyd: The whole interface was completely built using our own public APIs. [scribe assist by Markus Sabadello]
Michael Boyd: We're happy with our developer documentation. [scribe assist by Markus Sabadello]
Michael Boyd: In our API, we have three main API concepts. Credential API, Wallet API, and Provider API. [scribe assist by Markus Sabadello]
Michael Boyd: Connections and credentials we use with organizations are all in the Credentials API. We made it specificially for Issuers and Verifiers. This is probably most aligned with the VC HTTP API. [scribe assist by Markus Sabadello]
Michael Boyd: For Holders, we defined a Wallet API, which gives you the functionality of a mobile wallet, but in a custodial cloud environment. [scribe assist by Markus Sabadello]
Michael Boyd: We had a lot of customers requesting this, especially in uses cases where there is no mobile wallet. [scribe assist by Markus Sabadello]
Michael Boyd: We used this in a project with farmers. [scribe assist by Markus Sabadello]
Michael Boyd: After working with 100s of developers and 10s of customers going in production, we realized a lot of our customers are "providers" that are helping others onboard into an ecosystem. [scribe assist by Markus Sabadello]
Michael Boyd: The Provider API allows a company to create organizations en masse, and each organization can have a custodial cloud wallet. [scribe assist by Markus Sabadello]
<justin_richer> A note for the notes, I updated the PR with screenshots from the hacked version of ReDoc I threw together: https://github.com/w3c-ccg/vc-http-api/pull/226
Michael Boyd: Using this set of API endpoints, you can create a complete production ecosystem without any configuration needed. [scribe assist by Markus Sabadello]
Michael Boyd: I wanted to spend time talking about some of our decisions, specifically regarding the Credentials API. [scribe assist by Markus Sabadello]
Michael Boyd: As I said, we're following the HL Aries protocols and using DIDComm. [scribe assist by Markus Sabadello]
Michael Boyd: All of our semantics are closely aligned with HL Aries. Most exchanges start with a "connection". This uses Aries connection invitation protocol. [scribe assist by Markus Sabadello]
Michael Boyd: We found a lot of our customers like the "connections". It abstracts away the credential exchange from their infrastructure. [scribe assist by Markus Sabadello]
Michael Boyd: We are finding that customers want simple entry points, to make it easy to use. [scribe assist by Markus Sabadello]
Michael Boyd: In general, as technologists we value flexibility and robustness of features. [scribe assist by Markus Sabadello]
Michael Boyd: This is also the case for some of our power users. People want "60 minites to Wow". [scribe assist by Markus Sabadello]
<markus_sabadello> s/minites/minutes
Michael Boyd: I don't know where the VC HTTP API stops in terms of scope, but we found that connections are very valuable. [scribe assist by Markus Sabadello]
Michael Boyd: We also enabled connection-less credentials, e.g. if organizations want send a QR code via email to send a credential, they could do that as well. [scribe assist by Markus Sabadello]
Michael Boyd: In our Credentials endpoints, we abstracted a lot of the VC data model away from customers [scribe assist by Markus Sabadello]
Michael Boyd: We tried to find the right balance between abstraction and original data model. This is very tricky to figure out. [scribe assist by Markus Sabadello]
Michael Boyd: In our first API, we've chosen to be very "helpful" to our users, we abstract complexity away. [scribe assist by Markus Sabadello]
Michael Boyd: E.g. we define CRUD endpoints for all credentials, we enable organizations to store all credentials in a cloud wallet. [scribe assist by Markus Sabadello]
Michael Boyd: We have given users credential IDs to store on their end, if they want to have data self-hosted, they could choose to store all credentials in their own environment and delete them from the Trinsic backend. [scribe assist by Markus Sabadello]
Michael Boyd: We chose to make things easy to use and abstracted [scribe assist by Markus Sabadello]
<manu_sporny> mprorock, I see you... holding until 15 minutes is up and then I'll see if Michael wants to take questions.
Mike Prorock: +1 Manu - it is an if we have time
Michael Boyd: E.g. for an offer, you supply a credential definition. You can create that and then offering a credential is as simple as putting a credential ID and connection ID, and then adding the values. [scribe assist by Markus Sabadello]
Michael Boyd: All values are text type, we don't have specific field types at this point. [scribe assist by Markus Sabadello]
Michael Boyd: For the audience here, let's make this based on questions. I'm also interested in what areas others find most interesting, then let's have a discussion on shared learnings to build better APIs. [scribe assist by Markus Sabadello]
Manu Sporny: This sounds great. Let's use our queuing system. Anyone who wants to ask questions, please add youself to the queue. [scribe assist by Markus Sabadello]
Mike Prorock: I'm also super impressed by this. We've done similar abstraction in our products to make it easy to onboard. [scribe assist by Markus Sabadello]
Michael Boyd: Noone has asking for this [low-level access to semantics?], it wouldn't be complex to implement, but our organization users haven't really found this valuable yet. [scribe assist by Markus Sabadello]
Michael Boyd: Your users should be able to export and import credentials, to avoid vendor lock-in [scribe assist by Markus Sabadello]
Michael Boyd: HL Aries/indy stack don't really use the VC data model behind the scenes. They don't use contexts and linked data. [scribe assist by Markus Sabadello]
Markus Sabadello: Michael_Herman: I'm a client and developer using the Trinsic API, and it's easy to use.
Markus Sabadello: Michael_Herman: If every store wanted to be enabled to do purchase orders and invoices, how would this scale to be pervasive across the work?
Markus Sabadello: Michael_Herman: Does everybody have to become an Issuer?
<justin_richer> . o O ( My Cabbages! )
Markus Sabadello: Michael_Herman: If one store wants to send a purchase order to another store, do they have to become an Issuer? How do we make this scale for everyday business transactions?
Michael Boyd: It's useful to build the piping, the roads of an infrastructure, then let industry partners go and help provider more of a frontend experience to customers. [scribe assist by Markus Sabadello]
Michael Boyd: Would a grocery store have to be an Issuer? Depends, answer is probably yes, but they would probably be dealing with some frontend vendor software rather than VC data model directly. [scribe assist by Markus Sabadello]
Michael Boyd: I forsee APIs such as ours to be integrated with other systems across the world. This is why we mentioned the "Provider" concept. The majority of our customers want to "own" the experience, we're giving them the tools to suceed. [scribe assist by Markus Sabadello]
Markus Sabadello: Michael_Herman: I imagine add-ons to existing software that can issue VCs
Adrian Gropper: You mentioned messaging-oriented design with credentials going through DIDComm or email [scribe assist by Markus Sabadello]
Adrian Gropper: Is there any authorization component in your stack (Studio), or are you assuming there will be a frontend that might or might not have authorization. When you do it the way you did, does it matter to the Issuer whether they talk to the Holder of the Verifier? [scribe assist by Markus Sabadello]
Adrian Gropper: If it's messaging-oriented, I imaging it makes no difference if they communicate with Holder or Verifier. [scribe assist by Markus Sabadello]
Michael Boyd: Talking to you about authorization is a pleasure [scribe assist by Markus Sabadello]
Michael Boyd: We use bearer tokens for each organization as authorization. [scribe assist by Markus Sabadello]
Michael Boyd: For Aries/DIDComm that is done behind the scenes. We are talking about authorization to the API itself, and beyond that is DIDComm with mutually authenticated connections. [scribe assist by Markus Sabadello]
Mike Prorock: +1 This is very standard for auth approach for api services
Michael Boyd: Our bearer tokens are using our own identity provider endpoint. [scribe assist by Markus Sabadello]
Michael Boyd: We are looking at ZCAP-LD for future implementations of our API; at this point though it's just the bearer token itself that enables a client or server-side caller to authenticate to our API [scribe assist by Markus Sabadello]
Michael Boyd: The same goes for verifying a credential; they will authenticate with bearer token and then use the API endpoints. [scribe assist by Markus Sabadello]
Michael Boyd: For the Holder, that is completely done using DIDComm. The wallet is standalone, no dependency on our backend services. They have a push notification service behind the scenes. [scribe assist by Markus Sabadello]
Michael Boyd: Those are authenticated in headers at the endpoints. [scribe assist by Markus Sabadello]
<mprorock> "active"
Manu Sporny: Michael, there has been a heated discussion on authorization. I'm wondering if what Michael said is acceptable to you agropper, or if you are still concerned about sovereignty. [scribe assist by Markus Sabadello]
Adrian Gropper: I'm entirely focused on the ability of the subject to delegate. [scribe assist by Markus Sabadello]
Adrian Gropper: To the extent that Trinsic Studio doesn't force subjects to be holders, I'm completely aligned with that. [scribe assist by Markus Sabadello]
Adrian Gropper: In what I am proposing, I want to separate posession from control, and allow for delegation of the control component. [scribe assist by Markus Sabadello]
Adrian Gropper: The right to delegate as a human right is what ties together my insistence. [scribe assist by Markus Sabadello]
Adrian Hope-Bailie: Then why are you pushing back on VC-HTTP-API which has the exact same system to system needs as we see here [scribe assist by Mike Prorock]
Joe Andrieu: +1 Organizations are not people
Michael Boyd: We've taked an approach of "organizations are not people", this has helped us move forward. Issuers and verifiers are different enties than Holders. [scribe assist by Markus Sabadello]
Michael Boyd: With the Wallet API, this is a custodial relationship under an organization. An organization can have many wallets. [scribe assist by Markus Sabadello]
<manu_sporny> Citizens United v. Federal Election Commission would like to have a few words with you, Joe. :P
<mprorock> lol
Michael Boyd: For farmers authentication/authorization in one part of the world is probably not the same as for me in a different part of the world. [scribe assist by Markus Sabadello]
Manu Sporny: My question is about coordinating. Michael you asked how can we learn from each others. [scribe assist by Markus Sabadello]
Manu Sporny: In the Trinsic API, there are some endpoints that seem to map cleanly to VC HTTP API endpoints [scribe assist by Markus Sabadello]
Manu Sporny: The other discussion is about authorization. I think I heard you say you use bearer tokens for all endpoints module the wallet holder DIDComm part [scribe assist by Markus Sabadello]
Manu Sporny: Is is OAuth2 client credentials, is it some kind of OIDC based flow to the the bearer token? [scribe assist by Markus Sabadello]
<mprorock> are you using auth0 or okta?
Michael Boyd: I believe they are just client credentials, signed tokens that have an expiration date of I think one year; they are stored in a secure location and sent alongside the request. I don't think it's OIDC. [scribe assist by Markus Sabadello]
<justin_richer> one year token expiration? ��
Manu Sporny: The other question is maybe more important. I think I heard you say you focus on a simple, holistic product. [scribe assist by Markus Sabadello]
Manu Sporny: Is there any interest in Trinsic v2 API to align with VC HTTP API, or do you first focus on your customers and it's not necessarily a goal to align? [scribe assist by Markus Sabadello]
Michael Boyd: I'm interested in understanding the specific use cases, I didn't explore that before the call. I'd like Issuers and Verifiers to use open-source and use different vendors. [scribe assist by Markus Sabadello]
Michael Boyd: We'll likely see a dual approach where you can have an endpoint to issue a credential that is very abstracted [scribe assist by Markus Sabadello]
Michael Boyd: We're separating "Trinsic Core" and "Trinsic Ecosystems". Latter is a platform, former is a set of tools [scribe assist by Markus Sabadello]
Michael Boyd: We'll use the standardized specifications in our core side, and then we'll support more application-specific scenarios. [scribe assist by Markus Sabadello]
Michael Boyd: Yes we want to standardize and align with people, but we will have ecosystems products on top of that. [scribe assist by Markus Sabadello]
Manu Sporny: Interesting how you've broken up the APIs into those two groups. The Providers API seem really interesting. [scribe assist by Markus Sabadello]
Manu Sporny: Do you have any thoughts on which parts of those need to be standardized, and which parts don't? Maybe the ecosystems layer is value-add where vendors compete? The other approach is standardize everything [scribe assist by Markus Sabadello]
Michael Boyd: I resonate more with the first approach. I think having good tooling is a value-add for developers [scribe assist by Markus Sabadello]
Michael Boyd: With great tooling we achieve great adoption. [scribe assist by Markus Sabadello]
<mprorock> default expire for a new provider key i am creating now was set to "08/24/2024"
Michael Boyd: Tools that actually work and are easy to use. I'm thinking about how Docker gained such a following (largely due to tools) [scribe assist by Markus Sabadello]
Michael Boyd: Trinsic and others can then provide more of a platform, analogous to DockerHub [scribe assist by Markus Sabadello]
Michael Boyd: Do we want people to be locked in? No. But we do want to achieve real-world adoption, for that we need a healthy ecosystem of vendors to serve customers. [scribe assist by Markus Sabadello]
Michael Boyd: I like to solve customer products on a broad scale with products. [scribe assist by Markus Sabadello]
Michael Boyd: So I see this as a two-tiered approach [scribe assist by Markus Sabadello]
<mprorock> this was great!
<juan_caballero_(spruce)> thanks michael! this was great!
<michael_herman_(trusted_digital_web)> +1000
Manu Sporny: This is an example of really great API documentation. Thank you for coming, hopefully we will see more from Trinsic in the coming years. [scribe assist by Markus Sabadello]
Michael Boyd: I would love to learn from everyone here, and I hope we can learn from each other. michael@trinsic.id feel free to reach out. [scribe assist by Markus Sabadello]

Topic: VC HTTP API Renaming Poll Results

<manu_sporny> Poll results are here: https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0297.html
Manu Sporny: We sent a pool to the community to get some thoughts on what the name could be. [scribe assist by Markus Sabadello]
Manu Sporny: We have one objection on the poll, which means the editors will have to make a call, or the chairs and the CCG will have to make a call there. [scribe assist by Markus Sabadello]
Manu Sporny: But today we can go through the results so far [scribe assist by Markus Sabadello]
Manu Sporny: We went out to the community and asked what they wanted to rename the API to. There was good discussion on branding/marketing, with a number of suggestions on what we could do. [scribe assist by Markus Sabadello]
Manu Sporny: I'll share my secreen [scribe assist by Markus Sabadello]
Manu Sporny: 26 People voted in the poll. [scribe assist by Markus Sabadello]
Manu Sporny: Top picks were VC-API, VCX, VC HAPI [scribe assist by Markus Sabadello]
Manu Sporny: Most disliked names were also voted on. [scribe assist by Markus Sabadello]
<justin_richer> three cheers for Veri McCredentialFace
Manu Sporny: We used the Borda Count method (this is used whenever people are trying to pick their favorite option) [scribe assist by Markus Sabadello]
Manu Sporny: Pretty strong support for 3-5 items here, rest of them didn't get much support [scribe assist by Markus Sabadello]
Manu Sporny: It was good to get that data. The data has been uploaded to the mailing list. People can check the raw data. [scribe assist by Markus Sabadello]
Manu Sporny: Any thoughts on this? Surprises on what ended up being ranked highly, or anything interesting about the results? [scribe assist by Markus Sabadello]
Manu Sporny: I'm interested in how "VC API" got the highest results. [scribe assist by Markus Sabadello]
Manu Sporny: I was expecting other things that are more descriptive. [scribe assist by Markus Sabadello]
<justin_richer> fwiw this is not a transport protocol: "transport protocol" means something very specific in the networking world
Mike Prorock: Sad that Veri McCredentialFace is not on top :) [scribe assist by Markus Sabadello]
Mike Prorock: Interesting to have this non-binding poll, it's really useful feedback. [scribe assist by Markus Sabadello]
Mike Prorock: Having 26 votes is quite in line with active engagement numbers in the community. [scribe assist by Markus Sabadello]
Mike Prorock: At the same time, VC API it does seem a bit descriptive, it does seem to kind of make sense. I wasn't sure how the "transport"ly names would do. [scribe assist by Markus Sabadello]
Manu Sporny: Any last minute thoughts? [scribe assist by Markus Sabadello]
Manu Sporny: Thank you everyone, thank you Markus for scribing and Michael for presenting Trinsic API. [scribe assist by Markus Sabadello]
Manu Sporny: Next week mprorock will be running the call. [scribe assist by Markus Sabadello]
Manu Sporny: Have a wonderful rest of the week, bye [scribe assist by Markus Sabadello]

Meeting for 2019-12-17

Topics

  1. Introductions and Reintroductions
  2. Announcements and Reminders
  3. Action Items
  4. WebKMS

Meeting for 2019-12-10

Topics

  1. Agenda Review
  2. Introductions / Reintroductions
  3. Announcements and Reminders
  4. Progress & Action Items
  5. Verifiable Credentials for Education Task Force

Meeting for 2019-12-03

Topics

  1. Introductions and Reintroductions
  2. Announcements and Reminders
  3. Action Items
  4. did:key method

Meeting for 2019-11-12

Topics

  1. Introductions
  2. Announcements
  3. Action Items
  4. Personal Data Stores Comparison

Meeting for 2019-11-05

Topics

  1. Introductions and Reintroductions
  2. Announcements and Reminders
  3. Review action items and work items
  4. CCG 2020 Scope of work

Meeting for 2019-10-29

Topics

  1. Introductions / Re-Introductions
  2. Announcements
  3. Work Items and Action Items Review
  4. Year End Purge

Meeting for 2019-10-22

Topics

  1. Agenda review
  2. Announcements and Reminders
  3. Action Items
  4. Credential Schema Specification

Resolutions

  1. The W3C Credentials CG supports the rechartering of a Verifiable Credentials Maintenance Working Group.

Meeting for 2019-10-15

Topics

  1. Introductions and Reintroductions
  2. Announcements & Reminders
  3. Progress on Action Items
  4. DID handoff
  5. VC WG Maintenance Charter
  6. Contributing to JSON-LD Contexts

Meeting for 2019-10-08

Topics

  1. Introductions / Reintroductions
  2. Announcements & Reminders
  3. DIDs from a non-technical perspective
  4. IIW Report out

Meeting for 2019-09-10

Topics

  1. Introductions and Reintroduction
  2. Announcements & Reminders
  3. Action Items
  4. Verifiable Credentials next steps
  5. Decentralized Identity Working Group

Meeting for 2019-08-27

Topics

  1. Introductions and re-introductions
  2. DID working group charter / outreach
  3. Datashards
  4. Solid

Meeting for 2019-08-20

Topics

  1. Introductions and Reintroductions
  2. Announcements and Reminders
  3. Decentralized Topics at #RWOT9
  4. BTCR hackathon

Meeting for 2019-08-13

Topics

  1. Announcements and Reminders
  2. DID WG Charter and outreach
  3. Agents, Hubs, and More

Meeting for 2019-07-30

Topics

  1. intros and reintros
  2. announcements and reminders
  3. Progresson action items
  4. Standards setting process

Meeting for 2019-07-23

Meeting for 2019-07-09

Topics

  1. Introductions and Reintroductions
  2. Announcements and Reminders
  3. DID WG Charter Proposal
  4. Non-Violent Communication

Meeting for 2019-07-02

Topics

  1. Introductions and Reintroductions
  2. Announcements and Reminders
  3. Progress on Action Items
  4. Amira

Meeting for 2019-06-25

Topics

  1. Introductions and Re-introductions
  2. Accouncements
  3. Action Items
  4. Work Item Review, Fin

Meeting for 2019-06-18

Topics

  1. Introductions and Reintroductions
  2. Announcements and reminders
  3. Action Items
  4. Work item repair

Meeting for 2019-06-11

Topics

  1. Introductions and Re-introductions
  2. Announcements and Reminders
  3. Action Items
  4. Rubrics Task Force
  5. Credential CG Work Item Process Draft, simplified

Meeting for 2019-05-28

Topics

  1. Introductions and Reintroductions
  2. Announcements & Reminders
  3. Action Items
  4. Discuss New Work Item Process

Meeting for 2019-05-14

Topics

  1. Introductions and Reintroductions
  2. Announcements & Reminders
  3. Action Items
  4. Decentralized Identifier Rubrics

Meeting for 2019-05-07

Topics

  1. Introductions and Re-introductions
  2. Announcements
  3. Action Items
  4. Message from the chairs and ensuring a positive work environment
  5. IIW

Meeting for 2019-04-23

Topics

  1. Agenda review
  2. IP Note, call notes
  3. Introductions and re-introductions
  4. Announcements
  5. Open issues
  6. ABNF Task Force

Meeting for 2019-04-16

Topics

  1. Introductions / Reintroductions
  2. Annoucements and Reminders
  3. Action Items
  4. Survey Results

Meeting for 2019-04-02

Topics

  1. IP notes, call notes,
  2. Introductions & Reintroductions
  3. Announcements & Reminders
  4. Action Items
  5. DID Report out for AC Meeting
  6. Survey results

Meeting for 2019-03-26

Topics

  1. Introductions / Reintoroductions
  2. Announcements
  3. Progress on Action Items
  4. DIF Report Out

Meeting for 2019-03-19

Topics

  1. intros
  2. announcements and reminders
  3. Action items
  4. https DID method spec, and more

Meeting for 2019-03-12

Topics

  1. Introductions and Reintroductions
  2. Annoucements and reminders
  3. Action Items
  4. RWOT8 Report Out

Meeting for 2019-02-19

Topics

  1. Introductions/Reintroductions
  2. Announcements
  3. Action Items
  4. Review ABNF PR

Meeting for 2019-02-12

Topics

  1. Introductions
  2. announcements
  3. Action Items
  4. Use Cases

Meeting for 2019-02-05

Topics

  1. Introductions and Re-introductions
  2. Announcements and Reminders
  3. Work Item Review
  4. DID Issue Review

Meeting for 2019-01-29

Topics

  1. Introductions and Re-introductions
  2. Announcements and Reminders
  3. Action Items
  4. DID Pull Requests

Meeting for 2019-01-22

Topics

  1. Intros
  2. Announcements and reminders
  3. Progress on action items
  4. New work items
  5. Proposed work items
  6. DID Spec PR Triage

Meeting for 2019-01-15

Topics

  1. Introductions
  2. Announcements & Reminders
  3. Progress on Action Items
  4. Work Item Status Review
  5. New Work Items

Meeting for 2019-01-08

Topics

  1. Introductions and Re-introductions
  2. Announcements
  3. Action items
  4. Work items

Meeting for 2018-12-18

Topics

  1. Introductions
  2. Announcements and Reminders
  3. 2018 Year in Review

Meeting for 2018-12-04

Topics

  1. introductions
  2. reintroductions
  3. Announcements and Reminders
  4. DID resolver specification
  5. Work Items
  6. TAG charter review

Meeting for 2018-11-27

Topics

  1. Agenda Review
  2. Introductions / Reintroductions?
  3. Reminders and Events
  4. Progress on Current Action Items
  5. Work Items
  6. Review summary of previous DID stories, questions, painpoints meetings
  7. DID Summary High Points
  8. DID Explainer Template

Meeting for 2018-11-20

Topics

  1. Introductions and Reintroductions
  2. Announcements, reminders
  3. Action items
  4. Work Items
  5. Pain points

Meeting for 2018-11-13

Topics

  1. Introductions and Reintroductions
  2. Announcements
  3. Action Items
  4. Work Items
  5. DID Unique Selling Proposition

Meeting for 2018-11-06

Topics

  1. Introductions
  2. Update on Action Items
  3. Work Items
  4. W3C TPAC 2018
  5. IIW

Meeting for 2018-10-16

Topics

  1. Introductions and Reintroductions
  2. Announcements & Reminders
  3. Progress on Current Action Items
  4. Work Items
  5. TPAC Planning
  6. Feedback on charter

Meeting for 2018-10-09

Topics

  1. Agenda Review
  2. Introductions / Re-introductions
  3. Announcements / Reminders
  4. Progress on Action/Work Items
  5. W3C TPAC Planning.

Meeting for 2018-10-02

Topics

  1. Introductions and Reintroductions
  2. Announcements
  3. Review Action Items
  4. Work Items
  5. New Business
  6. RWoT7

Meeting for 2018-09-18

Topics

  1. Introductions & Reintroductions
  2. Announcements & Reminders
  3. Progress on Current Action Items
  4. Status of work items

Meeting for 2018-08-21

Meeting for 2018-08-14

Topics

  1. introductions and re-introductions
  2. announcements and reminders
  3. Progress on Current Action Items
  4. Progress on current action items
  5. Work items
  6. Jolocom

Meeting for 2018-08-07

Topics

  1. Introductions
  2. Review announcements
  3. Action items
  4. Work Items
  5. proof of personhood

Meeting for 2018-07-24

Topics

  1. Introductions
  2. Agenda Review
  3. Announcements & Reminders
  4. Progress on Current Action Items
  5. Work Items
  6. Amira Use Case

Meeting for 2018-07-17

Topics

  1. Agenda Review and Introductions
  2. Roadmap
  3. DID WG Charter

Meeting for 2018-07-10

Topics

  1. Introductions
  2. Announcements and Reminders
  3. uPort Ethereum DID Method

Meeting for 2018-07-03

Topics

  1. Introductions and Reintroductions
  2. Transparency
  3. Announcements and Reminders
  4. Action Items
  5. Work Items
  6. Focal Use Cases
  7. DID-Auth

Meeting for 2018-06-26

Topics

  1. Introductions
  2. Agenda Review
  3. Announcements & Reminders
  4. Progress on Current Action Items
  5. Work Items
  6. Focal Use Cases for DID WG
  7. Muscians and Influencers

Meeting for 2018-06-19

Topics

  1. Introductions and Reintroductions
  2. Announcements and Reminders
  3. Action Items
  4. Work Items
  5. Requirements for DIDs

Meeting for 2018-06-12

Topics

  1. Agenda review
  2. Introductions
  3. Announcements
  4. Action items - https://github.com/w3c-ccg/community/issues?q=is%3Aissue+is%3Aopen+label%3A%22action+item%22_
  5. Work items
  6. DID Method Requirements?
  7. Focal use cases

Meeting for 2018-06-05

Topics

  1. Introductions
  2. Announcements and Reminders
  3. Progress on current action items
  4. Status of Work Items
  5. Focal Use Cases for DID WG

Meeting for 2018-05-29

Topics

  1. Introductions and Re-Introductions
  2. Wyoming Blockchain Task Force Meeting
  3. Summer Hackathon
  4. Focal Use Cases

Meeting for 2018-05-22

Topics

  1. Introductions/Re-introductions
  2. Announcements and Reminders
  3. Action Items
  4. Work Items
  5. Update on Educational Task Force
  6. Formation of a User Story Task Force

Meeting for 2018-05-15

Topics

  1. Introductions and Reintroductions
  2. Reminders
  3. Progress on Current Action Items
  4. Status of Work Items
  5. Call for DID Focal Use Cases
  6. DID issues working session
  7. DID service naming and identification
  8. DID Document versioning
  9. Extensibility

Meeting for 2018-05-08

Topics

  1. introductions
  2. action items update
  3. work items
  4. digital verification github items
  5. Digital Verification community items and CCG people
  6. DID Use Cases & Domains

Meeting for 2018-05-01

Topics

  1. Reintroductions
  2. Action Items
  3. DID Working Group Transition

Meeting for 2018-04-24

Topics

  1. CCG Process

Meeting for 2018-04-19

Topics

  1. poll results
  2. Peer claims https://hackmd.io/BYWqUeNDRimyKJL5xsSOiw

Meeting for 2018-04-17

Topics

  1. Introductions
  2. Announcements
  3. Issues List
  4. ZK Lang

Meeting for 2018-04-10

Topics

  1. Introductions
  2. Next Week - Crypto Tuesdays - ZKLang
  3. Action Items
  4. MyData Panel at Helsinki
  5. Work items - DID Spec and DID Methods
  6. IIW26 Report Out
  7. Verifiable Claims WG Meeting

Meeting for 2018-04-05

Topics

  1. Occupational and Educational Credentials

Meeting for 2018-03-27

Topics

  1. Introductions / ReIntroductions
  2. Education Credentials Task Force
  3. https://github.com/w3c-ccg/community
  4. DID Auth Follow-up

Meeting for 2018-03-22

Topics

  1. Occupational/Educational Task Force

Meeting for 2018-03-20

Topics

  1. Introductions
  2. Announcements
  3. Current action items progress
  4. Work items
  5. DID-based Authentication (DID-Auth)

Meeting for 2018-03-13

Topics

  1. Introductions
  2. Announcements
  3. Report from Rebooting the Web of Trust 6

Meeting for 2018-02-15

Topics

  1. DID Service URLs
  2. Other DID Spec Items

Meeting for 2018-02-13

Topics

  1. Announcements
  2. DID Authentication
  3. Object Capabilities

Resolutions

  1. Create an Education and Occupational Credentials Task Force as described in https://lists.w3.org/Archives/Public/public-credentials/2018Feb/0013.html
  2. Adopt the Linked Data Object Capabilities specification as a work item.

Meeting for 2018-02-06

Topics

  1. Introductions
  2. Announcements
  3. DID Specification Reconciliation
  4. Crypto Tuesdays
  5. Cryptography Suite Implementations

Meeting for 2018-01-30

Topics

  1. Introductions and Reintroductions
  2. Agenda for Today
  3. Action Items
  4. CG Process
  5. Data Minimization
  6. Education Task Force

Resolutions

  1. Merge PR 41 into the main specification based on no objections, we have achieved consensus on this PR.

Meeting for 2018-01-25

Topics

  1. DID Harmonization PR
  2. Encryption
  3. DID Fragment Identifiers

Meeting for 2018-01-23

Topics

  1. Introduction to Akila
  2. Announcements, Focus for 2018
  3. DID Harmonization
  4. DID Hackathon Outcomes

Meeting for 2018-01-16

Topics

  1. Reintroductions
  2. Announcements
  3. Work Items
  4. Outreach
  5. Work Breakdown Structure (WBS) aka Roadmap Review

Meeting for 2018-01-11

Topics

  1. DID Harmonization
  2. Spec Updates

Meeting for 2018-01-09

Topics

  1. Reintroduction for Kerri Lemoie
  2. Announcements
  3. Progress on current action items
  4. DID Harmonization Proposal #1
  5. Outreach

Meeting for 2018-01-04

Topics

  1. Biometric Authentication
  2. DID Spec Scope?
  3. DID Document Extensibility
  4. Fundamental DID Architecture

Meeting for 2017-12-21

Topics

  1. Cryptographic Key Material

Meeting for 2017-12-19

Topics

  1. Introductions and Reintroductions
  2. Announcements and Status Updates
  3. 2017 Year in Review

Meeting for 2017-12-14

Topics

  1. Current Status of DID Hardening Discussions
  2. Options for Keys / Authentication
  3. Option #D

Resolutions

  2. Eliminate Option #3 from the discussion choices as described in this email: https://lists.w3.org/Archives/Public/public-credentials/2017Dec/0046.html

Meeting for 2017-12-12

Topics

  1. Introductions / Reintroductions
  2. Announcements
  3. Status of Work Items
  4. engagement model
  5. browser api and polyfill
  6. privacy and security requirements
  7. DID Spec Change Requests
  8. Other Topics

Meeting for 2017-12-07

Topics

  1. Intellectual Property Release
  2. Two Stages of DID Document
  3. Simple Arrays of Key Descriptions

Meeting for 2017-12-05

Topics

  1. Agenda Review
  2. Announcements
  3. Introductions
  4. W3C CCG Process Document
  5. W3C Intellectual Property Requirements & our CG Process
  6. CCG Registries

Meeting for 2017-11-30

Topics

  1. DID Hardening Proposal v3
  2. Format Independence
  3. Optional ID Property for the DID

Meeting for 2017-11-14

Topics

  1. Introduction to Mark Miller (Google)
  2. DID Spec Review
  3. Capabilities in Verifiable Credentials
  4. W3C TPAC 2017 Update

Meeting for 2017-10-31

Topics

  1. Status of Action Items
  2. Credential Handler API
  3. W3C TPAC Planning
  4. Post RWoT DID Spec

Meeting for 2017-10-24

Topics

  1. Reintroductions
  2. W3C TPAC
  3. DID Specification
  4. Digital Verification Cryptography
  5. JSON-LD and LD Signature Updates
  6. Credential Handler API
  7. Lifecycle Model
  8. Verifiable News
  9. Other Work Items
  10. Path for DID Spec Standardization

Meeting for 2017-10-17

Topics

  1. Introductions and Reintroductions
  2. New DID Spec PR
  3. Verifiable News
  4. W3C TPAC Planning

Meeting for 2017-09-26

Topics

  1. Introductions
  2. Action Items
  3. Credential Handler Polyfill Video
  4. Data Minimization & Selective Disclosure
  5. DID Specification
  6. Next week

Meeting for 2017-09-19

Topics

  1. Introductions and Reintroductions
  2. Proposed changes to DID Spec Overview
  3. DID Spec Discussion

Meeting for 2017-09-12

Topics

  1. Introductions and Reintroductions
  2. Action Items
  3. Proofs vs. Signatures
  4. Capabilities-based Security Model

Meeting for 2017-09-05

Topics

  1. Agenda Review
  2. Introductions / Re-introductions
  3. Action Item Review
  4. ActivityPub and Mastadon
  5. DID Specification

Meeting for 2017-08-29

Topics

  1. Introductions
  2. Work Item Progress
  3. Privacy and Security Requirements
  4. DID Specification Progress

Meeting for 2017-08-22

Topics

  1. Administrivia - Dialing In
  2. Introductions
  3. Mission Statement Review
  4. Credential Handler API (and polyfill)

Meeting for 2017-08-15

Topics

  1. Introductions
  2. Fake News and Bots
  3. Mission Statement
  4. Administrative Items

Meeting for 2017-08-08

Topics

  1. Introductions and Reintroductions
  2. Agenda Review
  3. Mission Statement

Meeting for 2017-08-01

Topics

  1. Action Items
  2. Introductions and Re-introductions
  3. Update on Community Group Name
  4. Revising the Mission Statement

Meeting for 2017-07-25

Topics

  1. Re-Introductions
  2. Action Items
  3. DID Specification Work Item
  4. Lifecycle Deep Dive

Resolutions

  1. Accept the DID Specification as a Credentials CG work item.

Meeting for 2017-07-18

Topics

  1. Introduction to Lionel Walberger
  2. Action Items
  3. DID Specification update
  4. Cryptography for Anonymous Credentials

Meeting for 2017-06-27

Topics

  1. Introductions
  2. Selective Disclosure and CL Signatures

Meeting for 2017-06-20

Topics

  1. Bitcoin DID Method (BTCR)
  2. Chainpoint v3.0
  3. Linked Data Signatures

Meeting for 2017-06-13

Topics

  1. Introductions
  2. Action Items
  3. Community Group Naming
  4. Interaction with Banking/Finance Industry
  5. Planning for W3C TPAC
  6. Work Item Review
  7. RDF Dataset Canonicalization
  8. Privacy and Security Requirements

Meeting for 2017-06-06

Topics

  1. Introductions
  2. Agenda Review
  3. Action Items
  4. Current Polls
  5. Decentralized Identifiers
  6. Reputation Systems
  7. Next Meeting

Meeting for 2017-05-30

Topics

  1. Community Group Scope and Naming
  2. Verifiable Claims Browser API and Browser Polyfill
  3. Lifecycle of a Verifiable Claim
  4. Data Minimization and Selective Disclosure Report
  5. Decentralized Identifier Spec

Meeting for 2017-05-23

Topics

  1. Introductions
  2. Action Item Review
  3. Future Work Items Discussion

Meeting for 2017-05-16

Topics

  1. Introduce New Chairs
  2. New Members
  3. Review of Credentails CG Mission Statement
  4. Community Group Priorities
  5. Potential Work Items

Meeting for 2017-05-09

Topics

  1. Agenda Review and Introductions
  2. WG Document Handoff
  3. Joining the VCWG
  4. Reminder: this is last CG call at this time
  5. Open Mic / Community Group Next Steps
  6. CG and WG call next week

Meeting for 2017-05-02

Topics

  1. Finalize CG Reports, hand-off to WG
  2. Trip Reports
  3. Working Group Membership
  4. Suggestions for next week

Resolutions

  1. Publish 2017-05-01 drafts as Final Reports. Gather feedback until this coming Friday, and publish final specifications if no objections.

Meeting for 2017-03-14

Topics

  1. Agenda review and Introductions
  2. Status of Verifiable Claims WG Creation
  3. No meeting on 3/28 (reminder)
  4. DO_NOT_CORRELATE flag discussion
  5. WoT use case
  6. Action Item Review (https://goo.gl/V4XTBT)
  7. Suggestions for next week agenda

Meeting for 2017-03-07

Topics

  1. Status of VCWG Creation
  2. Meeting for 2017-03-28 Cancelled
  3. IMS Badge Summit Update
  4. RWoT Demo Status
  5. Prioritizing Pull Requests
  6. Actions Item Review
  7. amigus email re: privacy: https://lists.w3.org/Archives/Public/public-credentials/2017Mar/0002.html
  8. Suggestions for Next Meeting Agenda

Meeting for 2017-02-28

Topics

  1. Introduction to Kim Duffy from BlockCerts
  2. Status of Verifiable Claims WG Creation
  3. Update on Verifiable Claims Playground
  4. Action Item Review
  5. Agenda for Next Week

Meeting for 2017-02-21

Topics

  1. Introduction to Sean Bohan
  2. Status of WG Creation
  3. Action Item Review
  4. Face to Face Meetings
  5. Requirements
  6. Correlatability of Usage Patterns
  7. Primary or Secondary Subject

Meeting for 2017-02-14

Topics

  1. Introduction to Abbas Ali from R3
  2. Status of Verifiable Claims WG Creation
  3. Sandbox for the implementers to work on
  4. Action Item Review
  5. Face to Face Meeting Opportunities
  6. Portable Reputation Kit

Meeting for 2017-02-07

Topics

  1. Agenda Review and Introductions
  2. Status of Verifiable Claims WG Creation
  3. Status of Face to Face in March
  4. Action Item Review
  5. Discuss work on requirements gathering
  6. Use Case Issue 18: Holder Terminology
  7. Use Case Issue 34: Lifecycle Engagement - next steps

Resolutions

  1. Do not close yet Issue 18 yet.

Meeting for 2017-01-31

Topics

  1. Agenda Review and Introductions
  2. Status of Verifiable Claims WG creation
  3. Possible VCWG F2F week of March 21st 2017
  4. Use Cases Framework Discussion

Meeting for 2017-01-24

Topics

  1. Agenda Review
  2. Status of Verifiable Claims WG Vote
  3. Use Cases Narratives and Revocation/Privacy
  4. Correlation Analysis and Prevention
  5. Filtering, Focusing use cases

Meeting for 2017-01-17

Topics

  1. Agenda review and Introductions
  2. Status of Verifiable Claims WG Vote
  3. Web of Trust Use Case
  4. Prioritization of/response to privacy concerns

Meeting for 2017-01-10

Topics

  1. Vote for Verifiable Claims WG
  2. Use Cases Document Update
  3. Agenda Items for Next Week

Meeting for 2016-12-20

Topics

  1. Introduction to Pari, from Intuit
  2. Agenda Review
  3. Verifiable Claims WG Vote
  4. Discussion on Github
  5. Intro to Github Pull Requests
  6. Use of WebIDL in the Spec

Meeting for 2016-12-13

Topics

  1. Vote for Verifiable Claims WG is Open
  2. Reference Libraries
  3. Use of JSON/JSON-LD in spec
  4. Next Meeting

Meeting for 2016-12-06

Topics

  1. Introduction to John Koshy
  2. Rebooting Web of Trust, Paris
  3. Issue Prioritization
  4. Use of JSON/JSON-LD in spec

Meeting for 2016-11-29

Topics

  1. Agenda review
  2. New Participants
  3. New Location for Specs
  4. Status of W3M Charter Review
  5. Call for review
  6. Brief review of adding issues in GitHub
  7. Nesting Signatures with JWT

Meeting for 2016-11-15

Topics

  1. W3C AB Feedback
  2. Specific Use Cases
  3. Age Verification Use Case
  4. Spec Issues

Meeting for 2016-11-08

Topics

  1. Gathering More Use Case Data

Meeting for 2016-11-01

Topics

  1. Rebooting Web of Trust
  2. Internet Identity Workshop #23
  3. Verifiable Claims Face-to-Face
  4. Intro to Phil Archer from W3C
  5. Responses to VC Concerns

Meeting for 2016-10-28

Topics

  1. Agenda Review
  2. Long-term Architectural Concerns
  3. Decentralized Identifiers
  4. Start of Data Model Deep Dive
  5. Data Model Deep Dive
  6. Digital Signatures
  7. Responding to Charter Review Comments

Meeting for 2016-10-27

Topics

  1. Welcome and Administrivia
  2. Introduction to Use Cases
  3. Good Use Cases
  4. Education Industry Use Cases
  5. Healthcare Use Cases
  6. Payments Use Cases
  7. Verifiable Claims Proposed Architecture / Goals
  8. Data model and Representation Overview
  9. The W3C Process
  10. VCF2F Day Two Agenda Bash

Meeting for 2016-10-11

Topics

  1. Verifiable Claims Face-to-Face Agenda
  2. architecture (shane)
  3. data model, representations (manu) - day 1 will feel repetitive b/c there will be ~50% newcomers

Meeting for 2016-10-04

Topics

  1. After Action Report - W3C TPAC
  2. Registering for VC Face-to-Face
  3. Verifiable Claims Face-to-Face Agenda
  4. Feedback on W3C Verifiable Claims Announcement

Meeting for 2016-09-06

Topics

  1. Quick introduction from Pindar Wong
  2. F2F Meeting at IIW
  3. Verifiable Claims Implementations to Demo
  4. Verifiable Claims RC-2 Draft Charter Feedback
  5. Estonian E-Residency Face-to-Face
  6. Planning for W3C TPAC
  7. Interplanetary File System and Verifiable Claims

Meeting for 2016-08-16

Topics

  1. Introduction to Bob Burke, Koupon Media
  2. Introduction to Adrian Gropper, HealthURL
  3. Verifiable Claims Face-to-Face at IIW
  4. Verifiable Claims RC-2 Draft Charter
  5. IPFS and Verifiable Claims

Meeting for 2016-08-02

Topics

  1. Feedback on Charter from W3C Management
  2. Verifiable Claims Face-to-Face Agenda
  3. Terminology and Expiration
  4. Linked Data Encrypted Signatures

Meeting for 2016-07-19

Topics

  1. Review All Dissenting Opinions
  2. JOSE / JWT Clarification/Analysis
  3. Verifiable Claims Face-to-Face Agenda
  4. Coordinating with Other Workshops

Meeting for 2016-07-12

Topics

  1. Verifiable Claims Presentation at WPIG face-to-face
  2. Identified Verifiable Claims "Weak Points"
  3. Next Steps

Meeting for 2016-06-21

Topics

  1. Verifiable Claims Working Group Proposal
  2. Terminology Results
  3. Data Model Specification
  4. Use Cases
  5. Next Steps

Meeting for 2016-06-14

Topics

  1. Terminology Poll
  2. Implementer Commitment Summary
  3. Verifiable Claims Architecture
  4. Primer
  5. Data Model Specification
  6. Use Cases
  7. Items that are "Good Enough" for Review

Meeting for 2016-06-08

Topics

  1. Discuss purpose of architecture proposal
  2. Analysis of current document
  3. Identifier registry
  4. Repository
  5. Simplifying Diagram

Meeting for 2016-06-07

Topics

  1. VCTF Deliverables
  2. Verifiable Claims Use Cases Review
  3. Verifiable Claims Charter
  4. Verifiable Claims Charter FAQ
  5. Architecture Summary
  6. Verifiable Claims Data Model Specification
  7. Terminology Conflicts
  8. Other items

Resolutions

  1. Adopt self-sovereign terminology over user-centric terminology.

Meeting for 2016-05-31

Topics

  1. Introduction to New Participants
  2. Self-Sovereign Identity Architecture
  3. Decentralized Identifiers
  4. Verifiable Claims Use Cases Review
  5. Update on Work Items

Meeting for 2016-05-24

Topics

  1. Introductions to New Participants
  2. Agenda Bashing
  3. Introduction to Anil John and DHS Blockchain R&D
  4. Other Introductions
  5. United Nations ID2020 Summit Recap
  6. Rebooting Web of Trust Design Workshop Recap
  7. Recent Vermont Legal Finding
  8. Update on Work Items

Meeting for 2016-05-17

Topics

  1. Introduction to Alka Gupta from GlobalID
  2. Blockchain and Identity
  3. Verifiable Claims Data Model Specification
  4. Credentials Transparency Initiative Terminology
  5. Target Date Web Payments IG Hand-off

Resolutions

  1. Augment the "Credential" terminology in the specification with a modifier like "OpenCredential" or "IdentityCredential" or "VerifiableCredential".

Meeting for 2016-05-10

Topics

  1. Introduction to Alok from Cambridge Blockchain
  2. Review of Survey Status
  3. Work on Existing Docs
  4. Verifiable Claims Data Model Specification
  5. Survey Results/Overview
  6. One page W3C AC Rep Summary
  7. Architecture Summary
  8. Implementers Summary

Meeting for 2016-04-26

Topics

  1. Credentials Transparency Initiative Alignment
  2. Review of Questionnaire Status
  3. Verifiable Claims Data Model Specification
  4. One page W3C AC Rep Summary
  5. Charter Cleanup
  6. Use Case Reviews

Meeting for 2016-04-19

Topics

  1. Introductions to New Participants
  2. United Nations ID2020 Initiative
  3. Review of Questionnaire Responses
  4. Work Items

Meeting for 2016-04-05

Topics

  1. Introduction to Christopher Allen
  2. Blockchain Interest in Identity Credentials
  3. Review of Questionnaire
  4. Charter Review To Date
  5. Options Moving Forward

Meeting for 2016-03-29

Topics

  1. Introduction to Todd Albers
  2. W3C Advisory Committee Summary
  3. Next Steps (in the next 4-6 weeks)
  4. Spec Ops

Meeting for 2016-03-15

Topics

  1. Draft Charter Proposal
  2. Use Cases Document
  3. Card for AC Meeting
  4. Vocabulary changes - Issuer, Curator, Inspector

Resolutions

  1. Integrate as much feedback as possible before 3pm today and send the editor's draft charter and use cases out for informal review to the interviewees, the survey respondents, and the W3C Advisory Committee.

Meeting for 2016-03-08

Topics

  1. Draft Charter Proposal
  2. Material for W3C Advisory Committe Meeting at MIT
  3. Use Cases Document
  4. Expected Timeline for VCTF Charter Review

Meeting for 2016-03-01

Topics

  1. Review Web Payments IG Vote on VCTF
  2. Next Steps (W3C AC Meeting)
  3. Draft Charter Proposal
  4. Use Cases Document

Meeting for 2016-02-19

Topics

  1. Current Status
  2. Use Cases Document
  3. Verifiable Claims Task Force Presentation
  4. Verifiable Claims Task Force Final Report
  5. Draft Charter Proposal

Meeting for 2016-02-12

Topics

  1. Background on Jeanne, Bob, and the Credentials Transparency Initiative
  2. Problem Statement
  3. Data Format
  4. Technical Advisory Committee on Metadata
  5. Need for Credentials Technology

Meeting for 2016-02-09

Topics

  1. Plan to Finishing up Interviews
  2. Verifiable Claims Task Force Final Report
  3. Use Cases Document
  4. Draft Charter Proposal

Meeting for 2016-02-02

Topics

  1. Summary of Interviews So Far
  2. Documents Needed By Web Payments Face-to-Face
  3. Verifiable Claims Task Force Final Report
  4. Use Cases Document
  5. Draft Charter Proposal

Meeting for 2016-01-29-2

Topics

  1. Introduction
  2. Problem Statement
  3. Level of assurance, Level of protection, and Level of control
  4. The Problem with User-Centric
  5. Important Trust Models
  6. OpenID, SAML, and Privacy
  7. Potential Standardization Opportunities
  8. Best Place for Standardization Work

Meeting for 2016-01-29-1

Topics

  1. Problem Statement
  2. User-centric Design vs Privacy-centric Design
  3. OpenID Connect, SAML, and OAuth
  4. Useful Technology Pieces
  5. The Work on OpenID
  6. The Best Mode for a Solution

Meeting for 2016-01-28

Topics

  1. Problem Statement
  2. Stakeholders and Benefits
  3. SAML, Oauth, OpenID Connect, and JOSE
  4. Important Work Items
  5. Best Location for Standards Work

Meeting for 2016-01-27

Topics

  1. Problem Statement
  2. OpenID Connect
  3. Definitions and User-Centric vs. Service-Centric
  4. Respect Network
  5. Portable Identifiers
  6. Ideal Place for Work

Meeting for 2016-01-26

Topics

  1. Interview Narratives So Far
  2. Responding to Identified Narratives
  3. Draft Charter Proposal
  4. Use Cases Document

Meeting for 2016-01-19

Topics

  1. Update on Past and Upcoming Interviews
  2. Plan (or lack thereof) for Face-to-Face in February
  3. Stalled Work

Meeting for 2016-01-08

Topics

  1. Verifiable Claims Problem Statement
  2. Anti-Fraud / Anti-Abuse
  3. Revocation / Status Checking
  4. Slow Evolution of Agent-Centric Protocols
  5. Trust and Semantics

Meeting for 2016-01-05

Topics

  1. Background on Verifiable Claims work
  2. Problem Statement and Scope
  3. Key Questions
  4. The Interviews

Meeting for 2015-12-15

Topics

  1. Introduction of New Participants
  2. Review Deliverables
  3. Review Milestones / Timelines
  4. Review Benefits for Stakeholders

Resolutions

  1. Request that the Web Payments Interest Group approve the Verifiable Claims Task Force with the caveat that we still need to do interviews before finalizing work and problem statement.
  2. Adopt the Deliverables in the VCTF wiki as they stand today.
  3. Adopt the Milestones / Timeline as it stands today in the wiki.
  4. Adopt the benefits as they stand now in the wiki with the understanding that we may come back and revise the list as we learn more over the next couple of months.

Meeting for 2015-12-08

Topics

  1. Introductions to New Participants
  2. Review of Scope
  3. Review Stakeholders
  4. Review Task Force Operation
  5. Review Success Criteria
  6. Next Steps

Resolutions

  1. Adopt the Scope statement as it exists in the Task Force Proposal wiki.
  2. Adopt the Stakeholders section as it stands in the wiki.
  3. Adopt the Task Force Operation section as it stands in the wiki.
  4. Adopt the success criteria as it stands in the wiki.

Meeting for 2015-12-01

Topics

  1. Introduction of Participants
  2. Review the purpose of the call
  3. Review Goals
  4. Review Weekly Meetings
  5. Review Definitions
  6. Review Problem Statement

Resolutions

  1. Adopt the goals statement as it exists in the Verifiable Claims Task Force Proposal.
  2. Adopt the weekly telecon format, tools, and time listed here http://w3c.github.io/vctf/#telecons with fixes to the URLs pointed out by Dave Longley.
  3. There is a significant difference between user-centric and service-centric architectures when it comes to verifiable claims.
  4. Adopt the definitions as they stand in the Verifiable Claims Task Force Proposal.
  5. Adopt the Problem Statement in the Verifiable Claims Task Force Proposal with the changes made during the call today.

Meeting for 2015-11-24

Topics

  1. Introduction to Dan Burnett
  2. WPIG / Verifiable Claims After Action Review
  3. Goals for Next Week's Meeting
  4. Administrivia for Next Week's Meeting

Meeting for 2015-11-17

Topics

  1. Current Status of Task Force Proposal
  2. Focus on Use Cases
  3. ToDo Items

Meeting for 2015-11-10

Topics

  1. Credentials Task Force in WPIG Update
  2. Tasks for Credentials CG
  3. Linked Data Fast Track WG Update

Meeting for 2015-11-03

Topics

  1. Introductions to New Participants
  2. Work Generated as a Result of W3C TPAC
  3. WebDHT Spec Released
  4. Reorganizing this group around new Task Force

Meeting for 2015-10-20

Topics

  1. W3C TPAC Credentials Presentation
  2. Introduction to Rebecca Simmons
  3. Introduction to Deb Everhart
  4. Linked Data Signatures Update
  5. HTTP Signatures Update

Meeting for 2015-10-13

Topics

  1. NACS Show
  2. HTTP Signatures
  3. Introductions to New Members
  4. W3C TPAC Credentials DRAFT Presentation
  5. Credentials Reference Implementation Demo
  6. Post-meeting Discussion

Meeting for 2015-10-06

Topics

  1. Current state of Credentials Survey
  2. Survey Outreach
  3. Upcoming Demos
  4. Lumina Meeting Review

Meeting for 2015-08-25

Topics

  1. Recruiting
  2. Standards Implementation Foundation
  3. Update from IMS Global
  4. Capabilities Wrap-up

Meeting for 2015-08-18

Topics

  1. Recruiting
  2. IMS Global Update
  3. Capabilities Document

Meeting for 2015-08-11

Topics

  1. Introduction to Annie Jenssen
  2. Recruiting
  3. Roadmap
  4. Credentialing Capabilities and Current Proposal

Meeting for 2015-08-04

Topics

  1. Recruiting
  2. Glossary Document
  3. Vision document

Meeting for 2015-07-28

Topics

  1. Recruiting
  2. Glossary Document
  3. Vision Document

Meeting for 2015-07-21

Topics

  1. Introduction to Andrew
  2. Introduction to John Tibbetts
  3. Recruiting
  4. Vision
  5. Glossary
  6. Use Cases
  7. Capabilities
  8. Roadmap

Meeting for 2015-07-14

Topics

  1. Introduction to Brendan Benshoof
  2. Recruiting
  3. Producing Documents
  4. Vision document
  5. Use Cases
  6. Capabilities
  7. Roadmap

Meeting for 2015-07-07

Topics

  1. Recruiting
  2. authorization.io
  3. Decentralized Identifiers

Meeting for 2015-06-30

Topics

  1. Credentials WG Plan
  2. Introductions of New Members
  3. Recruiting

Meeting for 2015-06-23

Topics

  1. Web Payments IG face-to-face in NYC
  2. Introduction to Matt Stone
  3. Current Status of Credentials at W3C
  4. Badge Alliance updates
  5. Focus on Recruiting New Members

Meeting for 2015-06-09

Topics

  1. Web Payments IG and Credentials

Meeting for 2015-06-02

Topics

  1. Credentials WG Charter and WPIG
  2. Recruiting document
  3. Credential Management API update
  4. Use Cases

Meeting for 2015-05-26

Topics

  1. Recruiting document (non-W3C member)
  2. Introduction to James and Arto
  3. Graph Normalization Update
  4. Recruiting W3C Members
  5. Credential Management API Extension (update)
  6. Use Cases

Meeting for 2015-05-19

Topics

  1. Introduction to Jordan Windsor
  2. Open Badges xsd:string issue
  3. WebAppSec Credential Management API
  4. Graph Normalization Test Suite
  5. Community Group Focus

Meeting for 2015-05-12

Topics

  1. Recap of 2015 Groningen Declaration Meeting
  2. OBI JSON-LD Context
  3. RDF Graph Normalization
  4. Credentials WG Charter on Web Payments Agenda
  5. Credentials WG support questionnaire
  6. Recruiting co-chair from Pearson

Meeting for 2015-05-05

Topics

  1. Introduction to Richard Varn
  2. Open Badges 1.1 Release
  3. 2015 Groningen Declaration Meeting
  4. WebAppSec Credential Management API Status Update
  5. Level One Project
  6. Credentials WG Charter on Web Payments Agenda
  7. Next Steps

Meeting for 2015-04-14

Topics

  1. Use Cases
  2. WebAppSec Credential Management API
  3. Credentials/Badges Vocabulary Update

Resolutions

  1. Switch the primary use cases document over to the micro-use cases approach, concentrate all future use case work into that document.

Meeting for 2015-04-07

Topics

  1. Executive Summary
  2. Use Cases
  3. Credentials/Badges Vocabulary Update

Meeting for 2015-03-31

Topics

  1. W3C Interest in Credentials WG
  2. Executive Summary
  3. Use Cases
  4. Credentials/Badges Vocabulary Update
  5. Roadmap

Meeting for 2015-03-10

Topics

  1. Teleconference Bridge
  2. Credentials Working Group Charter
  3. Use Cases / Linked Data Signatures
  4. Credentials/Badges Vocabulary Update
  5. Roadmap Update

Meeting for 2015-03-03

Topics

  1. Credentials Working Group Charter
  2. Use Cases
  3. Profile Use Cases
  4. Linked Data Signatures spec
  5. Credentials/Badges Vocabulary Update

Meeting for 2015-02-10

Topics

  1. Introduction to Laura Fowler
  2. Introduction to Brent Shambaugh
  3. Web Payments IG Face-to-Face
  4. Decentralized Identifiers for Credentials/Badges
  5. Signatures Update
  6. Badge Alliance Context/Vocabulary Update
  7. Roadmap Update

Meeting for 2015-01-27

Topics

  1. Signatures Update
  2. Badges/Credentials Vocabulary and Context
  3. Digital Promise Summit for Workforce

Meeting for 2015-01-20

Topics

  1. Bedrock / P3 Release
  2. Credentials / Web Payments IG Agenda
  3. Signatures Update
  4. Badge Alliance Vocabulary/Context Update
  5. Roadmap

Meeting for 2015-01-13

Topics

  1. Web Payments Face-to-Face
  2. Linked Data Signatures
  3. JSON-LD Credentials Context/Vocabulary Update
  4. Roadmap Update

Meeting for 2014-12-09

Topics

  1. Introduction to elf Pavlik
  2. Signatures Update
  3. Context Work Stream Update
  4. Roadmap Work Stream update
  5. Hosted vs. Signed

Meeting for 2014-12-02

Topics

  1. Coordination Plan for Next Few Months
  2. Path Forward for Digital Signatures
  3. Moving CG Documents onto REC-track at W3C

Meeting for 2014-11-25

Topics

  1. Digital Signatures - Pushback from Social Web / Harry Halpin
  2. Introduction to Dale McCrory
  3. Digital Signature Strategy

Meeting for 2014-11-18

Topics

  1. Groningen Declaration
  2. Digital Signatures for Credentials

Meeting for 2014-11-11

Topics

  1. Review W3C TPAC Meeting
  2. Web Payments IG Meeting
  3. W3C TPAC Credentials Hallway Discussions
  4. Planning for next 2 months

Meeting for 2014-10-28

Topics

  1. Introduction
  2. Identity Proofing
  3. Scope of CG Work
  4. Use Cases / Future Work
  5. Identifier Portability
  6. Data Rights, Legacy Support

Meeting for 2014-10-21

Topics

  1. Intro from Dale McCrory from Courseload
  2. Introduction to Nate Otto from Concentric Sky
  3. Review Credentials CG Presentation to Web Payments IG
  4. Review Credentials CG F2F Agenda
  5. Review Credentials Use Cases vote status
  6. Open Badges and JSON-LD

Meeting for 2014-10-14

Topics

  1. W3C TPAC and Credentials CG
  2. Credentials CG Use Cases Review
  3. Start Discussing Roadmap Document

Resolutions

  1. Publish a preliminary Credentials Use Cases document and vote on publishing it as a first public working draft before W3C TPAC. Start the vote at 5pm ET on Tuesday October 14th 2014 and keep it open for 7 days.

Meeting for 2014-10-07

Topics

  1. Voting Process on Credentials Use Case Document
  2. Web Payments Agenda on CG call last week
  3. Comments on Use Cases Document
  4. Remaining Use Cases
  5. Verifiable Claims
  6. Media Rights
  7. Data Rights
  8. Proof of Pseudo-anonymity
  9. Data Rights Agreement Before Transmission of Data
  10. Access Revocation
  11. Access Audit
  12. Access Credential Audit Information
  13. Education Use Cases
  14. Access to Transcripts
  15. Online Transcript
  16. Continuing Education
  17. University Credits
  18. Bachelor's Degree
  19. Any other use cases?

Resolutions

  1. Create and publish a preliminary Credentials Use Cases document and vote on publishing it as a first public working draft before W3C TPAC. Give fair notice of the vote immediately, start the vote at the end of the day on Tuesday October 14th 2014 and keep it open for 7 days.

Meeting for 2014-09-30

Topics

  1. Web Payments Use Cases Vote
  2. Register Now for W3C TPAC
  3. Advanced Use Cases (Tim Holborn)
  4. Offer use case
  5. Proof of Contribution Use Case
  6. Proof of Invention Use Case
  7. Wrapping up Use Cases

Meeting for 2014-09-23

Topics

  1. Complete Web Payments Use Case Review
  2. Identity Recovery
  3. Use Cases from Tim Holborn
  4. Generalized Credentials
  5. Read/Write Permissions
  6. Proof of Delivery
  7. Sharing Private Data
  8. Credential-based Access
  9. Confidential Sharing/Agreement
  10. Advertising and Data Rights
  11. Credentials for Internet of Things

Meeting for 2014-09-16

Topics

  1. W3C TPAC Preparation
  2. Mark as Liason to IMS Global and PESC
  3. Charter Vote Result
  4. Web Payments Use Case Review

Meeting for 2014-09-09

Topics

  1. Introduction of new Members
  2. Quick IGF 2014 Review
  3. Badge Alliance and JSON-LD Discussion
  4. Charter Vote Status
  5. Use Case Review

Meeting for 2014-08-26

Topics

  1. Introductions
  2. Overview of W3C Community Group Process
  3. Charter Review
  4. Questions Related to CG Operation
  5. Use Case Review

Resolutions

  1. Hold a vote on the Credentials CG Charter starting Friday, August 29th 2014 with the vote open for 2 weeks. Accept the charter if 2/3rds majority of votes cast are in favor.