Closed sebbader-sap closed 4 months ago
I think Option 3 is a good compromise to prevent conflicts with later versions but also prevent a "pre-release" path segment.
https://w3id.org/dspace/2024/1/context.json it is as decided in the meeting today
need to create a release and tag it as a release
@sebbader-sap will make a PR towards the w3id fork
Required steps:
Currently, we use "@context": "https://w3id.org/dspace/v0.8/context.json". However, as the "v0.8" is not the version that we will publish, we need to find a proper version tag and then use it to replace it everywhere.