Version number

[krischer]

For this to be usable it does need some kind of versioning. What is the envisioned approach here?

I propose a continuous versioning scheme based on the output of git-describe. The version number would be of the form DRAFT-LAST GIT TAG-COMMITS SINCE TAG-SHORT HASH, e.g. DRAFT-0.0.1-10-38df8f, or (for a clean tag): DRAFT-0.0.2. The DRAFT specifier would be removed if and when the FDSN accepts the proposal.

Practically this could be set-up as a CI stage that auto-generates a schema with a fixed schemaVersion field and examples that link to the correct $schema. This would mean StationJSON would be immediately at least somewhat usable.

What do you think?

[crotwell]

+1

https://semver.org/#spec-item-10
might be useful.

When accepted version should go to 1.0.0, and may be clearer to put the draft before the 'commits since'

0.0.1-draft.10+38df8f
matches semver more closely I think.

That said, this can become bikeshedding. Versioning is important, details of what is where, not so much.

[Jollyfant]

Practically this could be set-up as a CI stage that auto-generates a schema with a fixed schemaVersion field and examples that link to the correct $schema. This would mean StationJSON would be immediately at least somewhat usable.

So every push to the repo, CI would automatically increment the version number? +1 for whatever you think is the right approach.