published context file versionning

[simonLouvet]

Github url provide 302 response to obtain the context. If the good accept is correct, github seems to provides good response.
curl -L -H "Accept: application/ld+json" https://github.com/datafoodconsortium/ontology/releases/download/v1.11.0/context.json

json-ld playground not support this url, and we don't know why. If json-ld playground not support url, softwares using json-ld libraries don't support either.

2 Solutions

• publish context on a website
• use a proxy to provide url supported by json-ld playground
  • tested with success using grappe.io

[RaggedStaff]

In our last Ontology call, we discussed our branching strategy.

We agreed that we need to publish pre-release files to allow platforms to test/integrate.

We thought the easiest way to do this would be to use the current strategy (github latest release) for pre-release files & publish the live release files somewhere else... this could be automated through a github action, but would allow platforms to test changes before they are releases.

Could the proxy strategy you propose potentially support that strategy (we effectively need a github action to execute when we remove a pre-release tab to publish the files) ?

[RaggedStaff]

Just adding some notes from our tech call on 26/02/24:

1. We agreed to publish multiple versions of the context file - using a version number (e.g. v1.8.2) in the filename.
2. We agreed that all JSON-LD ontology artefacts would need to be aligned with that versioned context file.
3. We agreed we would move away from supporting a "latest" release in the ontology release files and require platforms to build against a named version of the standard.
4. We agreed that we would use github pages to provide the proxy service to publish the context files

Does that conform with everyone else's understanding @datafoodconsortium/tech_discussions ?

[RachL]

Thanks Garethe! I didn't had time yet to put the notes here, sorry for that.

[simonLouvet]

Finally, we use github page proxy to have usable json context file : http://docs.datafoodconsortium.org/ontology/context.json

When a new version of ontology is ready, ontology team have to produce a new file in repo in context directory :
context/constext_vxxx.json
context/constext_vyyy.json

context file in root have to be overwrite by last version.

Is it ok for you @lecoqlibre and @RaggedStaff ?

[RachL]

I think you can go ahead @simonLouvet ! I'm closing this discussion for now. Let's reopen if it does not work :)