W3C home > Mailing lists > Public > public-json-ld-wg@w3.org > November 2019

Re: Using PATCH on JSON-LD?

From: Leonard Rosenthol <lrosenth@adobe.com>
Date: Mon, 18 Nov 2019 23:50:09 +0000
To: Pierre-Antoine Champin <pierre-antoine.champin@univ-lyon1.fr>, Benjamin Young <byoung@bigbluehat.com>
CC: W3C JSON-LD Working Group <public-json-ld-wg@w3.org>
Message-ID: <95B05251-3770-4497-9BB5-9D7957C823F2@adobe.com>
Great information here – thanks!  Wish it were more positive about how we might go about solving our needs – but sometimes challenges are good 😊.

In case you’re interested – this is related to the work on ISO 16684-3 (JSON-LD serialization for XMP).  One of the SME’s raised a concern about not being able to use JSON Patch to update the JSON representation as part of a metadata editing workflow.  Looks like we may have to punt that one…


From: Pierre-Antoine Champin <pierre-antoine.champin@univ-lyon1.fr>
Date: Monday, November 18, 2019 at 2:09 PM
To: Benjamin Young <byoung@bigbluehat.com>
Cc: Leonard Rosenthol <lrosenth@adobe.com>, W3C JSON-LD Working Group <public-json-ld-wg@w3.org>
Subject: Re: Using PATCH on JSON-LD?

On Mon, 18 Nov 2019 at 20:00, Benjamin Young <byoung@bigbluehat.com<mailto:byoung@bigbluehat.com>> wrote:

That actually patches the graph (and is cross format) vs. patching the representation of the graph.


It could probably do with a JSON-LD representation, though.

Amiright, Pierre-Antoine? ;)

This would not be straightforward, since LD-Patch is not encoded as an RDF graph -- it has its own internal model, which is basically a sequence of patching operations.

But I guess we could work on a flavour of LD-Patch which
* uses JSON-LD to describe the triples in each operation, or even
* uses JSON to encode the whole document...






From: Leonard Rosenthol <lrosenth@adobe.com<mailto:lrosenth@adobe.com>>
Sent: Monday, November 18, 2019 1:37 PM
To: W3C JSON-LD Working Group <public-json-ld-wg@w3.org<mailto:public-json-ld-wg@w3.org>>
Subject: Using PATCH on JSON-LD?

Have anyone used JSON Patch (https://tools.ietf.org/html/rfc6902<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc6902&data=02%7C01%7Clrosenth%40adobe.com%7Cf28706c50fce48d2cd9c08d76c5ad8e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637097009752539893&sdata=R3%2Bht7VkIg8MUhaMmBz8M6ZTEd1G1hPhUP4X8Wdj2oA%3D&reserved=0>) on JSON-LD?   Are there any concerns about `@context` in this case?   What about schemas and validation?



Received on Monday, 18 November 2019 23:50:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:15:27 UTC