Add json-ld context

[brechtvdv]

No description provided.

[pietercolpaert]

Thanks @brechtvdv! If @EmidioStani’s comment can be addresses I think this is good to go!

Not blocking for the approval:

• I wonder whether we can automate this process somehow, or at least document that when adding a term to the vocabulary, we need to add it in the .ttl file and in the context file.
• We should also discuss whether we want to add a vocabulary section in the specification itself, and whether we want to add a SHACL shape to test conformance.

[brechtvdv]

Shouldn't we also add "@type": "@id" and "container": "@list" to "relations" and "view"?

[pietercolpaert]

• Container @list: certainly not as it’s not an rdf:List
• @type:@id: Would be a good idea for completeness sake, but not entirely necessary as you most probably won’t be using a JSON string value for the view thing but another object. I.e. you’ll do this:

{
 "@context": "https://w3id.org/ldes/context",
 "@id": "MyCollection",
 "view": {
    "@id":"", → indicating a relative IRI to the current page
    "relations": [ 
       {
          "@type": "tree:GreaterThanRelation",
          ...
       }
    ]
 },
 "members": [
    {
      ...
     }
 
 ]
}

Something we must do however is add a symbolic link from context to context.jsonld

By creating this JSON-LD example I also wonder whether it’s a good idea to changer the tree:member property in the plural members, but I guess in JSON that does make sense as we’re going to use an array then. The downside of it is that people might start confusing the IRI tree:member with an non-existing plural IRI.

[brechtvdv]

Thanks for the comments. Why not "views" as there can be multiple?

[pietercolpaert]

No: a page that is the one that has been fetched at this moment only has 1 tree:view property from the collection to the current page.

[brechtvdv]

But when this context is used at a catalogue page, there can be multiple?

[pietercolpaert]

This is currently not well worked out, how a catalog should look like. While I see implementations using it for that purpose I would actually refrain from doing that. See https://treecg.github.io/specification/discovery

[brechtvdv]

A PR is opened for the symbolic link: perma-id/w3id.org#4600