<scribe> scribe: manu

Agenda review, Introductions, Re-introductions

<scribe> Chair: burn

<scribe> Agenda: https://lists.w3.org/Archives/Public/public-vc-wg/2018Mar/0010.html

<burn> Chair: Dan_Burnett, Matt_Stone, Richard_Varn

burn: Agenda is the same as has been ... focus on assigning new issues.
... We have a new person - Allen Brown.

Allen: Hello all, I am currently an independent - 20 years at Xerox Parc, 15 at Microsoft, most of professional life - mathematical logic to specify computer systems, and proof that systems work.
... I've done stuff w/ core of SQL Server, worked on mathematical models and computational realization of systems... in healthcare space most recently.
... To tie those two examples together - pragmatic systems, make claims, make sure that claims are true. Lately, I'm interested in Blockchains and Verifiable Claims.
... Look forward to helping.

F2F reminder and call for topics

<burn> https://www.w3.org/2017/vc/WG/201804f2f.html

That link is for our face to face...

burn: We are still taking topic suggestions, but may focus almost exclusively on resolution of issues that can benefit from face-to-face discussion.
... If you have other suggestions, let us know.
... Any questions before we move on to Data Model issues?

<burn> issues: https://github.com/w3c/vc-data-model/issues

Data Model Issues

burn: We're going to try to move through unassigned issues, no update for use cases document.

https://github.com/w3c/vc-data-model/issues/139

stonematt: I'll take that issue

https://github.com/w3c/vc-data-model/issues/137

dlongley: I'll take that one, editorial

https://github.com/w3c/vc-data-model/issues/136

<dlongley> manu: Fundamentally we don't care what people put into claims. I'm worried that there's some detail in here that's not clear from what he's saying. It should be fairly easy to resolve this in that we don't care what people do -- you can make whatever extensions you want to.

<dlongley> manu: We should just say that he can do what he wants here and to use a JSON-LD context and make a vocabulary, etc.

DavidC: Higher level issue on standard and interop - if anyone can say anything, we won't get interop... these documents have standard fields, let's say that.

<gkellogg> Open World

burn: Perhaps we need to think about messaging around extensibility

gkellogg: I don't know if we need to be that restrictive, the way we provide extensibility is through use of annotation to metadata... or curry information... not sure that's required here.
... This is JSON-LD and RDF, open world assumption - even if our spec restricts ability to add information, nothing prevents others from adding information anywhere else.

burn: Try adding issue in that says something about extensibility.

https://github.com/w3c/vc-data-model/issues/135

dlongley: I'll do it, by referencing other issues.

https://github.com/w3c/vc-data-model/issues/133

burn: There have been many discussions about profile / profile ID...

DavidC: I issued a PR on how to resolve this in one way... basically, saying Profile ID is the ID of the profile, holder ID is ID of the holder.
... I'll take this one

https://github.com/w3c/vc-data-model/issues/98

Allen: I'll take this one

DavidC: In the PR, I did change some of the definitions and it makes things clear what a credential is.
... Allen may want to take a look at that.

https://github.com/w3c/vc-data-model/issues/80

dlongley: I think we decided to let this one hang out for a while...

burn: right

https://github.com/w3c/vc-data-model/issues/72

manu: Chris Webber should probably take this.

DavidC: We still have an ongoing discussion wrt. Verifiable Credential and Capability

<dlongley> DavidC: My proposition is that every capability can be represented as a Verifiable Credential.

DavidC: I haven't been able to get back to Chris Webber on his assertion.

https://github.com/w3c/vc-data-model/issues/70

DavidC: This is still a live/real issue - separate individual attributes, this can be asserted... people bundle these things into a profile... you can mix/match pairs that are not intended to be mixed together.

burn: This was your initial issue, you felt strongly about it.

DavidC: We just have an issue around atomic credentials... when you bundle, you might mix-match credentials that were not intended to be mixed together.

burn: Who is taking this issue?

stonematt: I'll take it

https://github.com/w3c/vc-data-model/issues/68

burn: Tempted to assign Joe to that one - he's had a lot of input on it.

https://github.com/w3c/vc-data-model/issues/61

dlongley: CLOSED! :)

https://github.com/w3c/vc-data-model/issues/57

burn: Richard is going to be unable to join us on these calls... I'll ask him if he can do that before he disappears.
... Status update

https://github.com/w3c/vc-data-model/issues/55

<stonematt> +1 on closing this one

DavidC: I think this one is resolved... multiple subjects, multiple credentials.

https://github.com/w3c/vc-data-model/issues/54

manu: i will take the last two

https://github.com/w3c/vc-data-model/issues/47

Manu: Perhaps ChristopherA should take this one...

burn: Yes, other people that opened issues and have participated heavily, maybe they should close out their own issues.

https://github.com/w3c/vc-data-model/issues/42

<stonematt> should we have a label for these sort of defered items

dlongley: It doesn't seem like we're going to get to this in the first version... do we close or mark it as version 2?

<gkellogg> s/differ/defer/

https://github.com/w3c/vc-data-model/issues/32

burn: is this closeable
... Ok, Christopher is assigned

https://github.com/w3c/vc-data-model/issues/60

dlongley: Can we link 60 and 32

burn: Yes, we'll do that, assign Kim.

stonematt: I'll take this one too ...

https://github.com/w3c/vc-data-model/issues/19

stonematt: I'll take that one

burn: We're through the entire issue list

Issue Updates

DavidC: I have a large PR assigned, to address ambiguities in the document.
... Trying to make document consistent.
... In the PR, there is a whole list of things we're trying to do to remove ambiguity. That needs careful consideration from the group.

<Zakim> manu, you wanted to do update from conferences.

burn: We'll go through all of these issues at the face-to-face meeting if we don't get to them before then

<dlongley> manu: There are a number of conferences going around in DC, elsewhere, NoIdentity, etc.

<dlongley> manu: It's amazing how many people have VC on their banners on the booths.

<dlongley> manu: Most of these companies we've never heard of or haven't participated in the group. People are latching onto the terminology or at least the group.

tzviya: I've been speaking with people in publishing that are interested in joining the group.

manu: There is strong traction in government for Verifiable Credentials and DIDs, we'll see some bigger players joining the group soon.

burn: We're through all of the issues assigned, don't have time for PRs yet, next call.

DavidC: There will be a speakerphone at the face to face, you can join... WebEx info will be sent out to member list with dial in information for call.

burn: The plan is to have remote dial in capability

<dlongley> manu: IIW is next week. The call next Tuesday is canceled?

<dlongley> burn: Yes, that's correct. No call next week because of IIW. Our group is meeting Friday for F2F.

burn: Please push issues forward as much as possible

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

FAILED: s/differ/defer/
Succeeded: s/face-to-face meetings/the face-to-face meeting/
Present: Dan_Burnett Allen_Brown Ted_Thibodeau Tzviya_Siegman Gregg_Kellogg Dave_Longley Manu_Sporny David_Chadwick Matt_Stone Nathan_George Liam_Quin Benjamin_Young Kaliya_Hamlin
Regrets: Joe_Andrieu
Found Scribe: manu
Inferring ScribeNick: manu
Agenda: https://lists.w3.org/Archives/Public/public-vc-wg/2018Mar/0010.html

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)