- From: Adam Kimball <adam@akimball.org>
- Date: Wed, 11 Sep 2019 10:06:08 -0600
- To: Ghaulser Rigoti <ghaulserigoti@gmail.com>
- Cc: public-schemaorg@w3.org
Received on Wednesday, 11 September 2019 18:38:07 UTC
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 <http://schema.org/>", > "@type": "WebSite", > ... > }, > { > "@context": "http://schema.org <http://schema.org/>", > "@type": "Article", > ... > } > ] > > > Graph > { > "@context": "https://schema.org <https://schema.org/>", > "@graph": [ > { > "@type": "WebSite", > ... > }, > { > "@type": "WebPage", > ... > } > ] > } > > Greetings
Received on Wednesday, 11 September 2019 18:38:07 UTC