Re: Tagging JSON files with their purpose

Hi Andy,

Since all the terms (keys) will be mapped to use simple "tags", under what
is called a JSON-LD context, the structure would be pretty much the same.
In practical terms, the only difference would be adding some pair of
key-values to your JSON objects:
* @id in case you want to identify for further reuse of the object (really
interesting in some cases)
* @type in case you want to indicate the kind of information you share.
* @context : -> this is the context to configure everything

So the only mandatory additional thing you have to include is the @context
(only once in the document). This shouldn't be too complex since it's
always the same one.

{    "@context" : "http://w3c.github.io/opentrack-cg/contexts/opentrack.jsonld",
    "@id" : "http://w3c.github.io/opentrack-cg/examples/athlete/001Farah.jsonld",
    "@type" : "Athlete",
    "familyName" : "Farah",
    "givenName" : "Mohamed Muktar Jama",
    "alternateName" : "Mo Farah",
    "url" : "http://www.mofarah.com",
    "gender" : "Male" ,
    "birthDate" : "1983-04-23",
    "image" : "https://example.com/260px-MoPodiumRio2016.png"
}

In this example, you could omit the @id if this athlete is only valid for
this document, and @type if you don't want to specify the type of entity
you are describing (in that case that entity will be ambiguous for an
automatic processing).

This is an example of an athlete description. I suppose your representation
would be more or less the same, right?

Martin

On Tue, Jun 13, 2017 at 2:41 PM Andy Robinson <andy@reportlab.com> wrote:

> 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
>