Project to define a schema for declaring version string formats and semantic meaning therein.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
Examples
Schemas
img
xmlns
.gitignore
ExampleSchemas.html
LICENSE
README.md
VersionSchema.xpr
docHtml.css
index.html
versionschema.experimental.0.html
versionschema.experimental.0.indexList.html
versionschema.experimental.0.indexListcomp.html
versionschema.experimental.0.indexListns.html
versionschema.experimental.0.xsd
versionschema.experimental.next.html
versionschema.experimental.next.indexList.html
versionschema.experimental.next.indexListcomp.html
versionschema.experimental.next.indexListns.html
versionschema.experimental.next.xsd
versionschema_experimental_0_xsd.html
versionschema_experimental_next_xsd.html

README.md

VersionSchema

Project to define a schema for declaring version string formats and semantic meaning therein.

What's this about?

VersionSchema is all about defining what the VersionMeta tag points to. The goal is to define a domain specific language that facilitates machine reasoning over version tags and keeps humans in the loop as well. Initially, this is probably one or more of XML, JSON or YAML with a data format defined by XSD or whatever stands in for one for YAML and JSON. Much is yet to be determined here. Perhaps EBNF is the right way to go?

Official web site is http://VersionSchema.org/.

Looking for stakeholders

  • Anyone who owns an existing, documented version scheme.
  • Anyone who owns or is a major influencer/contributor to software packaging/publishing tools.
  • Anyone with any tool that reads and acts on any kind of version string.

Project Status

2018-08

  • Initial site has been posted.
  • versionschema.experimental.0.xsd is completed.
  • Started vesionschema.experimental.next.xsd for development of next release.