- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Mon, 10 Sep 2018 17:31:03 +0900
- To: public-vc-wg@w3.org
available at:
https://www.w3.org/2018/09/04-vcwg-minutes.html
also as text below.
Thanks a lot for taking these minutes, Yancy!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
Verifiable Claims Working Group
04 Sep 2018
[2]Agenda
[2] https://lists.w3.org/Archives/Public/public-vc-wg/2018Aug/0010.html
Attendees
Present
Benjamin_Young, Dan_Burnett, Dave_Longley,
David_Chadwick, David_Lehn, Ganesh_Annan,
Gregory_Natran, Manu_Sporny, Ted_Thibodeau,
Tzviya_Siegman, Yancy_Ribbens, Chris_Webber,
Daniel_Hardman, Lovesh_Harchandani, Michael_Lodder,
Ken_Ebert, Nathan_George, Kaz_Ashimura
Regrets
Clare_Nelson
Chair
Dan_Burnett, Matt_Stone
Scribe
Yancy
Contents
* [3]Topics
1. [4]Agenda review, Introductions, Re-introductions
2. [5]blockchain workshop
3. [6]Assign owners to unassigned issues
4. [7]Status update on external review of Data Model Spec
5. [8]Most stagnant issues
6. [9]Data Model PR review
* [10]Summary of Action Items
* [11]Summary of Resolutions
__________________________________________________________
<burn> scribenick: Yancy
Agenda review, Introductions, Re-introductions
burn: no action items
... looking at most stagnant issues and data model review
blockchain workshop
manu: blockchain web commerce interest group. Nothing solid but
chance something will happen. FYI since most of us are not on
invite list.
<tzviya> [12]https://www.w3.org/2003/08/Workshops/
[12] https://www.w3.org/2003/08/Workshops/
manu: headsup from IBM, Sovrin, Evernym, Digital Bazaar etc
will be there
... birds of a feather session at tpac but not traditional
workshop
Assign owners to unassigned issues
manu: will be a workshop around strong identities and that's it
about blockchain breakout
<burn>
[13]https://github.com/w3c/vc-data-model/issues?utf8=%E2%9C%93&
q=is%3Aissue+is%3Aopen+no%3Aassignee
[13] https://github.com/w3c/vc-data-model/issues?utf8=✓&q=is:issue+is:open+no:assignee
burn: wants to talk about closing issues or PR for issue
... issue was discussed 6 days ago and not worried yet on this
daniel: questions being asked are interesting and thinks those
are good questions but doesn't have answers
DavidC: happy to take this issue
Status update on external review of Data Model Spec
burn: ken would you be able to introduce yourself
ken: working with Sovrin. working on standards architecture and
coding
Most stagnant issues
<burn>
[14]https://github.com/w3c/vc-data-model/issues?utf8=✓&q=is%3Ai
ssue+is%3Aopen+sort%3Aupdated-asc++-label%3Adefer+
[14] https://github.com/w3c/vc-data-model/issues?utf8=✓&q=is:issue+is:open+sort:updated-asc++-label:defer+
burn: most stagnant issues. Wants to find a way to unstick and
keep them moving.
... posted link
... start at top and work our way down
... start with #72
... cwebber2 would you comment
<kaz> [15]issue 72
[15] https://github.com/w3c/vc-data-model/issues/72
cwebber2: didn't writup PR
... will make a priority this week
<burn> ACTION: Cwebber to write up PR for issue #72
burn: next is 194
<kaz> [16]issue 194
[16] https://github.com/w3c/vc-data-model/issues/194
<Zakim> manu, you wanted to say we have some designs for
this...
<daniel> have to step away for about 10 min; brb
manu: want to talk a bit before you submit that PR because of
good feedback from customer deployment. may help to have a
discussion in working group.
<burn> Manu commenting briefly on 172
cwebber2: happy to have discussion in group or after
burn: needs to login with host code for everyone to showup
...: can't change it now
manu: I see it
<burn> now to issue 194
manu: can take this
...: thousands of vocab words may conflict
... w3c vocab is something google and microsoft does not want
to do for schema.org
... jasonld will let you do that but some scary things can
happen
... won't prevent anyone from pulling in if they want to do
that
... should be clean vocab because of that
... should be able to close the issue (no op)
... nothing to be added as a result
... a completly different issue because of content control is a
commment on PR
<manu> ACTION: Manu to respond to issue 194 Dan Brickely, no
op, and suggested path forward, then close issue.
davidc: raised a number of questions and would like answers
burn: request for comments
... moving on to #133
... last comment was from manu asking joe if this was fixed
... request for david and manu to look at this
... joe is ooo for next few weeks
... manu thinks we can close if davidc agrees
<kaz> [17]issue 133
[17] https://github.com/w3c/vc-data-model/issues/133
<Zakim> manu, you wanted to agree with DavidC, but I think we
can close at least this issue.
davidc: all related as a higher generic level, not sure it has
been fixed as a whole. might be good to discuss face to face
which is more productive than email
manu: agrees with david that there's a higher level meta issue
that hasn't been resolved, but we can close this issue because
we have a profile id and should be able to close.
davidc: agrees with manu on that
burn: if you think joe is not to be surprised then it's fine to
close
... make sure joe is not unaware
<scribe> ACTION: manu to bring it up with Joe
burn: thank you
... next is #200
... not a lot of discussion
<Zakim> manu, you wanted to note what was supposed to happen.
burn: matt and joe are both not present
manu: Matt put in a PR to fix a lot of typos and issues but not
noted in issue. I need to close the loop with him to make sure
good solid response are made for Clare
<scribe> ACTION: find PR and cross ref with issue
manu: matt addressed 201
... it wasn't 200
... nothing has been done for 200
... 200 is stagnant
... Matt worked on 201
<kaz> [18]issue 200
[18] https://github.com/w3c/vc-data-model/issues/200
<kaz> [19]issue 201
[19] https://github.com/w3c/vc-data-model/issues/201
burn: matt and joe to review and unstick
<burn> ACTION: Matt and Joe to review 200 and get it moving
burn: leaving 10 minutes to look at PR's
... looking at #209
... duplicate of #128
... wondering why there are two
<kaz> [20]issue 209
[20] https://github.com/w3c/vc-data-model/issues/209
<kaz> [21]issue 128
[21] https://github.com/w3c/vc-data-model/issues/128
TallTed: the way he reads those two, is one is wishing for
default and other is looking for this isn't a default and go
look there
... not identical
<DavidC> +1
Davidc: agrees
<Zakim> manu, you wanted to defer, regardless.
manu: is confused because it looks like a duplicate
tallted: 128 is asking for a standard schema and 129 is if not
using that standard default what to look against
<kaz> [22]issue 128
[22] https://github.com/w3c/vc-data-model/issues/128
<kaz> [23]issue 129
[23] https://github.com/w3c/vc-data-model/issues/129
manu: can defer both issues can be done by not specifying in
the spec and instead use feature later
<daniel> I am back
manu: not critical and can defer until next specification
<ken> nage: the presence of schema would really help us reason
about ZKP functionality relative to the data model, this
doesn't mean we must add it now, but it would speed things
along
DavidC: types and content is the same. has had discussions if
it's strongly verified. In the documentation it has been added
to address types.
... here's a type that gets embedded in the schema for it
nage: we have issue with it not specifying the type of
encoding. It would accelerate the process to specify.
<Zakim> manu, you wanted to suggest that there is a way to
solve this with a single property.
nage: it would speed up the process if we did have it by
mapping to crypto
manu: has an idea of how to address with a single attribute.
one way is to defer and the other is to get a simple proposal
and I might have one.
<manu> yes, dlongley is right
<manu> this will take a little bit of effort.
dlongley: will have to specify and might take more than one
attribute which could be more effort than we think
burn: is there a summary manu could do
manu: trying to prevent us from having long features. we run
the risk on introducing a feature that isn't thought out well.
tallted: it's a data model how much are we expecting?
manu: the concern is how it acts when we deploy the feature.
question is does it actually solve anything?
... data model is simple but does it solve the problem
... validation language example. is an attack surfaced open.
<burn> I think it's fine to ask if this is critical for this
version
tallted: thinks manu is thinking beyond scope and protocol
... the model doesn't do that. if YAML or otherwise
dlongley: if we don't have a good grasp of how to do this. It's
not simple enough to just toss in the data model.
<Zakim> burn, you wanted to reiterate question about whether we
must have this now
dlongley: thinks it's more difficult than just data model and
it's a middle ground
burn: Manu is right that we are tying to finish things up
... doesn't think we will have an answer today
... we reserve the right to say this isn't going to be resolved
for this version
<manu> ACTION: Manu to work on PRs for 128 and 129.
burn: any objections for how to move forward?
Data Model PR review
<burn> [24]https://github.com/w3c/vc-data-model/pulls
[24] https://github.com/w3c/vc-data-model/pulls
burn: opportunity for manu to bring up items for how to move
forward
... daniel if you can talk about credentials. lovesh don't know
if you're being blocked.
manu: suggests DavidC, then Daniel, then lovesh
davidc: had some good feedback from dlongley
daniel: bearer credentials and had discussion in other forum
and feels like verbiage isn't right.
lovesh: proposed the change to verify the call cryptographic
repository.
... any comment?
manu: still thinks there's a problem with VC
... any input from the group would be good
<lovesh> [25]https://github.com/w3c/vc-data-model/pull/214
[25] https://github.com/w3c/vc-data-model/pull/214
Summary of Action Items
[NEW] ACTION: Cwebber to write up PR for issue #72
[NEW] ACTION: find PR and cross ref with issue
[NEW] ACTION: manu to bring it up with Joe
[NEW] ACTION: Manu to respond to issue 194 Dan Brickely, no op,
and suggested path forward, then close issue.
[NEW] ACTION: Manu to work on PRs for 128 and 129.
[NEW] ACTION: Matt and Joe to review 200 and get it moving
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes formatted by David Booth's [26]scribe.perl version
1.152 ([27]CVS log)
$Date: 2018/09/10 08:26:36 $
[26] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[27] http://dev.w3.org/cvsweb/2002/scribe/
Received on Monday, 10 September 2018 08:32:13 UTC