W3C home > Mailing lists > Public > public-privacy@w3.org > July to September 2019

Re: Privacy HR requested for JSON-LD 1.1 Syntax, API and Framing

From: Pete Snyder <psnyder@brave.com>
Date: Mon, 15 Jul 2019 11:17:31 -0700
Cc: "public-privacy (W3C mailing list)" <public-privacy@w3.org>, W3C Chairs of JSON-LD WG <group-json-ld-wg-chairs@w3.org>
Message-Id: <937BBC03-5BED-4A05-B2E3-A95722DC195E@brave.com>
To: Robert Sanderson <azaroth42@gmail.com>
Hi Robert,

Thanks for reaching out on this.  I the three documents you sent over a couple of close reads, but I still am not clear on a couple of privacy-relevant issues.  I was hoping you could clarify the following issues.  If it’d be better to discuss too, we could also schedule a call with all of PING, but that would have to wait until the next PING call (in ~2.5 weeks) and I imagine you’d like to move faster than that :)

1) I don’t see a point where the described API touches the Web API.  How is this intended to be used by applications running in the browser?

2) What privacy relevant information is sent with calls to the [documentLoader](https://www.w3.org/TR/json-ld11-api/#dom-jsonldoptions-documentloader) end point?  Cookies or similar?  If so, pulled from what origin (and single or double keyed), etc?  In general more explanation of how this interacts with the browser is needed.

3) If this is intended to be implanted in browsers, have any vendors implemented it?  Generally W3C prefers at least two independent implementations of functionality before standardizing / recommending.

4) How does the contextUrl interact with other URL / origin specific privacy features in the browser (same origin policy, CORS, etc?)

Thanks much!

Pete Snyder
Brave Software
Privacy Researcher

> On Jun 19, 2019, at 1:11 PM, Robert Sanderson <azaroth42@gmail.com> wrote:
> Dear Privacy folks,
> The JSON-LD WG hopes to move to CR about the time of TPAC or shortly thereafter.  Our working drafts are stabilizing but not 100% complete at this time.
> We would very much like to schedule a privacy review with you. We would anticipate sending one chair and one editor to the call, likely myself (Rob Sanderson) and Gregg Kellogg.
> Our TR-track specs are:
>   * https://www.w3.org/TR/json-ld11/
>   * https://www.w3.org/TR/json-ld11-api/ 
>   * https://www.w3.org/TR/json-ld11-framing/
> Many thanks!
> Rob
> -- 
> Rob Sanderson
> Semantic Architect
> The Getty Trust
> Los Angeles, CA 90049
Received on Monday, 15 July 2019 18:17:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:49:38 UTC