W3C home > Mailing lists > Public > semantic-web@w3.org > May 2021

Re: Chartering work has started for a Linked Data Signature Working Group @W3C

From: Dan Brickley <danbri@danbri.org>
Date: Thu, 6 May 2021 16:40:25 +0100
Message-ID: <CAFfrAFpvG78+wAsveoeQ02WGzY-opyDUoJ=FxdtwmR-TfkQAVQ@mail.gmail.com>
To: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
Cc: semantic-web@w3.org
On Thu, 6 May 2021 at 15:27, 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.


This gets worse in RDFa, where

<p>All content on this site is licensed under
   <a

property="http://creativecommons.org/ns#license"

href="http://creativecommons.org/licenses/by/3.0/">
ALL RIGHTS RESERVED</a>.

 ©2011 Alice Birpemswick.</p>

...is a real possibility, and one that puts pressure on the
non-mathematical details around what it means for a party to sign something
which is a) not intuitive for 99.9%+ humans, b) has a human-friendly layer
entangled with it in the source document which will explicitly be discarded
before digital signing.

“Hey that’s not what I meant when I reviewed the content and signed it” is
not solved by bnode maths.

Web content saying one thing to humans and another to machines is of high
relevance to Search engines, btw.

Dan


>
> peter
>
>
>
>
Received on Thursday, 6 May 2021 15:40:54 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 6 May 2021 15:41:01 UTC