W3C home > Mailing lists > Public > public-json-ld-wg@w3.org > March 2022

Re: JSON to JSON-LD

From: Roberto Polli <robipolli@gmail.com>
Date: Mon, 7 Mar 2022 11:24:40 +0100
Message-ID: <CAP9qbHVTPYA=dOA3OXcy=NWWG3=s4FqP9L9+FQS4O_XcGi+Wrw@mail.gmail.com>
To: public-json-ld-wg@w3.org
Cc: pierre-antoine@w3.org, orie@trasmute.industries
Hi folks,

In Italy we are working on a way to embed json-ld information in
OpenAPI3 / JSON schema
files and provide tools to do it. I'd be happy to discuss the thread further.

There are:

- a related GH issue https://github.com/w3c/strategy/issues/300
- a whitepaper with various proposals, one of which  in an advanced stage
  https://docs.google.com/document/d/1fBRH2wtg1p_g4voNSTlHiSJmKgvfNaIsUXwPBO36RuM/edit#

Feedback welcome,
R.


> Dear all,

> https://github.com/transmute-industries/verifiable-data/tree/main/packages/jsonld-schema
> (JSON Schema <-> JSON-LD)
> https://github.com/google/schema-dts
> https://www.npmjs.com/package/react-structured-data
> https://www.npmjs.com/package/hylar (not exactly what you asked for, but
> one of my favorite related projects).

> The naive approach is to just push in an `@vocab` and use arrays more than
> maps.

> IMO, it's harder to make JSON-LD from other data sources, than it is to
> convert from JSON-LD to other data sources... same is true of RDF.
Received on Monday, 7 March 2022 14:53:26 UTC

This archive was generated by hypermail 2.4.0 : Monday, 7 March 2022 14:53:27 UTC