Would adding a dcterms:created triple to the import modules & release artefacts make sense?

Currently, ODK assumes a workflow where the versioning is using dates instead of SemVer, as the OBO community uses a date based versioning scheme.
If ODK is used by someone outside of the OBO community and would like to rather use SemVer or some other versioning scheme, the `VERSION` variable given in the Makefile would have to be overwritten in the custom Makefile. To be able to indicate the release date of the import modules and the release artefacts an additional dcterms:created triple should then be provided as a best practice. This can be done by overwriting the `ANNOTATE_ONTOLOGY_VERSION` variable in ones custom.Makefile with: `annotate -V $(ONTBASE)/releases/$(VERSION)/$@ --annotation owl:versionInfo $(VERSION) --annotation dcterms:created $(TODAY)`.

Now, I'm wondering if it would make sense to also add this dcterms:created triple to the standard ODK Makefile, to make the creation date semantically more explicit, although it is implicitly already provided in the owl:versionInfo triple in the standard ODK setup. I don't think there is an immidiate need for this, but indexing/look-up services, like OLS or Bioportal, might have a use case to utilize this triple.

Review the standard ODK Makefile and the ANNOTATE_ONTOLOGY_VERSION variable, using the custom Makefile example in the issue as the starting point. Determine whether dcterms:created should be added for import modules and release artefacts, and confirm that the chosen annotation is consistently present in the generated outputs.

Written by the indexing model from the issue text.