- From: Andy Robinson <andy@reportlab.com>
- Date: Tue, 13 Jun 2017 13:38:27 +0100
- To: Martin Alvarez-Espinar <martin@w3.org>
- Cc: public-opentrack <public-opentrack@w3.org>
On 13 June 2017 at 12:41, Martin Alvarez-Espinar <martin@w3.org> wrote: > Hi Andy, > > JSON-LD is a way to represent Linked Data. Everything should be identified > by IRIs (a kind of unique web addresses). > > In your example, we want to represent a list of results. To be clear I'm NOT going to use JSON-LD for interchange between us and other competition management system, this summer. It is more work than necessary to generate it, and much more work for the people at the other end (who may have very limited programming skills circa 1995) to parse it, or to present it in results. It needs to be flat and simple and map to spreadsheets. Instead, I was asking if there is any convention in "non-LD" JSON to include metadata about the embedded content. I would be very happy to add "@type="meeting_result" if that's widely understood, or just to have our own convention that we have "type" at the top of each file. Maybe also "date_generated" Anyway, examples tomorrow should clarify.... -- Andy Robinson
Received on Tuesday, 13 June 2017 12:39:01 UTC