Tagging JSON files with their purpose

• From: Andy Robinson <andy@reportlab.com>
• Date: Tue, 13 Jun 2017 09:23:53 +0100
• To: public-opentrack <public-opentrack@w3.org>
• Message-ID: <CABjtApv-Cr-1RW_YYqV61HBiVGkfk-yx=2OVNnMvyr2dvwRCbg@mail.gmail.com>

If we're producing JSON formats (not full json-ld)  for a specific
purpose, which we still want to formalise, should we have something at
the top level to indicate the type or the schema?

For example, if the purpose is "results of some races" (like this...

    https://entries.opentrack.run/2017/not/json_results/

...should we have something at the top like this?

{

    "type": "meeting_results"

or perhaps

    "schema": "http://opentrack.run/schemas/meeting_results.json"
}

I see that the JSON-LD samples use "@type", but wonder if this is
appropriate for a message format, rather than an entity with a unique
URL.




-- 
Andy Robinson

Received on Tuesday, 13 June 2017 08:24:33 UTC