- From: Henry Story <henry.story@bblfish.net>
- Date: Mon, 6 Jun 2022 10:26:02 +0200
- To: semantic-web@w3.org
- Cc: Joshua Shinavier <josh@fortytwo.net>, Eric Prud'hommeaux <eric@w3.org>
> On 5. Jun 2022, at 19:18, Henry Story <henry.story@bblfish.net> wrote: > >> >> On 3. Jun 2022, at 17:51, Eric Prud'hommeaux <eric@w3.org> wrote: >> >> On Fri, Jun 03, 2022 at 04:19:49PM +0200, Henry Story wrote: >>> >>> >>>> On 3. Jun 2022, at 12:58, Eric Prud'hommeaux <eric@w3.org> wrote: >>>> >>>>> >>>>> I’ll look into Schema Salad >>>>> https://www.commonwl.org/v1.0/SchemaSalad.html >>>> >>>> In principle, an accompanying JSON-LD @context does this for you, e.g. >>>> AVRO schema: >>> >>> Thanks Eric for those very helpful examples. (I think the data you >>> gave for the second example does not quite fit the schema, but I >>> get the point). >> >> Yeah, I had .name as a sibling of .study . > > Before looking at your ideas on avro-dl I wanted to look at Salad, > as it had Avro in the title "Semantic Annotations for Linked Avro Data”. > The problem it is trying to solve is the number of different files > doing nearly the same thing, which is something you pointed out > earlier in this thread too I think. [snip all those examples] Now I am wondering if one could not just use SHACL or ShEX to describe the binary Avro data directly? Salad is really only using Avro as a schema language, but SHACL and ShEX are that too… Could one use that instead of the json? If so it would require some retooling (how much?), but it would have the advantage of making the mapping of the binary data to RDF clear and to keep that mapping very close to the data (since Avro data cannot be understood without the schema). Henry Story PS. I opened an issue on Salad repo where I linked to this discussion https://github.com/common-workflow-language/schema_salad/issues/540 https://co-operating.systems WhatsApp, Signal, Tel: +33 6 38 32 69 84 Twitter: @bblfish
Received on Monday, 6 June 2022 08:26:18 UTC