Create GitHub sub-module for common tools

[rjyounes]

Include:

• Pre-commit hooks
• setup.cmd
• rdf-toolkit.jar
• Versioning validation
• Other validations (e.g., from Peter)

Not:

• bundle.yaml - this is project-specific
• LICENSE.txt - project-specific

[rjyounes]

Also add functionality proposed in #953.

[Jamie-SA]

Initial proposal:

• create a new github repository, possible name: ontokit
• move the ./tools and ./validation directories from this repo, to same directories in ontokit
• use git submodules to have ontokit show up as the ./ontokit directory in this repo
• move the setup.cmd script to the base directory of ontokit
• modify the setup.cmd and pre-commit scripts to work in this configuration and automate details of submodules as much as possible

[rjyounes]

If we implement the versioning ontology in gist as in #979, we could also put the versioning queries in ontokit. If people want to modify the queries they could still create their own versions.

Could everything that's now in gist tools also reside in ontokit?

[Jamie-SA]

Could everything that's now in gist tools also reside in ontokit?

Yes, that is my expectation.

[rjyounes]

We should also put the versioning queries into this repository.

[rjyounes]

Repository: ontology-developer-kit

[rjyounes]

In future the sub-gists could include the gist repo if we want.

[coltonglasgow]

Make sure everything from ./tools and ./validation has been copied over.

Note: Validations are currently gist specific.

[rjyounes]

Make sure everything from ./tools and ./validation has been copied over.

If validations are gist-specific in the sense of referring to gist, they should not be in the sub-module. If they are gist-specific only in the sense that they use the gist style guide, then we can include them since they enforce our conventions. Anyone who doesn't want to apply those conventions doesn't have to use them.