A standard JSON-LD context

[pietercolpaert]

A work item to work on a standard JSON-LD context and frame

{
    "@context" : "TODO",
    "@id": "#Collection",
    "@type": "Collection",
    "title": "My TREE collection",
    "view": {
        "@id": "", → must be the current page, so a relative IRI should always work
        "@type": "tree:Node",
        "relation": [
           {
              "@type": "GreaterThanOrEqualToRelation",
              "value":  {
                  "@value":"5",
                  "@type":"xsd:integer"
              }
              "path": "ex:number",
              "node": "?starting=5"
           }, …
        ]
     },
    "member": [
		… 
    ]
}

First part: the context should be made re-usable. When using JSON-LD examples, we should be able to assume that context is being used.

Second part: we could propose a URI for a profile in which this context is used. That way, when that profile is set, a client could parse the JSON in the member array streamingly.

This is also relevant for SEMICeu/LinkedDataEventStreams#42

[pietercolpaert]

From today’s call: let’s focus first on the context. The profile can be created as a side-project: we’ll first need to see incredible performance gains if we want to add it to the spec.