Re: Agenda for January 10 VCTF meeting

The call has been scheduled for 2am local time for quite a while.   When I am otherwise busy on related work locally (or indeed endeavouring to live on a healthy time clock) it has been difficult to participate and have done so when I have felt it was important.  One one or more occassions I've called asleep after a busy day starting at ~7:30 am or so, which is better to support these works locally.

I am working to increase the participant mix, however until such a time as that has occurred perhaps the addition of a gitter room via GitHub may also help.

I'll check the link (and the old ones) and try to ensure the thinking overtime is available for those who would benefit from it now.

Tim.h.

On Sat., 7 Jan. 2017, 5:40 pm Joe Andrieu, <joe@andrieu.net <mailto:joe@andrieu.net>> wrote:
Tim,

The use cases we'll be discussing are at https://opencreds.github.io/vc-use-cases/ <https://opencreds.github.io/vc-use-cases/>

Please suggest improvements or ask questions via the issues list at https://github.com/opencreds/vc-use-cases/issues <https://github.com/opencreds/vc-use-cases/issues>

I'll have some proposals for additions/improvements to the Needs Map and there are already twenty issues to consider, ranging from simple grammar to terminology shifts and additional content.

The more we can discuss via github issues, the easier it will be to address your concerns about time on the call.

-j

On Fri, Jan 6, 2017, at 02:32 PM, Timothy Holborn wrote:
> Maybe also basic math skills tutorial?
> 
> The allotted time (perusal) is 1 hour, and someone is leading the schedule into a format that seems to imply use of some unknown compression format.
> 
> We use standards here I thought?  Time being one of them.
> 
> Best wishes for 2017.  I suggest if the agenda items do not fit into the allotted time (ie 1 hour schedule with specified tasks and allotted time) its disingenuous to list it. (To a running sheet that says you need 1:50).
> 
> Unless some sort of other statement is implied, that is less clear?
> 
> If people believe they'll be running the broader agenda, with an array of "lockout modalities", I expect a graph / ontological response is amongst the most likely  outcomes. (If, like the compression algorithm used in your proposed agenda that does not make sense, let me know.  Happy to outline it.).
> 
> Finally, please supply the modern usecases being reviewed.  They've been stripped in past, simplified, and I believe the dignity/privacy related considerations less than clear as part of former text redactions. It's important people know what their voting for.
> 
> Tim.h.
> 
> 
> On Sat., 7 Jan. 2017, 8:21 am Varn, Richard J, <rvarn@ets.org <mailto:rvarn@ets.org>> wrote:
> Tuesday, January 10, 2017
> 
> Time: 11am ET, UTC -5
> 
> 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:+1-540-961-4469;ext=6306> (extension 6306)
> 
> Duration: 60 minutes
> 
> Scribes: DanB, NateO, KerriL, MatthewL, CarlaC, StuartS, MattS, GreggK, ShaneM, Longley, ChristopherA, Manu, DavidE, LesC, RichardV, BrianS,
> 
> 
> 
> Proposed Agenda
> 
> ---------------
> 
> 0. Agenda review and Introductions (5 mins)
> 
> 1. Vote for Verifiable Claims WG is open - Vote! (5 mins)
> 
> 2. Use Case Review (50 mins)
> 
> ----The Line---- (if time permits after the above)
> 
> 3. Use of WebIDL in spec [1] (20 min target)
> 
> 4. Privacy Section Discussion [2] (10 min intro)
> 
> 5. Part II of the GitHub tutorial (20 mins)
> 
> 
> 
> [1]https://github.com/opencreds/vc-data-model/issues/4 <https://github.com/opencreds/vc-data-model/issues/4>
> [2] https://github.com/opencreds/vc-data-model/issues <https://github.com/opencreds/vc-data-model/issues>
> 
> 
> Please let us know if there are any other items to consider at the next meeting or subsequent meetings.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.
> 
> 
> Thank you for your compliance.
> 
> 

--
Joe Andrieu, PMP
joe@andrieu.net <mailto:joe@andrieu.net>
+1(805)705-8651
http://blog.joeandrieu.com <http://blog.joeandrieu.com/>