W3C

- DRAFT -

Verifiable Claims Working Group

23 Jan 2018

Agenda

Attendees

Present
Adrian, Benjamin_Young, Chris_Webber, Christopher_Allen, Dan_Burnett, Dave_Longley, Gregg_Kellogg, Gropper, JoeAndrieu, Liam_Quin, Manu_Sporny, Richard_Varn, Ted_Thibodeau, Nathan_George, David_Lehn
Regrets
David_Ezell
Chair
Richard_Varn, Dan_Burnett, Matt_Stone
Scribe
TallTed

Contents


<scribe> scribenick: TallTed

next FTF time and place

<gkellogg> https://www.eventbrite.com/e/internet-identity-workshop-iiwxxvi-26-2018a-tickets-39785360083

https://docs.google.com/spreadsheets/d/19Ndqc5pLsTu2ZmP4Wy7OlMOmskQFHPh28sMjW3ugsww/edit#gid=0

[ now planned to be Thursday, April 5-6, following IIW ]

<burn> I believe meeting is Thu afternoon plus Friday

<burn> Thu to overlap, Fri for us

varn: et al, general discussion about F2F, now planned to be Thurs-Fri, April 5-6, following IIW

Status update on subject != holder chart review

https://lists.w3.org/Archives/Public/public-vc-wg/2017Dec/att-0016/SubjectHolder.jpeg

varn: working on review

agropper: sent a list of use cases from health care, asking for some help with generating some more specificity in use case doc
... list at https://www.w3.org/mid/CANYRo8hgxPn1+AysV5px83Jfn=ja__noES2TT_1PgHjoLk1cSg@mail.gmail.com

<burn> Adrian's email: https://lists.w3.org/Archives/Public/public-vc-wg/2018Jan/0010.html

varn: for next week, hoping that a helper will contact agropper
... any other volunteers to look at Subject != Holder for their pet cases?

JoeAndrieu: has a very full plate, not sure how best to engage on this
... challenges are scope and depth
... we've got 84 use cases in eval doc. which of these are worth focused time?
... level of specificity is very low so far; need to do some deep-dives

varn: could adding some of these as exemplars in data model help?

JoeAndrieu: including some of these as non-normative examples is a good path, but which ~5 should those be?

<Zakim> burn, you wanted to discuss what we are after here

burn: given the diagram, does the set of use cases we have cover the diagram at the level of specificity you see as important?
... if not, are those use cases covered in the data model?
... if anything is missing, suggest that now. else, we consider the model and cases good.

JoeAndrieu: not clear what "addressed sufficiently" means. e.g., marriage certificate may not be...

varn: concrete answer of "addressed sufficiently" is -- if the existing handling will cause an objection when we come to PR/CR/etc., then it's not sufficiently addressed. if no objection forthcoming, then it is.

<Zakim> manu, you wanted to ask if we can focus on one use case and see if we can express it.

<dlongley> i suggest we make a github issue that says "how do we represent this use case in the data model"

<burn> +1 dlongley

<dlongley> and then we try and answer that in comments.

manu: best way to work through this is to pick a concrete example (e.g., marriage certificate) and try to express it with the data model
... if there's a use case someone thinks is not covered, that should be raised to the group for such workup
... in the end, we have a number of examples

varn: is the question of marriage certificate about full lifecycle, or a static point therein?

<burn> joe needs to give us a specific use case, I believe

JoeAndrieu: deep dive would be full lifecycle. in any case, focus should be on the "sticky wicket" part, not the easy part.
... maybe focus is on after-divorce, need for kid to prove parentage

<varn> subject does not equal holder where a spouse asserts a person is their spouse for purposes of getting workplace benefits

<nage> I'm more interested in the case where the parties using the credential don't have equal rights, like the case of the children needing a credential about the parent's marriage (or former marriage) -- though this case is interesting too

JoeAndrieu: will write up marriage license sticky wicket
... from process, would like to find 5 other use cases with sticky wickets

<liam> [Liam thinks about people who have to get a marriage cert amended, e.g. as a result of gender reassignment!]

manu: additional point -- need to make sure we're covering most common cases well, not focus entirely on corner cases

varn: key points are to whom the claims are being presented (employers, schools, housing)

Need volunteers to edit and contribute to a revocation spec

manu: this is about status check, as in "drivers license has been revoked"

JoeAndrieu: can propose this as a paper topic at RWoT in addition to CCG

Liam to update web page--provide suggestions

varn: we're asking for people to submit thoughts/requests for improvement to liam, and for liam to review as well

ChristopherA: based on last week's hackathon, people couldn't figure out where existing libraries were, nor what their states were if located

liam: if we have implementations, tell me, and I'll add them

manu: there are none yet. maybe in next few months.
... correction, we have some basic implementations, but they're VERY nascent, not production worthy in any way

liam: always a tradeoff in WGs. implementations of draft specs get shipped, and implementors get upset about having to change to bring into compliance.

manu: big warnings "this is a draft, don't put implementation into production" are the best we can do

<varn> TallTed

<varn> Sorry. The nicknames confuse me

<manu> TallTed: The WG page needs work - it's hard to find charter, work that has been done, etc. We should fix that.

<manu> Please, no wiki - we don't need another source of information...

<manu> TallTed: Github puts up a lot of barriers to people that are not coders

<manu> +1 to TallTed

<manu> TallTed: If you look at lots of WG over past 10 years, you'll find basic structure to all home pages, which happen to be in the wiki

<burn> Liam, can you please update the home page to include what Ted asked for?

<manu> TallTed: Link to charter, link to things we're working on, current status, products that have been finalized, chairs, participation links, etc.

<manu> Varn: So, a basic home page.

<dlehn> preset+ David_Lehn

<liam> [i can move the link to the charter to the top, or copy it, and if people send me info abot products will add it for sure]

Data model issue review and volunteers to drive issues to closure

varn: we have a growing list of issues. folks need to look at these and provide feedback; we can't just grow the list indefinitely.

<Zakim> burn, you wanted to ask specifically for volunteers to 'own' issues

burn: what we'd like is for particular people to volunteer to drive particular issues to closure

<dlongley> closed this one: https://github.com/w3c/vc-data-model/issues/71:)

burn: self-assign or ask chairs to assign you to the issue. your job is not necessarily to solve the issue yourself, but to push toward that solution by pulling others into action...

<burn> Thanks dlongley

ADJOURN

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/01/23 16:58:16 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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)

Succeeded: s/Monday/Thursday/
Succeeded: s/April 2, before IIW/April 5-6, following IIW/
Succeeded: s/party/part/
Present: Adrian Benjamin_Young Chris_Webber Christopher_Allen Dan_Burnett Dave_Longley Gregg_Kellogg Gropper JoeAndrieu Liam_Quin Manu_Sporny Richard_Varn Ted_Thibodeau Nathan_George David_Lehn
Regrets: David_Ezell
Found ScribeNick: TallTed
Inferring Scribes: TallTed
Agenda: https://lists.w3.org/Archives/Public/public-vc-wg/2018Jan/0012.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: 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.)


[End of scribe.perl diagnostic output]