Adopt a methodology for versioning Json-Ld contexts

[jimmarino]

This has two aspects:

1. We should adopt the pattern developed by W3C for Json-Ld context versioning:

https://www.w3id.org/2023/dspace/v1

See here

2. We should usew3id.org to resolve context URLs.

[ssteinbuss]

Options:

• https://w3id.org/dspace/2023/v1
• https://w3id.org/dspace/v1

IDSA needs to acquire w3id.org/dspace namespace and add a list of maintainers there.

https://github.com/perma-id/w3id.org

https://w3id.org

[ssteinbuss]

started to acquire the dspace w3id https://github.com/International-Data-Spaces-Association/w3id.org/tree/master/dspace

[ssteinbuss]

• Please check the content of the READMEmd.
• Please add your contact information when appropriate to the README.md
• Which rewrite rules do we need to put into the .htaccess ?

[matgnt]

summary of the meeting today:

• we can not use raw links to the context because of rate limits (other projects had already...)
• either use gitbook or github page to publish the context.json document and then add it to the .htaccess file as a forwarding rule.

[sebbader-sap]

Decision as of 28.09.2023:

JSON-LD Context versioning topic:

Option 3: https://w3id.org/dspace/v<major>[.<minor>] --> e.g. https://w3id.org/dspace/v1.1 and https://w3id.org/dspace/v2

Hosting location of the context file:

Option 0: Start with an W3ID link to the Github raw file and move the file/adjust the link if some quota actually is reached.

[sebbader-sap]

Left before closing the issue:

• [x] adjust context URL everywhere. New one is https://w3id.org/dspace/v0.8

[jimmarino]

@ssteinbuss I think this issue can now be closed.

[sebbader-sap]

I am closing it as https://github.com/International-Data-Spaces-Association/ids-specification/issues/224#issuecomment-1945687346 contains all what we will do for this topic as much as this repo is affected.