JSON $schema

[albertmink]

We have to clarify what $schema we are refering to in the serialized files:

• "$schema": "http://github.com/SAP/abap-file-formats/file-formats/clas/clas.json"
• "$schema": "https://github.com/SAP/abap-file-formats/blob/main/file-formats/clas/clas.json"
• link to completely something different: schemastore.org/abap_clas.json (just as a mirror, to make access easier)

See:
#11 (comment)

[schneidermic0]

Now, I have got your point. This is a good question. I guess we should start with the second one. Any further opinions?

[Christopher-Hermann]

I also prefer the second approach.

[xtough]

Neither the 1st, nor the 2nd approach.
1st is obviously not a valid URL, it will always yield 404.
2nd is a moving target, because blob/main may change from one minute to the next.
At least for instances of these JSON Schemas, I would prefer a stable URL like https://github.com/SAP/abap-file-formats/release/1.2.3/file-formats/clas/clas.json and for the schema ID itself something like https://github.com/SAP/abap-file-formats/release/latest/file-formats/clas/clas.json
We should look into GitHub Tags and Releases at https://docs.github.com/en/github/administering-a-repository/linking-to-releases

[albertmink]

Good input and yes, we should avoid using moving targets 😅

So, once there is a release/tag release_v.1, we can use
https://github.com/SAP/abap-file-formats/blob/release_v.1/file-formats/clas/clas.json
instead the blob/main.

[albertmink]

Once we have published the repo, urls like
https://github.com/raw/SAP/abap-file-formats/main/file-formats/clas/clas.json
would work and open the file as it is. Tagging by release/tag is preserved.
To me, this seams like the natural choice.