Re: Validator & optimizer

Hello,

I am not sure if this is relevant to your query, we're deploying a feature
to connect graphs (what you refer to as cross-listing/referencing) where I
have a graph, following your example, of movies I can reference directors
from the people graphs and the platform will automatically bring in the
data - given that the movies graph is configured to do so. This to avoid
duplicating the directors' data and be able to reference the directors'
graph from multiple "client" graphs.

In practice, given 2 entities:

Movies' Graph:
{
 "@type": "Movie"
 "director": { "@id": "https://data.example.org/directors/director_1" }
 (...omissis...)
}

and

Directors' Graph:
{
 "@type": "Director"
 "@id": "https://data.example.org/directors/director_1"
 (...omissis...)
}

the platform will automatically expand the initial graph to

[ {
 "@type": "Movie"
 "director": { "@id": "https://data.example.org/directors/director_1" }
 (...omissis...)
}, {
 "@type": "Director"
 "@id": "https://data.example.org/directors/director_1"
 (...omissis...)
} ]


This work will support in the future also data coming from 3rd party graphs
like dbpedia.org or wikidata.org.

Cheers,
David


On Thu, 21 Oct 2021 at 06:14, Hugh Paterson III <sil.linguist@gmail.com>
wrote:

> Greetings,
>
> I am familiar with the schema validator at: https://validator.schema.org
>
> I am wondering if there has been any work (theoretical or
> practical/functional) on creating a tool which optimizes JSON+LD graphs.
> In the case of schema.org and the use of the vocabulary it is possible to
> list assertions several times in the graph. Alternatively, one could
> cross-reference these entities. For example, maybe a person is listed with
> a description of who they are and some basic facts and relationships, this
> person could be listed as a director of a film listed on the same page
> along with their details, or that part of the graph could just reference
> the person in the graph somewhere else.
>
> Obviously the cross-listing/referencing strategy leads to an equally rich,
> but less verbose graph. I'm looking for a tool which would catch these
> sorts of "double listings"... does something like that exist?
>
> all the best,
> - Hugh Paterson III
>