Properly handle json-ld syntax

In JSON-LD, every key not starting with a @ (including id when working with contexts that map id to @id) can be an array, an object containing at least @id or @value, or an array of such objects. When specs constrain the domain, that constraint applies semantically to the @value or the @id, not to the syntax itself.

• !1 (comment 202989)
• !1 (comment 202686)

mentioned in merge request !1 (merged)

In JSON-LD, every key not starting with a @ (including id when working with contexts that map id to @id) can be an array, an object containing at least @id or @value, or an array of such objects. When specs constrain the domain, that constraint applies semantically to the @value or the @id, not to the syntax itself.

Oh yeah, forgot about that, that's why you recommended json-ld expansion instead of compaction to validate / handle the payload ?

Indeed. That's what we do in swh-search.

An other option is to use a graph API like RDFlib, like we do in swh-indexer

ok thanks, I will keep it as-is for now and keep this issue open to see when should we should schedule a proper payload parser/validator

changed title from identify which properties could be array or objects in the payload to Properly handle json-ld syntax

changed the description