- From: Benjamin Young <byoung@bigbluehat.com>
- Date: Fri, 23 Aug 2019 12:19:36 +0000
- To: "public-json-ld-wg@w3.org" <public-json-ld-wg@w3.org>
- Message-ID: <DM5PR06MB3401FACF811BAA263D424D5CB2A50@DM5PR06MB3401.namprd06.prod.outlook.com>
Dear all,
Our call is today, Friday August 23rd, at 12 noon Eastern, 9am Pacific, 5pm UK, 6pm Europe.
Webex and call in information are available here: https://lists.w3.org/Archives/Member/member-json-ld-wg/2018Jun/0000.html
Agenda:
* Scribe Selection
* Approve minutes of previous call:
https://www.w3.org/2018/json-ld-wg/Meetings/Minutes/2019/2019-08-16-json-ld<https://www.w3.org/2018/json-ld-wg/Meetings/Minutes/2019/2019-08-09-json-ld><https://www.w3.org/2018/json-ld-wg/Meetings/Minutes/2019/2019-07-26-json-ld>
* Announcements / Reminders
* Standing TPAC reminder
* Others?
* Horizontal Review Updates (if any)
- https://github.com/w3c/json-ld-wg/issues?q=is%3Aissue+is%3Aopen+label%3Ahorizontal-review
* Issues:
* Encapsulate HTML processing
https://github.com/w3c/json-ld-syntax/pull/214
https://github.com/w3c/json-ld-api/pull/135
* Reconsider Processing Levels #213
https://github.com/w3c/json-ld-syntax/issues/213
* Should rel="alternate" keep the base IRI of the original document? #139
https://github.com/w3c/json-ld-api/issues/139
<https://github.com/w3c/json-ld-syntax/issues/213>
* Removing "at risk" declarations on inline issues and `<base>` handling
https://github.com/w3c/json-ld-api/pull/137
- JSON Canonicalization inline issues
- HTML `<base>` parsing requirement
* AOB?
* Adjourn
Cheers!
Benjamin
Co-Chair, W3C JSON-LD WG
--
http://bigbluehat.com/
http://linkedin.com/in/benjaminyoung
Received on Friday, 23 August 2019 12:20:02 UTC