Establish a workflow so we get updated ShEx/SHACL representations from Schema.org about schemarama

[danbri]

/cc @RichardWallis @ericprud

I believe we should likely be using Github Actions, either pulling/polling from here, or pushing out from Schema.org upon release. I haven't fully surveyed the patterns, options and issues but this blog post looks like a good start.

[danbri]

RTFM'd a little more. It seems we could install an action in schemaorg/schemaorg repo that uses this: https://github.com/peter-evans/repository-dispatch ... and which would be wired to an action here

[RichardWallis]

Following the merge of schemaorg PR #3182 the output from the shex_shacl_shapes_exporter.py script will be produced when the site is built. On the release of a schema version (next one being V15.0) those files will be copied to the schemaorg/data/releases/{version number} directory in the repo. These could then be pushed, to or pulled from, another repo such as this via an action.

Would be good if the action could work with the 'latest' schema version.

As per the schemaorg PR comments, we should work on the naming of these files.

[danbri]

suggest 'shapes' instead of 'res'

[RichardWallis]

Schemaorg 6fcbc1b implements @danbri's suggestion.

[danbri]

Fab, thanks @RichardWallis

can we test run it on webschemas before the next real release?

[RichardWallis]

Provided ./software/util/buildsite.py --release is run before deployment to weschemas the download should work from
https://webschemas.org/version/latest/schemaorg-shapes.shexj

[danbri]

Aye aye cap’n!