- From: Daniel Burnett <danielcburnett@gmail.com>
- Date: Tue, 23 Jan 2018 12:49:35 -0500
- To: Charles Engelke <w3c@engelke.com>
- Cc: David Chadwick <D.W.Chadwick@kent.ac.uk>, Verifiable Claims Working Group <public-vc-wg@w3.org>
- Message-ID: <CA+Enjb+HNhaZzXp-eydbiw__wwaS=2agD3e7HdsTvxd6fOcwEA@mail.gmail.com>
I'm sorry to hear that. We appreciate all of your input and look forward to hearing from you when we're done! -- dan On Tue, Jan 23, 2018 at 10:50 AM, Charles Engelke <w3c@engelke.com> wrote: > Due to my travel schedules I've missed more of these meetings than I've > made, and haven't been able to participate meaningfully, so I am leaving > the WG. I'll be watching for your output and expect to use it when it's > ready. > > Thanks, > > Charlie > > On Tue, Jan 16, 2018 at 7:37 AM, Daniel Burnett <danielcburnett@gmail.com> > wrote: > >> Thanks David. Updated inline below. >> >> -- dan >> >> On Sat, Jan 13, 2018 at 4:23 AM, David Chadwick <D.W.Chadwick@kent.ac.uk> >> wrote: >> >>> Hi Richard >>> >>> I attach an update to ref [2] below which added the missing use case for >>> Subject Acts4 Verifier, as provided by Joe. >>> >>> Could you update the link please >>> >>> many thanks >>> >>> David >>> >>> >>> On 12/01/2018 18:42, Varn, Richard J wrote: >>> > Tuesday, Jan 16, 2018 >>> > >>> > Time: 11am Boston >>> > >>> > Text Chat: http://irc.w3.org/?channels=vcwg >>> > <https://na01.safelinks.protection.outlook.com/?url=https%3A >>> %2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__ir >>> c.w3.org_-3Fchannels-3Dvcwg%26d%3DDwMFaQ%26c%3D0YLnzTkWOdJlu >>> b_y7qAx8Q%26r%3DKheINWPzU3x8Jj96NXLwS0k5Y5jGbk-Gi1U5Cdx5914% >>> 26m%3DO4F7K-wNo0hQDkgacsvCSZnIvERoaSgITbmNAEJBiwE%26s% >>> 3DVkXa9zXhtiOI9NqCnBa1ZdI6Ust4h6ql-UFooRNcCNw%26e%3D&data= >>> 02%7C01%7Crvarn%40ets.org%7Cb6df5007c8e44206b48d08d556bc >>> 7386%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C6365102897 >>> 56815594&sdata=bAe7RV4ggc213vqO2w74KA%2B4Tq0ewJ%2FiiLNI6M% >>> 2BHtZY%3D&reserved=0> >>> > >>> > IRC://irc.w3.org:6665/#vcwg >>> > <https://na01.safelinks.protection.outlook.com/?url=https%3A >>> %2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__ir >>> c.w3.org-3A6665_-23vcwg%26d%3DDwMFaQ%26c%3D0YLnzTkWOdJlub_y7 >>> qAx8Q%26r%3DKheINWPzU3x8Jj96NXLwS0k5Y5jGbk-Gi1U5Cdx5914%26m% >>> 3DO4F7K-wNo0hQDkgacsvCSZnIvERoaSgITbmNAEJBiwE%26s%3Dc0FjBksO >>> ukpqTE60txm1rRlY2DCzZaqSjTEs-qjUOuE%26e%3D&data=02%7C01%7Cr >>> varn%40ets.org%7Cb6df5007c8e44206b48d08d556bc7386%7C0ba6e9b7 >>> 60b34fae92f37e6ddd9e9b65%7C0%7C0%7C636510289756815594&sdata >>> =kgv2YiH7%2BaqBCzP%2BJIEHigQqxnQtxWDJPo%2F5I2WKG98%3D&reserved=0> >>> > >>> > >>> > >>> > JOIN WEBEX MEETING >>> > >>> > >>> > >>> > Meeting number (access code): 644 128 007 >>> > >>> > Meeting link and password, in member email archive: >>> > >>> > https://lists.w3.org/Archives/Member/member-vc-wg/2017Aug/ >>> 0000.html >>> > <https://na01.safelinks.protection.outlook.com/?url=https%3A >>> %2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__ >>> lists.w3.org_Archives_Member_member-2Dvc-2Dwg_2017Aug_0000.h >>> tml%26d%3DDwMFaQ%26c%3D0YLnzTkWOdJlub_y7qAx8Q%26r%3DKheINWPz >>> U3x8Jj96NXLwS0k5Y5jGbk-Gi1U5Cdx5914%26m%3DO4F7K-wNo0h >>> QDkgacsvCSZnIvERoaSgITbmNAEJBiwE%26s%3Dkboh5wefrltQtz5nPOwGU >>> E5V9KqjukagQ-PcnfojdD4%26e%3D&data=02%7C01%7Crvarn%40ets.org >>> %7Cb6df5007c8e44206b48d08d556bc7386%7C0ba6e9b760b34fae92f37e >>> 6ddd9e9b65%7C0%7C0%7C636510289756815594&sdata=ETYRDptD60HGkq >>> qYLTsyaRI51fWzzAP91kBKHhTfy%2Bo%3D&reserved=0> >>> > >>> > NOTE: The above URL and password are new as of 8 Aug 2017. The URL >>> and >>> > password are not to be shared due to continued misuse of the WebEx >>> > international calling function. >>> > >>> > >>> > >>> > Toll number: +1-617-324-0000 <tel:(617)%20324-0000> >>> > >>> > Mobile Auto Dial:+1-617-324-0000 <tel:(617)%20324-0000>,,,644128007# >>> > >>> > >>> > >>> > If you do not or cannot connect on the WebEx session, you must identify >>> > yourself to the chairs so that we can link the participants to the >>> > unidentified dialed-in numbers at the start of the call in order to >>> > comply with the rules for participation and disclosure. >>> > >>> > >>> > >>> > >>> > >>> > Duration: 60 minutes >>> > >>> > Scribes: JonnyCrunch, AdamL, DavidE, MattS, AdamM, RichardV, TallTed, >>> > DanB, CharlesE, ChrisW, DavidL, GreggK, Longley, DavidC, Manu, JoeA, >>> > NathanG, MattL >>> > >>> > >>> > >>> > Topic Time (m) >>> > >>> > 1-Agenda review, Introductions, Re-introductions (5 min) >>> > >>> > 2-Vote on potential spring meeting dates--Monday March 5 or Friday >>> April >>> > 6 [1] (10 min) >>> > >>> > 3-Volunteer assignments on subject != holder chart review [2] (10 >>> min) >>> > >>> > 4a-CG alignment/Coordination Update--DID Method Registry [3] (10 min) >>> > >>> > 4b-Linked Data Key Types Registry [4] ( min) >>> > >>> > 4c-Credential Status Method Registry [5] ( min) >>> > >>> > 5-Domain Discussion of the Week (Use Cases) [6] (10 min) >>> > >>> > 6-Data Model Outstanding PRs (checkin) [7] (10 min) >>> > >>> > 7-Test Suite and Implementation Progress (5 min) >>> > >>> > >>> > >>> > [1] >>> > https://docs.google.com/spreadsheets/d/19Ndqc5pLsTu2ZmP4Wy7O >>> lMOmskQFHPh28sMjW3ugsww/edit#gid=0 >>> > >>> > >>> > >>> > [2] >>> > https://lists.w3.org/Archives/Public/public-vc-wg/2017Dec/at >>> t-0016/SubjectHolder.jpeg >>> >> >> Updated link is https://lists.w3.org/Archives/Public/public-vc-wg/2018Jan >> /att-0006/SubjectHolder.jpg >> >>> >>> > >>> > >>> > >>> > [3] http://bit.ly/2AHJ1KG >>> > >>> > >>> > >>> > [4] http://bit.ly/2jfhpZs >>> > >>> > >>> > >>> > [5] https://w3c-ccg.github.io/vc-status-registry/ >>> > >>> > >>> > >>> > [6] https://goo.gl/7Tj6oV >>> > >>> > >>> > >>> > [7] https://github.com/w3c/vc-data-model/pulls >>> > >>> > >>> > >>> > ===== >>> > >>> > Richard Varn >>> > >>> > >>> > >>> > >>> > ------------------------------------------------------------ >>> ------------ >>> > >>> > 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. >>> > >>> > ------------------------------------------------------------ >>> ------------ >>> >> >> >
Received on Tuesday, 23 January 2018 17:50:53 UTC