- From: Simon Steyskal <simon.steyskal@wu.ac.at>
- Date: Fri, 25 Jan 2019 16:05:33 +0100
- To: Benjamin Young <byoung@bigbluehat.com>, "public-json-ld-wg@w3.org" <public-json-ld-wg@w3.org>
- Message-ID: <E1gn33R-0004uR-9Z@mimas.w3.org>
regrets, will make it next week though! br simon -------- Original message --------From: Benjamin Young <byoung@bigbluehat.com> Date: 1/24/19 18:06 (GMT+01:00) To: public-json-ld-wg@w3.org Subject: [Agenda] JSON-LD Teleconference 2019-01-25 Dear all, Our next call is tomorrow, Friday January 25th, at 12 noon Eastern, 9am Pacific, 5pm UK, 6pm Europe. Call in details are available here: https://lists.w3.org/Archives/Member/member-json-ld-wg/2018Jun/0000.html This week we’ll continue to work through the sealed context issues, as we gave ourselves until the F2F in a couple weeks time to move it forward. Agenda: * Scribe Selection * Approve minutes of previous call: https://www.w3.org/2018/json-ld-wg/Meetings/Minutes/2019/2019-01-11-json-ld * Logistics * Face to Face 2/7-8, Washington DC, * Issues - Sealed Contexts * New related issues * https://github.com/w3c/json-ld-syntax/issues/116 * perhaps https://github.com/w3c/json-ld-syntax/issues/108 * Original issues discussed last week (featuring more discussion) * #20 - https://github.com/w3c/json-ld-syntax/issues/20 (main issue) * #98 - https://github.com/w3c/json-ld-syntax/issues/98 (good discussion) * #108 - https://github.com/w3c/json-ld-syntax/issues/108 (references the issue) Ideally, we should move these toward proposed syntax and API approaches prior to our F2F meeting (if possible). * AOB * Adjourn Thanks, Benjamin & Rob
Received on Friday, 25 January 2019 15:06:03 UTC