Re: Agenda: Verifiable Claims Teleconference - Tuesday, May 17th 2016

+1 re: protocol vs. data-model issues.

I've noted version control as another facet to providing validation controls

Beyond the notation of an expiry date; what is the longest possible lifespan of a credential? Is it the timespan that the encryption method used on the document is considered useful / difficult to break?

Expiry also brings up issues about long-term archives i guess. not that support necessarily creates an operational issues.  Perhaps therein is the variance between optional and mandatory.

Tim.

On Wed, 25 May 2016 at 00:03 Stone, Matt <matt.stone@pearson.com <mailto:matt.stone@pearson.com>> wrote:
​I won't be there today, but be very clear to distinguish between the expiration of the credential (in the data model, like an issue date) and the "time since last verified" that the protocol would care about.

-stone​


=====
Matt Stone
501-291-1599


On Tue, May 24, 2016 at 7:49 AM, Daniel Burnett <danielcburnett@gmail.com <mailto:danielcburnett@gmail.com>> wrote:
Manu,

There has been a mailing list thread [1] about whether a credential expiration date property should be required in the data model.  It appears to me that, so far, there isn't consensus either way.  You might want to add it as an agenda item we can discuss if time permits at the end of the meeting.

-- dan

[1] https://lists.w3.org/Archives/Public/public-credentials/2016May/0023.html <https://lists.w3.org/Archives/Public/public-credentials/2016May/0023.html>

On Mon, May 23, 2016 at 4:10 PM, Manu Sporny <msporny@digitalbazaar.com <mailto:msporny@digitalbazaar.com>> wrote:
Hi all,

We have a Verifiable Claims Task Force call tomorrow to get an intro to
the US Department of Homeland Security's Blockchain research project
around identity from Anil John (who initiated the project). We'll also
provide a rundown of what happened at the United Nations ID2020 summit,
the Rebooting Web of Trust Design Workshop, and how those events
dovetail with the work we're doing here. Finally, we'll get an update on
progress on deliverables for the upcoming W3C Blockchain workshop and
Web Payments IG meeting on July 1st 2016.

The meeting is open to the general public. There are no Intellectual
Property Release requirements. The call will be recorded and minuted to
ensure we're capturing everyone's concerns properly.

If you want to add anything to or modify the proposed agenda below,
please respond via the mailing list or make a note of it at the
beginning of the call. If your organization would not like the call to
be recorded, let me know and we'll disable the audio recording.

==========
Tuesday, May 24th 2016
Time: 11am Boston
Text Chat: http://tinyurl.com/w3c-vctf <http://tinyurl.com/w3c-vctf>
           irc://irc.w3.org:6665/#vctf <http://irc.w3.org:6665/#vctf>
Voice: sip:vctf@96.89.14.196 <mailto:sip%3Avctf@96.89.14.196>
       tel:+1-540-961-4469;ext=6306 <tel:%2B1-540-961-4469%3Bext%3D6306> (extension 6306)
Duration: 60 minutes
Scribes: MattC, MattS, Longley, DanB, Gregg, Nate, Brian,
==========

Proposed Agenda
---------------

1. Introduction to Anil John and DHS Blockchain R&D
   * https://www.sbir.gov/sbirsearch/detail/867797 <https://www.sbir.gov/sbirsearch/detail/867797>
2. United Nations ID2020 Summit Recap
3. Rebooting Web of Trust Design Workshop Recap
4. Update on Work Items
    * Charter
    * Use Cases
    * FAQ
    * Verifiable Claims Data Model Specification
    * Survey Results/Overview
    * One page W3C AC Rep Summary (1 page)
    * Architecture Summary (1-2 pages)
    * Implementers Summary (1 page, incorporated into survey)

-- manu

--
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: The Web Browser API Incubation Anti-Pattern
http://manu.sporny.org/2016/browser-api-incubation-antipattern/ <http://manu.sporny.org/2016/browser-api-incubation-antipattern/>