Testing the compliance of a develop stage version without a triple

#1

Hello,

We would like to test the draft of the version of our vocabulary https://archivo.dbpedia.org/info?o=http%3A//open-services.net/ns/core but we have a process for making changes to prod: https://github.com/oslc-op/oslc-specs/pull/461 (i.e. this PR will only land on master, there is another process to actually deploy a new spec to the NS, which is connected to the progression of the standard).

We would like to be able to simply submit a document from Github and get it checked as if it was a develop stage version.

We will also discuss making an exception for the archivo:trackThis triple but it may be tricky to tag it as errata to the old spec.

Alternatively, is there a way to package some executable in a Docker container and run it as a GIthub Action in the CI build?

Best regards,
Andrew

#2

Hi,

We would like to be able to simply submit a document from Github and get it checked as if it was a develop stage version.

so the file on github should be treated as a develop stage version automatically once these changes (https://github.com/oslc-op/oslc-specs/pull/461) are available at http://open-services.net/ns/core#.

We will also discuss making an exception for the archivo:trackThis triple but it may be tricky to tag it as errata to the old spec.

Iā€™m not sure if I understand what exactly the problem is with adding that triple, maybe you can elaborate that a bit further.

Alternatively, is there a way to package some executable in a Docker container and run it as a GIthub Action in the CI build?

No there is no such thing (yet), unfortunately the only way right now is by using that triple.
But for the future it could be a nice feature to have, we will discuss if we should implement it.

Best Regards,
Denis

1 Like
#3

Hi again,

I added the develop stage version by hand: http://archivo.dbpedia.org/info?o=http%3A//open-services.net/ns/core%23&dev
So you dont have to wait until the github version is officially deployed.

Have a nice day,
Denis

1 Like
#4

Hello Denis,

Thank you so much for making an exception! It is very helpful as we usually need to take a vote to promote the vocabularies under the /ns and we have only done that when a new version of the spec is voted.

Best regards,
Andrew