14:42:36 RRSAgent has joined #vcwg 14:42:36 logging to http://www.w3.org/2017/10/10-vcwg-irc 14:42:46 rrsagent, draft minutes 14:42:46 I have made the request to generate http://www.w3.org/2017/10/10-vcwg-minutes.html burn 14:42:51 rrsagent, make logs public 14:43:06 Meeting: Verifiable Claims Working Group 14:43:22 Chair: Dan_Burnett, Matt_Stone, Richard_Varn 14:43:32 Agenda: https://lists.w3.org/Archives/Public/public-vc-wg/2017Oct/0005.html 14:49:09 stonematt has joined #vcwg 14:53:18 present+ Dan_Burnett 14:56:09 Charles_Engelke has joined #vcwg 14:58:06 present+ Charles_Engelke 14:58:23 present+ Kim_Hamilton_Duffy 14:58:53 present+ Dave_Longley 14:59:46 present+ Nathan_George 15:00:19 kimhd has joined #vcwg 15:00:26 TallTed has joined #vcwg 15:00:49 present+ David_Chadwick 15:01:51 present+ Colleen_Kennedy 15:01:58 present+ Ted_Thibodeau 15:02:03 colleen has joined #vcwg 15:02:06 nage has joined #vcwg 15:02:16 present+ colleen_kennedy 15:03:01 present+ Gregg_Kellogg 15:03:03 scribenick: Charles_Engelke 15:03:11 present+ Nathan_George 15:03:34 JoeAndrieu has joined #vcwg 15:03:42 present+ Joe_Andrieu 15:03:43 DavidC has joined #vcwg 15:03:56 Agenda review and discussions. Anyone visiting? Not today. 15:04:01 Agenda: https://lists.w3.org/Archives/Public/public-vc-wg/2017Oct/0005.html 15:04:33 Manu will not be here today, so we may not get far on some topics. 15:04:48 Topic: TPAC topic review & TPAC Planning 15:04:52 present+ Matt_Stone 15:05:10 https://docs.google.com/spreadsheets/d/161h0QO8QODtS04eyLQqc6errV7RamcbS-xOPJL6S0g0/edit#gid=0 15:05:56 present+ Richard_Varn 15:05:59 varn has joined #vcwg 15:06:27 present+ Christopher_Allen 15:06:51 Matt_Stone presented spreadsheet of TPAC topics. Created a schedule for Thursday and Friday going from 8:00 to 6:00 with lunch and two breaks. 15:06:52 present+ Chris_Webber 15:07:40 Items in the charter are prioritized for day one. 15:07:55 OpenID/SAML topic time zeroed out. No objections. 15:08:33 Not on this list is evidence & assessment 15:09:48 stonematt: Thursday afternoon overlaps with AC meeting, so we will lost some AC members from the WG meeting. 15:09:51 is anyone on our group an AC rep? 15:10:02 varn - I am 15:10:17 All WG chairs are invited to AC meetings 15:10:27 present+ Liam_Quin 15:10:45 present+ varn 15:11:10 present- varn 15:12:07 stonematt: we might shift around order of topics. 15:12:21 q+ 15:12:24 q? 15:12:29 q+ 15:12:35 q? 15:12:42 stonematt: we have an open time slot early on day two, but it's only half an hour. 15:12:45 ack ChristopherA 15:12:50 https://github.com/w3c/vc-data-model/issues/47 15:14:11 ChristopherA: want to make sure that there's time for different kinds of claims. People still don't understand what a verifiable claim is. 15:15:21 q+ to ask if the problem is terminology or that we don't actually understand it well enough ourselves 15:15:31 q? 15:15:34 ack dlongley 15:15:36 nage has joined #vcwg 15:15:37 ChristopherA: have had people thinking that a verifiable claim meant the contents were true rather than that the signature was valid. 15:17:40 ack burn 15:17:40 burn, you wanted to ask if the problem is terminology or that we don't actually understand it well enough ourselves 15:18:07 dlongley: We could move "subject is not holder" use case discussion after Joe's generic use case discussion and potentially put them together in the same 2 hour time block. 15:18:16 q+ 15:18:20 we are only verifying who issued a claim, that the contents of the claim such as subject/earner, evidence used, data contained in claim have not been changed in any way not authorized by the issuer, that the person asserting the claim has the right to do so, and so on. Have we not written this down in a way that explains that clearly enough? 15:18:22 ack ChristopherA 15:18:34 burn: is this a terminology issue, or an understanding issue? 15:18:40 burn: We have other scheduling concerns so we're really interested in order -- not specific time slots, so we'll take just the order suggestion there under advisement. 15:19:01 q+ 15:19:12 What is verifiable is *authorship*. 15:19:15 "verifiable attribution" 15:19:24 we are not the ontology group determining what claims mean 15:20:08 we verify the integrity of the statement--that it is made by the author as stated, not the factuality or truthfulness of the statement 15:20:16 ack TallTed 15:20:19 ChristopherA: what is verifiable is authorship. We're attracting people who want us to move on to what is inside the claim - is it true? 15:20:55 Once we get the basics, then others can extend the work into primary meaning or applicability of the claim for a specific purpose 15:21:09 q+ to frame the extras as claims about claims 15:21:17 q+ 15:21:41 q+ 15:21:46 ack JoeAndrieu 15:21:46 JoeAndrieu, you wanted to frame the extras as claims about claims 15:22:06 TallTed: calling us "Verifiable Claims" is going to make this confusion continue, going beyond the actual scope. But WG name is already in place. 15:22:35 MattLarson has joined #vcwg 15:22:42 TallTed: talking about Subject vs Holder is going well beyond the nominal scope of verifying that "a said b" 15:22:43 ack varn 15:22:47 q? 15:23:54 @varn exactly. claim about claims addresses a lot of "add-on" evaluation and assertions, e.g., evidence, negative claims, etc. 15:24:04 TallTed: much of the mailing list content, many agenda items for calls and for TPAC, are going well beyond "did a say this (perhaps, on date)?" 15:24:06 ack cwebber 15:24:10 q? 15:24:30 varn: claims about claims are much broader than scope 15:24:32 q+ 15:24:33 http://www.mumble.net/~jar/articles/oo.html 15:24:42 I don't need to change name, I just want to clarify the definitions early on. 15:24:50 +1 to strong definitions 15:24:50 especially given the common confusion. 15:24:55 s/I don't need/... I don't need/ 15:24:59 +1 15:25:08 ack stonematt 15:25:08 cwebber: lots of areas have seriously overloaded names (e.g. "object"). Should focus on strong definitions. 15:25:22 also related to: https://github.com/w3c/vc-data-model/issues/66 15:25:24 q+ 15:25:27 q+ 15:25:42 i agree claims about claims is complicated and deep and we are doing that. but if someone wants to extend our work to do that, more power to them 15:25:59 stonematt: Have no interest in rebranding group. Stay in current scope. Work on data model. 15:25:59 we are not doing that I meant 15:26:36 stonematt: TPAC discussion topics on these definitions, clarifying scope. 15:26:51 ack burn 15:27:57 ack TallTed 15:27:58 burn: Regard concerns about discussion varying widely. We may go beyond what we define in the document, but that's a good thing for getting group alignment. 15:28:32 @varn Well, technically, the subject of a claim can be a "concept", which always seemed odd to me. But if using another claim as the subject lets us provide evidence, dispute, or make negative claims, then we have a forward looking resolution for all those who are looking for that capability. 15:28:57 s/that capability/those capabilities/ 15:29:06 q+ 15:29:23 TallTed: not advocating changing the group name. Nudge for a bit more consistency in stating what is in scope. Much of the discussion is getting deep into things outside of scope. So capture the use cases, note they need to be addressed, but make it clear that they aren't necessarily going to be addressed in WG. 15:29:36 ack ChristopherA 15:29:56 Yes. that's extremely cogent. The question we answer is "Did Joe say this?" 15:30:00 q+ 15:30:02 ChristopherA: agrees should not change name, shares many of the same concerns. 15:30:48 ChristopherA: there are people with misconceptions, and we need to address those misconceptions strongly. 15:31:13 we may need a section of "VC's don't xyz..." 15:31:14 i don't think the "this" in "Did Joe say this" is *entirely* out of scope, there are some minimal, common parts of "this" that we want to define for interoperability. 15:31:20 q? 15:31:25 ack DavidC 15:31:31 and we should define those and say that's all that's in scope. 15:31:44 q? 15:31:44 ChristopherA: Misconceptions about scope are causing problems with people thinking what we're talking about is different from our actual discussions. 15:31:45 +1 Christopher, would love to see some PRs 15:31:48 q+ 15:32:46 Note that I am about to close the queue on this topic for today 15:32:52 +1 to David Chadwick ... it is in scope for us to provide some *minimal* semantics about "this". 15:33:11 DavidC: claims are not meaningful without extra context around them. 15:33:17 ack stonematt 15:33:31 -1 to David. There are plenty of situations where the claim is valid independent of holder==subject 15:33:41 and meta data about the claim itself. 15:33:46 (a well worn debate between us) 15:33:56 stonematt: we're getting away from our agenda item, so should get back to that. 15:34:00 q? 15:34:23 Topic: Readiness for Privacy Group exposure 15:35:09 Link to an email from David on privacy: https://lists.w3.org/Archives/Public/public-vc-wg/2017Oct/0003.html 15:35:13 burn: Next topic - Readiness for Privacy Group exposure. Significant privacy concerns were raised about our group, even before the group was formed. Questions about whether document is ready for their review. 15:35:17 present+ David_Lehn 15:36:54 q? 15:36:54 David_Lehn: Have seen many questions and comments on privacy. Need to address those in the WG. Trying to turn the privacy document into HTML and post on GitHub. 15:37:08 s/David_Lehn/David_Chadwick/ 15:37:14 Topic: Introduce Milestone 1.5 15:37:27 https://github.com/w3c/vc-data-model/milestone/5 15:38:26 stonematt: On Milestone 1.5 - Formal Vocabulary. Dave Longley warned that we don't want to do that too early, because as soon as it's out there, people will start using it. 15:39:29 stonematt: the milestone is the formal publishing of the machine vocabulary to whichever systems we choose at that time. 15:39:34 well said 15:39:40 Topic: Data Model Spec current milestone issues 15:39:55 https://github.com/w3c/vc-data-model/milestone/3 15:41:01 TallTed: (sorry for timeline issue in logs) "*minimal* semantics" == claims are (expressible) in RDF, i.e., {?s ?p ?o}. Dealing with the URIs or literals in those positions (checking whether ?s is holder, etc.) is beyond (current) scope. 15:41:38 ? who is speaking now? 15:42:12 +1 on concern 15:42:20 q/ 15:42:22 q? 15:42:27 liam: what language is the base language for translation 15:42:30 q+ 15:42:41 ack stonemat 15:42:43 i18n support native in RDF (can express language) 15:43:14 q+ 15:43:16 [and in XML for that matter but we need to be explicit about what's in our dm] 15:43:20 ack dlongley 15:43:32 stonematt: support localization and language is important. Can we just decide we need this, or do we need discussion? 15:44:09 q? 15:44:18 dlongley: if things are missing, we should enumerate them. Would be good to find out what issues people think still exist that aren't addressed by technology choices already made. 15:44:23 q? 15:44:25 Topic: Test Suite Progress 15:44:27 q+ 15:44:34 ack stonematt 15:44:47 +1 to examples 15:44:53 yes, good point 15:44:59 +1 to example in other language 15:45:22 [this may also include Basic English, for accessibility purposes] 15:45:42 stonematt: thinks it would be good to put examples in other languages in docs to validate that it's correct. Request for volunteers with nature language other than English, especially other character sets. 15:47:26 cwebber: on update for test suite. This is number two priority for him for right now. Manu is working on this, there might be others from Digital Bazaar who might be helping. This is probably the worst month for him to work on this given other work. 15:47:51 burn: Any other volunteers? No offers. 15:48:03 Topic: Future Agenda Topics 15:48:33 burn: we have a few minutes available for other topic. Any requests? 15:49:03 q+ 15:49:03 claimvelope? 15:49:09 ack nage 15:49:12 q+ 15:50:17 +1 good for in person discussion. 15:50:23 q+ 15:50:26 ack varn 15:50:42 q+ to suggest future use case topic 15:50:51 is "claimvelope" a "verifiable profile"? 15:50:55 nage: topic from Web of Trust regarding binding claims and identifiers. Many different approaches were brought up. 15:51:48 I would like to see the claimvelope discussion in CCG 15:52:06 +1 claimvelope metadata/labeling 15:52:06 varn: some people want their claims to public, others discoverable, others private. We need a wrapper - some kind of metadata describing things like privacy issues in claims. A properly structured "claimvelope" helps with that. 15:52:30 q? 15:52:36 > Richard- yes I am very interested in this 15:52:46 ack ChristopherA 15:52:57 burn: ChristopherA said he'd like to see this in the community group. 15:53:03 so i guess "claimvelope" is more like an advertisement for further discovery ... need to figure out a name for this. 15:53:31 dlongley: would you include this topic in at Terms of Use discussion? 15:53:54 stonematt: might be orthogonal, i don't really mind where it's discussed. 15:54:24 dlongley: are these sorts of topics addressed in something like ORDL 15:54:29 q? 15:54:31 ack JoeAndrieu 15:54:31 JoeAndrieu, you wanted to suggest future use case topic 15:54:32 dlongley--yes, that would be one purpose of a claimvelope. it could do other things to describe the payload and its terms of use. like reverse clickwrap. 15:54:36 q+ 15:54:38 stonematt: oh, i don't know about that. 15:54:54 ChristopherA: Need to make sure we have right people for the use cases. 15:55:43 ack stonematt 15:55:43 q? 15:55:44 (I also will not be able to make call next week) 15:56:57 stonematt: we have an unscheduled session on "time to live" and "terms of use" and "digital rights language". Where does this fit. It seems related to claimvelope. Are these new ideas that we have to solve? 15:57:38 for the minutes, joe andrieu wants time on the call in two weeks to discuss use cases again 15:58:07 JoeAndrieu: wants time on call in two weeks to discussion use cases. 15:58:15 having a set of data elements that are selectively described in the wrapper of the claim is what i am after 15:58:38 present+ David_Ezell 15:58:44 rrsagent, draft minutes 15:58:44 I have made the request to generate http://www.w3.org/2017/10/10-vcwg-minutes.html burn 15:58:47 dezell has joined #vcwg 18:02:15 Zakim has left #vcwg 18:05:54 DanC has joined #vcwg 18:22:34 DanC has left #vcwg 21:38:44 gkellogg has joined #vcwg