14:52:15 RRSAgent has joined #vcwg 14:52:15 logging to http://www.w3.org/2017/08/01-vcwg-irc 14:52:25 Zakim has joined #vcwg 14:55:10 TallTed has joined #vcwg 14:56:25 present+ Dan_Burnett 14:56:40 Meeting: Verifiable Claims Working Group 14:56:54 Chair: Matt Stone, Richard Varn, Dan Burnett 14:58:55 amigus has joined #vcwg 14:59:06 rrsagent, bye 14:59:29 colleen has joined #vcwg 14:59:34 rrsagent, make logs public 14:59:41 rrsagent, make minutes 14:59:41 I have made the request to generate http://www.w3.org/2017/08/01-vcwg-minutes.html manu 15:00:12 gkellogg has joined #vcwg 15:01:03 present+ colleen_kennedy 15:01:12 present+ Dave_Longley 15:01:25 Present+ Manu_Sporny, Gregg_Kellogg, Dan_Burnett, Adam_Migus, Ted_Thiboudeaux 15:01:26 stonematt has joined #vcwg 15:01:33 Present+ Richard_Varn 15:01:37 Present+ Matt_Stone 15:01:39 present+ 15:01:46 present- stonematt 15:01:59 rrsagent, make minutes 15:01:59 I have made the request to generate http://www.w3.org/2017/08/01-vcwg-minutes.html manu 15:02:01 present+ Adam_Migus 15:02:02 nage has joined #vcwg 15:02:15 present+ Nathan_George 15:02:27 present+ ChristopherA 15:02:43 present+ Chris_Webber 15:02:53 present+ Christopher_Allen 15:02:58 present+ Ted_Thibodeau 15:03:11 present- Ted_Thiboudeaux 15:03:50 TallTed has changed the topic to: VCWG - 2017-08-01 concall agenda https://lists.w3.org/Archives/Public/public-vc-wg/2017Jul/0018.html 15:03:55 Present+ Kim_Hamilton_Duffy 15:04:04 varn has joined #vcwg 15:04:56 Agenda: https://lists.w3.org/Archives/Public/public-vc-wg/2017Jul/0018.html 15:05:03 JoeAndrieu has joined #vcwg 15:05:05 rrsagent, make minutes 15:05:05 I have made the request to generate http://www.w3.org/2017/08/01-vcwg-minutes.html manu 15:05:09 I'm getting "host has not logged in" for webex 15:05:50 s/I'm getting "host has not logged in" for webex// 15:05:59 host is Liam and host is not needed for us to use it 15:06:09 Present+ dezell 15:06:14 s/host is Liam and host is not needed for us to use it// 15:08:18 Scribe: dezell 15:08:34 Topic: Agenda review, Introductions and Reintroductions 15:09:09 Matt: there's a new structure in pull request #65. We need to discuss. 15:09:38 Matt: also, Manu suggested "milestones for deliverables." 15:10:12 +1 to the Agenda. 15:10:48 Matt: we also need a new editor use cases. 15:11:30 There was also some discussion by Rieks with Manu that though difficult, had some points. 15:11:40 DavidC has joined #vcwg 15:11:50 q? 15:11:51 Agenda approved. 15:12:07 yes, but my pw does not work for the webex 15:12:22 Matt: anyone want to introduce themselves? 15:12:37 also I cannot login to the W3C pages 15:13:35 Adam Migus: I'm an enterprise architect, 20 years in security. Verifiable claims came to my attention at a conference where Manu presented. 15:13:47 ...: I'm involved as a SpecOps standards champion. 15:14:01 Topic: Data Model Spec discussion 15:14:10 https://w3c.github.io/vc-data-model/ 15:14:22 present+ 15:14:23 https://github.com/w3c/vc-data-model/pull/65 15:15:04 pr preview: https://htmlpreview.github.io/?https://github.com/w3c/vc-data-model/blob/msporny-verification/index.html 15:15:06 Manu: The PR is multi-faceted. There is clarifying restruction, came out of discussion of verification/revocation. 15:15:58 ...: This version should be easier to read. There are now sections of the document that talk about things we've been mulling over. 15:16:13 ...: we're trying to create a way to introduce new concepts in a more modular way. 15:16:17 Here's the latest structure of the document in an HTML preview: https://htmlpreview.github.io/?https://github.com/w3c/vc-data-model/blob/msporny-verification/index.html 15:16:47 zakim, who's on the phone? 15:16:47 Present: Dan_Burnett, colleen_kennedy, Dave_Longley, Manu_Sporny, Gregg_Kellogg, Adam_Migus, Richard_Varn, Matt_Stone, Nathan_George, ChristopherA, Chris_Webber, Christopher_Allen, 15:16:50 ... Ted_Thibodeau, Kim_Hamilton_Duffy, dezell, liam 15:16:57 Manu: look at the table of contents on the left. 15:17:10 present- dezell 15:17:19 present+ David_Ezell 15:17:24 present- liam 15:17:29 present+ Liam_Quin 15:17:52 present- colleen_kennedy 15:17:57 present+ Colleen_Kennedy 15:17:58 Manu: this PR version moves Verification up to the core part of the spec. The core data model section will be revamped (so ignore for now). 15:18:13 ...: but more basic concepts are now discussed in depth. 15:18:24 ...: That's followed by advanced concepts. 15:19:01 ...: Section 6 is "Verification" which outlines all the steps one might do to see if a claim is useful - syntax, information, expiration, non-revoked, etc. 15:19:43 ...: I hope this will give us concrete sections of the spec we can point to when people want to know how we address certain issues. 15:19:57 ...: we want to tie concepts to implementation. 15:20:05 q? 15:20:09 q+ 15:20:19 +1 15:20:21 ack burn 15:20:37 q+ 15:21:10 q? 15:21:32 Burn: I like this in general. I think it will be easier for people. We need some deliniation between normative and non-normative. Granted this can be difficult in a model per se. 15:21:39 q+ to note "prefer implementers/readers", normative vs. informative sections 15:21:44 ack ChristopherA 15:22:29 If revocation instructions are present, the claim must not have been revoked. 15:22:42 Christopher: I see some difficulty understanding between [sections] 6.3 and 6.4. 15:22:45 q? 15:23:19 q? 15:23:21 q+ to respond to 6.3 and 6.4 15:23:26 ...: Manu had a discussion with someone online. I liked Manu's responses, and I think they help illuminate the difference. 15:23:26 ack manu 15:23:26 manu, you wanted to note "prefer implementers/readers", normative vs. informative sections and to respond to 6.3 and 6.4 15:23:29 s/ If revocation instructions are present, the claim must not have been revoked.// 15:23:59 I actually prefer to help readers rather than implementers, myself 15:24:03 cwebber2... i think that's supposed to mean "If revocation instructions are present, they MUST/SHOULD be followed during verification." 15:24:17 Favoring users is always better 15:24:27 Manu: Dan noted it might difficult for implementers to understand tradeoffs. There is some question about whether these documents are for implementers or web developers. 15:24:27 that text needs updating (but all of section 6 does, mostly placeholders now) 15:24:48 dlongley, thanks for the clarification 15:25:02 ...: W3C documents seem to favor implementers, but I'd say we prefer that the document should be easy to read for a general technical audience. 15:25:04 q? 15:25:18 ...: I don't know that we'll shove everything into the core datamodel section. 15:25:38 Manu, this was not a major point. My major point was wrt normative/informatie. 15:25:49 ...: we have some experience doing it this way with another spec (now in rec) and we'll see how it goes. 15:26:26 ...: Yes - we'll have normative and informative sections. The basic and advanced concept sections will be normative. 15:26:38 q? 15:27:05 Not the entity profile, but how to trust the entity profile 15:27:06 ...: Christopher asked about 6.3 and 6.4 - entity profiles. Our intent is to define entity profiles in this document. 15:27:48 ...: Hopefully that will become clearer. I hope the bulleted lists will in time be expanded to be more readable. 15:27:52 s/Christopher Asked/Christopher Webber asked/ 15:27:52 q? 15:27:53 Q+ 15:28:00 ack ChristopherA 15:28:48 q+ to agree that "trust in the entity profile" is out of scope.... trust networks are out of scope. 15:28:57 agree that we should focus on semantics, not trust 15:29:05 q? 15:29:28 Christopher A: I'm making a point that there are some requirements hiding in the discussion about entities and entity profiles. 15:29:47 q? 15:29:51 ack manu 15:29:51 manu, you wanted to agree that "trust in the entity profile" is out of scope.... trust networks are out of scope. 15:29:55 ...: These issues might belong in other kinds of specs - what are those? 15:30:23 Manu: we don't outline the trust models in detail - that's on purpose since they are out of scope. 15:30:42 ...: Our work is meant to be "trust model agnostic." 15:30:50 q? 15:30:53 q+ 15:31:12 But there are some assumptions about those choices here, and I just to be explicit that those choices are made elsewhere. 15:31:12 Kim asks, in webex chat - "Which github issue is Christopher referring to?" 15:31:14 ...: these concepts are continuing to be explored in the Credentials CG. 15:31:55 q? 15:32:11 Issue was from an old version of the spec: https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2016/issues/34#issuecomment-319298392 15:32:11 Sorry, but no Tracker is associated with this channel. 15:32:21 of the DID spec. 15:32:25 q? 15:32:30 ack me 15:32:30 ack dezell 15:32:46 q+ 15:33:09 Matt: seems like there's general positive feedback. From a readability perspective, IMO it's a big improvement. 15:33:18 ack JoeAndrieu 15:33:18 q+ to ask if we want to merge the PR at this point and iterate on it after that? 15:34:09 +1 to Joe's comment. 15:34:10 JoeAndrieu: the notion of whether the "holder" is the "subject" and how can we trust that is a key concern. 15:34:22 I think there are some assumptions/requirements for other documents here. 15:34:27 q+ to add to the "entity profile" discussion 15:34:30 ...: we need better language, and I think that topic is requiring more work. 15:34:46 Matt: I suggest we open an issue for that terminology issue. 15:34:49 q+ to agree with JoeA, it's unresolved, and that was apparent in the DID spec conversation last week. 15:34:57 q- later 15:35:05 q? 15:35:46 ack me 15:35:46 nage, you wanted to add to the "entity profile" discussion 15:35:48 Nathan: entity profile has a lot of things related to privacy. So there are discussions of both terminology and how an EP is used in practice. 15:35:54 ack manu 15:35:54 manu, you wanted to ask if we want to merge the PR at this point and iterate on it after that? and to agree with JoeA, it's unresolved, and that was apparent in the DID spec 15:35:57 ... conversation last week. 15:36:28 Manu: Just to underscore - I didn't mean to say EP and Privacy are out of scope. Selecting "One Trust Model" is out of scope per our charter. 15:36:42 q? 15:36:51 +1 to clarification about trust model, noting that the embedded/assumed trust models need some teasing out, esp wrt entity profiles 15:37:02 ...: We had a good discussion last week, and it was obvious that we are still not totally aligned on terminology. 15:37:08 I'm not yet hearing that even if we don't choose a trust model, there are some requirements that a trust model must specify, and that list we may want to include. 15:37:29 +1 PR65 looks like a good improvement 15:37:34 ...: But I think that's a >different< discussion than PR 65. 15:37:37 +1 to PR 65 15:37:37 +1 to merge PR65 15:37:40 +1 on PR65 15:37:41 +1 15:37:47 ...: I need to ask if it's OK to merge PR65. 15:38:06 +1 15:38:16 +1 15:38:17 +1 15:38:18 +1 15:38:29 +1 15:38:39 Matt: hearing no objections. So we can close this topic and move to the next one. Merge is approved. 15:38:51 Topic: Milestones for next deliverables 15:39:09 I have made the request to generate http://www.w3.org/2017/08/01-vcwg-minutes.html dezell 15:39:37 I'm needing more examples, and if the spec changes, the examples are changed. 15:39:51 q+ 15:40:13 Matt: I'd like to start the discussion to get feedback on what deliverable milestones might be, with an eye to creating implementation milestones. 15:40:32 Christopher A: trying to use examples in the document was harder than I thought. 15:40:49 kimhd has joined #vcwg 15:41:03 ...: I'm not saying the examples should be change (they are illustrative) but we need to be sure we have covered all the subtleties. 15:41:24 q? 15:41:28 ack ChristopherA 15:41:38 q+ 15:41:41 ...: we need more detailed examples. And we need to track that when the spec changes the examples change. 15:41:47 q+ to mention that this is what milestone 1 should deal w/ and setup - a test suite w/ examples. 15:41:50 ack burn 15:42:17 Linked Data has subtleties 15:42:24 Burn: Understood desire to make examples match. Please feel free to create a PR to address any issues you see, or ask. Feel empowered. 15:42:27 ack manu 15:42:27 manu, you wanted to mention that this is what milestone 1 should deal w/ and setup - a test suite w/ examples. 15:42:52 +1 on test suite 15:42:58 Manu: I agree with Christopher A. Minimal Liable Implementations are the way to go - a test suite with examples will help. 15:43:03 q? 15:43:16 q+ 15:43:17 s/Liable/Viable 15:43:26 s/Liable/Viable/ 15:43:57 ...: Milestone 1 - demonstration signature issue and revocation. 15:44:32 ...: once we have that, we can grow the examples in the test suite in the direction we want. 15:44:59 ...: we should have tests and source documents, and expand dynamically when people pose questions. 15:45:00 +1 to milestone 1 be Minimum Viable Implementation that is scoped to Issue & Sign (not Expire and Revoke) 15:45:02 +1 to starting test suite. Will need that to finish CR eventually anyway. 15:45:36 q? 15:45:52 ...: Milestone 1 - a one month effort to create the above minimal viable implementation. 15:46:27 ack stonematt 15:46:40 Matt: sounds like the minimal implementation is "issue sign", milestone 2 is "expiration revocation", and we can decide Milestone 3 later. 15:47:06 q? 15:47:36 Manu: normally materials are kept in a project in GitHub. Create a "milestone 1" and describe it. 15:47:49 s/issue sign/issue signature/ 15:47:58 q? 15:48:05 ...: if the group agrees we can move ahead. 15:48:13 no objections 15:48:17 Matt: people OK with these first two milestones? 15:48:19 +1 15:48:21 +1 15:48:22 +1 to first two milestones 15:48:24 +1 15:48:34 +1 15:48:34 +1 15:48:36 +1 to milestone 1 - check issuer/syntax/signature... milestone 2 - revocation, etc. 15:48:45 +1 15:48:46 q+ for Editor for Use Cases 15:48:55 q+ 15:49:08 q? 15:49:15 q- 15:49:25 Topic: Editor for Use Cases 15:49:27 ACTION: manu to describe the first two milestones (issue/signature) and (expiration revocation) in GitHub. 15:49:27 Sorry, but no Tracker is associated with this channel. 15:49:43 Topic: Editor for Use Cases 15:50:07 q? 15:50:07 Joe: I can take responsibility for this role and pose changes through an issue. 15:50:12 ack JoeAndrieu 15:50:12 JoeAndrieu, you wanted to discuss Editor for Use Cases 15:50:20 q+ to wonder if we want to cut down too much on use cases? 15:50:32 Matt: Thanks Joe. 15:50:42 q? 15:50:44 ack manu 15:50:44 manu, you wanted to wonder if we want to cut down too much on use cases? 15:51:02 q+ 15:51:18 Manu: My question - I know we have a narrow charter, so I'm wondering how we focus the use cases without losing "out of scope" use cases. 15:51:30 q? 15:51:36 +1 for a non-normative "Future Considerations" section 15:51:41 ...: We want a way to express our future vision. 15:51:44 other specs have that. 15:51:48 ack JoeAndrieu 15:51:51 +1 retain "VC UCs out of scope for this WG" labeled as such 15:52:46 q? 15:53:02 +1 to what JoeA just said. 15:53:04 JoeAndrieu: So that's one organizing (in/out of scope) principle, but I have others. I'll include it in my recommendation. 15:53:09 q? 15:53:43 Topic: Next Week's Agenda 15:53:43 q+ 15:53:52 ack burn 15:53:53 Matt: what should we address. 15:54:11 q+ 15:54:20 q+ to ask "data model discussion" on next weeks agenda.... specifically, entity profile discussion. 15:54:23 q? 15:54:26 Burn: no item to propose, but once the milestones are created, people in this group must evaluate Milestone 1 >very carefully<. 15:54:34 ack DavidC 15:54:36 I have an issue for next week, when I hope to be able to join via Webex 15:55:21 DavidC: go ahead and type your issue in there now 15:55:23 ack manu 15:55:23 manu, you wanted to ask "data model discussion" on next weeks agenda.... specifically, entity profile discussion. 15:55:24 On the CC group we discussed group attributes, and having a single attribute in each claim, and claims linked via a group ID 15:55:24 ack manu 15:55:42 I also said that people need to make sure their milestone 1 issues are entered into GitHub 15:55:49 manu: I think we should discuss entity profile and review the datamodel. 15:56:12 q? 15:56:43 Matt: thanks for the discussion. Nice progress. 15:56:46 Adjourned. 15:56:49 bye all 15:56:49 Ciao!! 15:56:55 rrsagent, make minutes 15:56:55 I have made the request to generate http://www.w3.org/2017/08/01-vcwg-minutes.html burn 15:56:55 I have made the request to generate http://www.w3.org/2017/08/01-vcwg-minutes.html dezell 15:57:45 zakim, who's on the phone? 15:57:45 Present: Dan_Burnett, Dave_Longley, Manu_Sporny, Gregg_Kellogg, Adam_Migus, Richard_Varn, Matt_Stone, Nathan_George, ChristopherA, Chris_Webber, Christopher_Allen, Ted_Thibodeau, 15:57:48 ... Kim_Hamilton_Duffy, David_Ezell, Liam_Quin, Colleen_Kennedy 15:59:25 present- ChristopherA 15:59:59 present+ Ted_Thibodeau 16:00:48 present+ Kim_Hamilton_Duffy 16:00:59 rrsagent, make minutes 16:00:59 I have made the request to generate http://www.w3.org/2017/08/01-vcwg-minutes.html burn 16:01:10 zakim, who's on the phone? 16:01:10 Present: Dan_Burnett, Dave_Longley, Manu_Sporny, Gregg_Kellogg, Adam_Migus, Richard_Varn, Matt_Stone, Nathan_George, Chris_Webber, Christopher_Allen, Ted_Thibodeau, 16:01:13 ... Kim_Hamilton_Duffy, David_Ezell, Liam_Quin, Colleen_Kennedy 16:03:02 present+ David_Ezell, Liam_Quin, Colleen_Kennedy 16:03:10 rrsagent, make minutes 16:03:10 I have made the request to generate http://www.w3.org/2017/08/01-vcwg-minutes.html burn 16:08:00 present+ Kim_Hamilton_Duffy 16:08:04 rrsagent, make minutes 16:08:04 I have made the request to generate http://www.w3.org/2017/08/01-vcwg-minutes.html burn 16:09:35 s/...:/.../g 16:09:40 rrsagent, make minutes 16:09:40 I have made the request to generate http://www.w3.org/2017/08/01-vcwg-minutes.html burn 16:10:52 rrsagent, bye 16:10:52 I see 1 open action item saved in http://www.w3.org/2017/08/01-vcwg-actions.rdf : 16:10:52 ACTION: manu to describe the first two milestones (issue/signature) and (expiration revocation) in GitHub. [1] 16:10:52 recorded in http://www.w3.org/2017/08/01-vcwg-irc#T15-49-27