14:38:46 RRSAgent has joined #vcwg 14:38:46 logging to http://www.w3.org/2017/05/30-vcwg-irc 14:39:39 Chairs: DanB, RichardV, MattS 14:39:49 Agenda: https://lists.w3.org/Archives/Public/public-vc-wg/2017May/0013.html 14:41:55 rrsagent, draft minutes 14:41:55 I have made the request to generate http://www.w3.org/2017/05/30-vcwg-minutes.html burn 14:42:01 rrsagent, make minutes public 14:42:01 I'm logging. I don't understand 'make minutes public', burn. Try /msg RRSAgent help 14:46:08 rrsagent, make logs public 14:50:28 present+ DanBurnett 14:57:38 present+ JoeAndrieu 14:59:27 present+ RobTrainer 14:59:44 present+ RichardVarn 15:00:05 Rob_Trainer has joined #vcwg 15:00:08 present+ ManuSporny 15:00:40 present+ ChrisWebber 15:00:56 gkellogg has joined #vcwg 15:01:14 present+ ChristopherAllen 15:01:24 present+ ColleenKennedy 15:01:47 zakim, who's on the phone? 15:01:47 ChristopherA has joined #vcwg 15:01:47 Present: DanBurnett, JoeAndrieu, RobTrainer, RichardVarn, ManuSporny, ChrisWebber, ChristopherAllen, ColleenKennedy 15:01:58 Good Morning! 15:02:13 present+ DaveLongley 15:02:16 JoeAndrieu has joined #vcwg 15:02:18 present+ Gregg_Kellogg 15:02:37 amigus has joined #vcwg 15:02:40 colleen has joined #vcwg 15:02:55 present+ 15:05:09 present+ AdamMigus 15:05:19 Scribe: amigus 15:05:45 Topic: Agenda review and Introductions 15:05:50 q+ 15:06:02 ack cwebber2 15:06:21 ack cwebber 15:06:52 cwebber: I am Chris Webber; I joined because of my interest in distributed identity. I'm here with spec ops 15:07:02 Topic: Status of publishing UC FPWD 15:07:27 https://w3c.github.io/vc-use-cases/ 15:07:32 cwebber: I'm also involved in but that is not as part of my spec ops affiliation 15:07:38 We discussed last week of having 1 person each week being "re-introduced" 15:07:50 s//Social Web WG 15:07:59 present+ 15:08:01 burn: editors have beenworking on the document but i'm not sure of that status. Manu? 15:08:21 manu: usecases? greg made the majority of updates 15:08:29 q? 15:08:30 https://github.com/w3c/vc-use-cases/pull/41 15:08:52 rrsagent, draft minutes 15:08:52 I have made the request to generate http://www.w3.org/2017/05/30-vcwg-minutes.html manu 15:09:13 Meeting: Verifiable Claims Working Group Telecon 15:09:13 gkellogg: working though it on PR 41; we are going to publish as FPWD but not ready yet 15:09:49 gkellogg: updated the patent URI. we set the publish date we can revisit if required 15:10:17 gkellogg: we could use the mailing list for continued discussion but there's the issue list in github 15:10:54 burn: anyone have any comments? if none editors and chairs will make decisions because it's all administrative 15:11:00 how to do a first public working draft (long URL sorry) https://services.w3.org/xslt?xmlfile=https://www.w3.org/2005/08/01-transitions2017.html&xslfile=https://www.w3.org/2005/08/transitions2017.xsl&docstatus=fpwd-wd-tr&echidna=true 15:11:06 gkellogg: I did update the intro to reflect that we're a WG now... 15:11:15 Topic: Discuss FPWD for Data Model doc 15:11:17 no other comments than +1 publish! 15:11:49 ack liam 15:12:10 liam: chair must send a publish request and request approval for the shortname 15:12:32 gkellogg: yes, got it, only pointing out that it's administrative 15:13:08 gkellogg: we'll target publishing on Tuesday but it's done when its approved and ready.. 15:13:22 Data model: https://w3c.github.io/vc-data-model/ 15:13:29 q+ to mention a few things. 15:13:59 Are you asking for this now? 15:14:02 q? 15:14:05 burn: this is the main topic for today; reminder: if you see a major gap like a section, then now is the time to mention that even if the content will be TBD lets just get the section added 15:14:06 ack manu 15:14:06 manu, you wanted to mention a few things. 15:14:21 manu: a couple of items in the spec: 15:14:38 First item - remove WebIDL from spec - https://github.com/w3c/vc-data-model/pull/45 15:14:43 manu: first item: there's a PR for it (above) 15:14:50 ACTION: chairs to send transition request for FPWD for UC doc when gkellog says doc is ready 15:15:37 q? 15:15:56 q+ 15:16:08 manu: a little contraversial but want to comment out the WebIDL from the spec because it makes browser integeration murkey. 15:16:27 manu: 15:16:33 browser tools are designed to work that way -- you need the Web IDL to convert data to/from JS and C++ ... it's not clear that we need or want that kind of rigidity here as its potentially harmful to extensibility 15:16:40 manu: second issue: terminology: we need to clean up, I 15:16:46 SeanBohanSovrin has joined #vcwg 15:16:57 manu: will suggest changes like in a PR 15:17:17 manu: will try to use the word 'entity' mostly 15:17:58 manu: we don't talk about the ecosystem; that was on purpose to avoid scope excess but now that things are better defined we might want to add something back. 15:18:40 manu: reasoning is to make sure others understand what we're trying to accomplish and that web developers understand what we're doing and the context around it. That includes terminology hence the previous 15:18:54 ack ChristopherA 15:19:00 manu: those are the changes before FPWD; I'll do a PR to get it started. 15:19:06 Present+ SeanBohan 15:19:15 ChristopherA: I have other items so i'll wait 15:19:44 burn: quesiton for manu: do you want to make some decision today or is this just discussion at this point? 15:20:02 manu: discussion and thoughts from the group is what we want today 15:20:03 +1 remove web_idl 15:20:22 q? 15:20:25 q+ 15:20:38 q+ to ask how to avoid bikesheds for terminology 15:20:45 ack JoeAndrieu 15:20:52 manu: first remove webidl, second remove the contentious word 'identity' and use 'entity' instead; third is (see above) 15:21:07 q? 15:21:12 joeAndrieu: how do we replace identity with entity? seems like different things... 15:21:15 q+ to respond to joe and the avoiding bikeshedding comment. 15:21:24 ack manu 15:21:24 manu, you wanted to respond to joe and the avoiding bikeshedding comment. 15:21:32 q- 15:22:01 manu: the terminology discussion probably is best done offline so that we don't eat all the time in the meeting. we'll set something up 15:22:17 q+ 15:22:23 manu: really just want a feel what the group things WRT direction 15:22:23 q? 15:22:47 manu: to address the bikeshedding potential: chairs please call us on bikeshedding when you see it 15:22:47 ack gkellogg 15:23:24 q+ 15:23:29 ack dlongley 15:23:42 gkellogg: there are other specs that use WebIDL without the assumption that it integrates with browsers in a particular way so I don't know if I agree with removing it on that basis because this isn't the only spec that does it (without making the assumption) 15:24:18 dlongley: we can obviously use WebIDL but we don't really *need* to use it so its easy to stay away from 15:24:54 +1 to what dlongley said. 15:24:58 q? 15:25:04 dlongley: we're not defining an interface that one should use a WebIDL for, so we don't need it -- we're jumping the gun including it 15:25:57 q+ to respond to burn - yes, we want to do that, WebIDL is a very verbose way of doing that. 15:26:06 ack manu 15:26:06 manu, you wanted to respond to burn - yes, we want to do that, WebIDL is a very verbose way of doing that. 15:26:09 burn: manu question: I don't mind us removing any particular syntax or defn language but my concern is that we are still able to be clear about defining the data model and ways that it can be used. people assume we're using JSON-LD only and we want to make it clear that it's just that... 15:26:15 +1 that we want to have multiple syntaxes as examples, -1 to Web IDL as one of those unless really necessary 15:26:43 manu: you're right; people think it's JSON-LD only. Maybe we should remove JSON-LD to and just go with JSON 15:26:58 s/clear that it's just that/clear that it's not just that/ 15:27:20 q+ 15:27:25 manu: we've opened ourselve up to misinterpretation as a semantic web thing. 15:27:40 manu: we could do it will basic examples; it's a lot less verbose than WebIDL 15:27:47 agree that WebIDL definitions are crazy verbose 15:27:50 manu: this might make it look simpler 15:27:59 manu:we could externalize the WebIDL defn 15:28:23 also -- if you can express something as JSON, you can define Web IDL for it 15:28:47 dlongley, I know that and you know that, but that wasn't the concern I raised 15:28:50 manu: education like JSON but ecomm/retail and finance use XML.. 15:28:53 q+ (on this topic, re: kinds of examples) 15:28:53 what about presenting as "just json" but saying in some note that this can be read as json-ld with an implied context? 15:29:03 q? 15:29:05 q+ on this topic, re: kinds of examples 15:29:20 ack gkellogg 15:29:23 manu: so we could show JSON, JSON-LD and XML too so that everyone sees it in their preferred format 15:29:42 q? 15:29:46 q+ 15:30:11 gkellogg: we are supposed to create a vocabulary so that we aren't building things that aren't local; JSON-LD gives us a solution for that and JSON doesn't. 15:30:38 gkellogg: I don't want to lose the ability to do localization right in the name of simplicity 15:31:01 gkellogg: XML does allow us to tie terms back to vocab by using namespaces but it does support it. 15:31:37 ack ChristopherA 15:31:37 ChristopherA, you wanted to comment on this topic, re: kinds of examples 15:31:38 burn: admin interupt: there are no issues to discuss in the next item so it was just discussion and we're basically having that discussion now. 15:31:43 q? 15:32:41 q+ to point out the JSONFeed discussion and how it relates to uptake. 15:33:11 q+ to talk about missing sections (not serialization) 15:33:18 ChristopherA: I agree with gkellogg. I want to point out to the community that, using schemas, we can have a vocabulary that results in everything being canonical regardless of format. There are other things (OWL?) that supports schema. We could point out that we don't have schema when we use JSON. 15:33:31 +1 to telling that story 15:33:35 ack cwebber 15:33:51 ChristopherA: when we define things that are outside of the schema then it doesn't matter what your encapsulation is 15:34:38 ???: we dealt with this previously and came up with a solution which is to use profiles 15:34:44 s/???/ChrisWebber 15:35:35 ChrisWebber: people who are averse to JSON-LD we could use an 'implied context' by using a profile type contstruct.. 15:35:35 ack manu 15:35:35 manu, you wanted to point out the JSONFeed discussion and how it relates to uptake. 15:35:47 manu: +1 to that 15:35:56 https://github.com/brentsimmons/JSONFeed/issues/49#issuecomment-303499812 15:35:59 manu: it worked in the social web group so we should explore that 15:36:14 (I'd like to be in queue when new topics are started) 15:36:40 engelke has joined #vcwg 15:37:09 We may be even able to get IPLD be the same canonically, which is a format that may have a lot of legs. 15:37:30 manu: i want to highlight a new data format called ???; JSON-LD has gotten pushback from the larger community. I'm pointing that out because it will repeat and we have to be careful about how we respond. we can't say 'don't use JSON-LD' but i don't have a crisp answer for how we should respond 15:37:57 q? 15:38:05 manu: so we just need to be careful (in the spec) about how we approach it and ChristopherA's suggestion seems right 15:38:20 s/ChristopherA's/cwebber's 15:38:36 I'd prefer to see 3 examples with each, with XML, JSON-LD, and JSON. 15:38:47 burn: any other questions before we go back to the broader 'gap' question 15:39:30 ChristopherA: there was a work item that came up in the CG. 15:39:32 https://docs.google.com/document/d/1W0r6TOaJXGcDP4qOzOIEfSymub4nRSLrBmtBqyDf06I/edit?usp=sharing 15:39:48 Present+ CharlesEngelke 15:40:08 https://bitsonblocks.net/2017/05/17/a-gentle-introduction-to-self-sovereign-identity/ 15:40:11 ChristopherA: it was an issue WRT other parties that are thinking about claims outside of this group; they seem to have 3 categories when they talk of it: 15:41:02 ChristopherA: R3 is a consortium that's doing something with claims and proofs which are attestations of the claims but they have attestations separate from that. 15:41:32 ChristopherA: seems like they want 1) claim, 2) proof (by others) of claim and 3) ability to refute a claim 15:42:02 ChristopherA: some say that the way we're doing it does already support this but it's not clear to me that it's the case 15:42:15 +1 it would be a good idea to say how each of those concepts map to verifiable claims 15:42:22 in the spec 15:42:25 ChristopherA:especially when discussing reputation based systems 15:43:27 q? 15:43:38 q+ JoeAndrieu 15:44:06 ack JoeAndrieu 15:44:06 JoeAndrieu, you wanted to talk about missing sections (not serialization) and to 15:44:40 JoeAndrieu: regarding elements and context: we don't have something for presentation of claims i.e. it's issued then presented to an inspector. we don't have something that shows the relationship especially when dealing with multiple claims and disclosure 15:45:00 JoeAndrieu: we also need a notion of scope-of-use 15:45:10 q? 15:45:14 JoeAndrieu: i think both are key to addressing privacy 15:45:34 q+ to ask Joe to raise an issue on the spec for that. 15:45:41 q+ to ask ChristopherA to raise an issue. 15:45:45 will do Manu 15:45:45 ack manu 15:45:45 manu, you wanted to ask Joe to raise an issue on the spec for that. and to ask ChristopherA to raise an issue. 15:45:57 burn: FYI we need to have even empty sections so people can see what's coming... 15:46:25 manu: just want to make sure that ChristopherA and JoeAndrieu's comments are added to the Github issue tracker; can you guys add them? 15:46:50 Topic: Review of issues for Datamodel Document 15:46:52 https://github.com/w3c/vc-data-model/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc 15:46:57 (another example of the 3 in addition to R3s: https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2016/blob/master/final-documents/reputation-toolkit.pdf Assertion Evidence Evaluation) 15:47:12 SeanBohan_Sovrin_ has joined #vcwg 15:47:27 burn: any comments from anyone? 15:47:35 burn: anything else from you manu? 15:48:12 manu: not yet, just the 3 items discussed earlier however, both ChristopherA's and JoeAndrieu's comments aren't addressed and should be 15:48:38 manu: actually one other item: we're doing a talk to the ??? next week I'd like to give folks a heads up that we're doing that 15:48:45 Topic: pull request 38 15:48:46 https://github.com/w3c/vc-data-model/pull/38 15:49:33 s/???/US Federal Reserve Secure Payments Task Force/ 15:49:40 burn: JoeAndrieu and amigus submitted comments, we're working through them 15:50:43 s/through them/through them. Ask that others review and comment./ 15:51:16 manu: i've been asked to come talk to the ??? to talk about our work in Charlotte, NC. they launched a task force to make faster payments happen and keeps pace with the rest of the world also better identification for fraud reduction. they're interested in VC, WP and related 15:51:33 s/???/US Federal Reserve Secure Payments Task Force/ 15:51:42 manu: please take a look at what I've done and contact me (don't leave comments in the doc) 15:52:01 rrsagent, draft minutes 15:52:01 I have made the request to generate http://www.w3.org/2017/05/30-vcwg-minutes.html burn 15:52:08 manu: it's a BD, is a 75 minute, keynote with over 100 folks in banking/finance 15:52:33 Topic: suggestions for next week 15:52:57 Suggestion: Cover PRs that I will hopefully get to today/tomorrow. 15:52:59 burn: ChristopherA brought up introductions and re-introductions which we'll start on next week 15:53:31 burn: manu: getting the docs published is top priority; we had a poll in the CG before the WG started so we have stuff 15:53:51 rrsagent, draft minutes 15:53:51 I have made the request to generate http://www.w3.org/2017/05/30-vcwg-minutes.html burn 15:54:44 s/have stuff/already have a list of priorities for discussion to start from/ 15:54:50 rrsagent, draft minutes 15:54:50 I have made the request to generate http://www.w3.org/2017/05/30-vcwg-minutes.html burn 15:55:10 I have posted issue: https://github.com/w3c/vc-data-model/issues/47 15:55:45 rrsagent, draft minutes 15:55:45 I have made the request to generate http://www.w3.org/2017/05/30-vcwg-minutes.html burn 16:01:45 rrsagent, make minutes 16:01:45 I have made the request to generate http://www.w3.org/2017/05/30-vcwg-minutes.html burn 16:02:48 rrsagent, bye 16:02:48 I see 1 open action item saved in http://www.w3.org/2017/05/30-vcwg-actions.rdf : 16:02:48 ACTION: chairs to send transition request for FPWD for UC doc when gkellog says doc is ready [1] 16:02:48 recorded in http://www.w3.org/2017/05/30-vcwg-irc#T15-14-50