Re: Graph sintax

In addition to Adam's A1 reply I'll note that the popular Yoast SEO
WordPress plugin uses @graph in version 11.

In a blog post they helpfully explain their rationale in doing so....

Yoast SEO 11.0: Structured data awesomeness • Yoast
https://yoast.com/yoast-seo-11-0/

... as well as providing some more detailed technical information about
their use of @graph - which, I think, very much answers your exact
question. :)

A specification for integrating structured data • Yoast Developer Portal
https://developer.yoast.com/features/schema/specification/

On Wed, Sep 11, 2019 at 11:40 AM Adam Kimball <adam@akimball.org> wrote:

> Hi Ghaulser,
>
> Although that is an excellent question, it isn’t really one that the folks
> on this list probably worry about much.  I suggest you have a look at the
> json-ld specification here
> <https://json-ld.org/spec/latest/json-ld/#named-graphs>. In short, people
> use @graph when they need named graphs or when they are presenting data
> that doesn’t roll up into a single root.
>
> Hope that helps,
> Adam
>
>
>
> On Sep 10, 2019, at 3:29 AM, Ghaulser Rigoti <ghaulserigoti@gmail.com>
> wrote:
>
> What is the difference between using the graph syntax instead using the
> classic one in the json ld? Doest it have some advantages?
>
> Classic
> [
>   {
>     "@context": "http://schema.org",
>     "@type": "WebSite",
>     ...
>   },
>   {
>     "@context": "http://schema.org",
>     "@type": "Article",
>     ....
>   }
> ]
>
>
> Graph
> {
> "@context": "https://schema.org",
>     "@graph": [
>         {
>             "@type": "WebSite",
>             ...
>         },
>         {
>             "@type": "WebPage",
>             ...
>         }
>     ]
> }
>
> Greetings
>
>
>