- From: Ivan Herman <ivan@w3.org>
- Date: Thu, 6 May 2021 19:01:10 +0200
- To: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
- Cc: semantic-web@w3.org
- Message-Id: <D47E1F24-00D4-41D4-ABFB-1E923CA75AB1@w3.org>
Peter, just to make it clear (and that was, I believe, Manu's intentions, too). The WG charter does not, will not, shall not propose JCS as an alternative; the proposed work is on the RDF abstract syntax. The only thing we have to acknowledge is that there are communities out there that do that, and we cannot ignore this. It does not have a bearing on what the WG would do except, maybe, to be sure that it does not make it actively _impossible_ for someone to follow that route on a JSON-LD serialization of the RDF Data (although, to be honest, I would not even know what we would do that would make that impossible). Cheers Ivan > On 6 May 2021, at 15:39, Peter F. Patel-Schneider <pfpschneider@gmail.com> wrote: > > But JCS doesn't work for signing JSON-LD, as it is too discriminative. For example, the two JSON-LD strings > > { > "@context": { > "name":"http://schema.org/name" > }, > "name": "Manu Sporny", > "status": "trollin'" > } > > and > > { > "@context": { > "name":"http://schema.org/name" > }, > "name": "Manu Sporny" > } > > represent the same linked data, but have different JCS forms. > > peter > > > ---- Ivan Herman, W3C Home: http://www.w3.org/People/Ivan/ mobile: +33 6 52 46 00 43 ORCID ID: https://orcid.org/0000-0003-0782-2704
Received on Thursday, 6 May 2021 17:01:34 UTC