- From: Ryan J. McDonough <ryan@damnhandy.com>
- Date: Mon, 2 Sep 2013 14:18:42 -0400
- To: public-linked-json@w3.org
- Message-Id: <8D1186C1-A028-4FEC-9A0B-1CA607486EF6@damnhandy.com>
+1 on the JSON-LD Playground. As someone who also relatively new to JSON-LD, this has been an incredibly helpful tool. Also have a look at the RDF Translator: http://rdf-translator.appspot.com/ This is another useful tool if you're interested in determining that your JSON-LD document properly translates into other RDF formats or microdata. The combination of the two have helped me create JSON-LD output that looks more like your standard JSON while also ensuring that it's also proper RDF. Ryan- On Sep 2, 2013, at 12:59 PM, Gregg Kellogg <gregg@greggkellogg.com> wrote: > On Sep 1, 2013, at 6:36 PM, Ka-Sing Chou <ka-sing@quantumspork.nl> wrote: > >> Dear JSON-LD Community, >> >> I have been studying JSON-LD for a while and I just did an attempt to create JSON-LD based on an existing webpage. However, I have no idea if the output is correct. I really hope you guys can help me out a bit: >> >> JSON-LD: https://www.seoprovider.nl/seo-pakketten/mkb-geavanceerd.json >> Based on: https://www.seoprovider.nl/seo-pakketten/mkb-geavanceerd/ >> >> Anyway... a contextless json-ld, which contains every detailed information is also correct, right? If someone has a better idea on how I can improve this, please let me know. > > The JSON does not look like JSON-LD at all; instead, it looks like microdata JSON. To be JSON-LD, it must either have an @context, or use an external context. Moreover, JSON-LD does not keep properties under a "properties", or any other kind of container. > > A good way to check your JSON-LD is using the playground: http://json-ld.org/playground. > > Gregg > >> Big thanks in advance. >> >> -- >> Friendly regards, >> >> Ka-Sing Chou >> +31 6 - 54 76 30 81 >> ka-sing@quantumspork.nl >
Received on Tuesday, 3 September 2013 21:19:42 UTC