semantic-versioning/semantic-versioning-w3c
17
0
Fork 0
Code Issues 1 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

Update_index.bs #3

Open
eugen.thaci wants to merge 2 commits from eugen.thaci-master-patch-07132 into master
pull from: eugen.thaci-master-patch-07132
merge into: semantic-versioning:master
Conversation 1 Commits 2 Files Changed 1
+142 -62
1 changed files with 142 additions and 62 deletions
Download Patch File Download Diff File Expand all files Collapse all files
index.bs
+142 -62
View File
@@ -1,9 +1,8 @@
<pre class='metadata'>
Title: Semantic Versioning
Title: Clever Semantic Versioning
H1: v3.0.0, W3C Draft, 30 March 2024
Shortname: Semantic Versioning
Abstract: Semantic Versioning is a specification for versioning of software and related artifacts. It ensures versions are predictable and meaningful adding semantics to versioning.
Date: 2024-03-30
Shortname: Clever Semantic Versioning
Date: 2025-03-30
Level: 3
Status: LS
Complain About: accidental-2119 on, broken-links on, missing-example-ids on
@@ -27,40 +26,46 @@ Editor: Jeffrey Phillips Freeman, CleverThis https://CleverThis.com, Jeffrey.Fre
!Contributor: <a class="p-name fn u-url url" href="https://Rui.Hu.u.CleverThis.com">Rui Hu</a> (<a class="p-org org" href="https://CleverThis.com">CleverThis</a>) <a class="u-email email" href="mailto:Rui.Hu@CleverThis.com">Rui.Hu@CleverThis.com</a>
!Contributor: <a class="p-name fn u-url url" href="https://Stanislav.Hejny.u.CleverThis.com">Stanislav Hejny</a> (<a class="p-org org" href="https://CleverThis.com">CleverThis</a>) <a class="u-email email" href="mailto:Stanislav.Hejny@CleverThis.com">Stanislav.Hejny@CleverThis.com</a>
!Contributor: <a class="p-name fn u-url url" href="https://Luis.Mendes.u.CleverThis.com">Luis Mendes</a> (<a class="p-org org" href="https://CleverThis.com">CleverThis</a>) <a class="u-email email" href="mailto:Luis.Mendes@CleverThis.com">Luis.Mendes@CleverThis.com</a>
!Contributor: <a class="p-name fn u-url url" href="https://madeline.pace.u.CleverThis.com">Madeline Pace</a> (<a class="p-org org" href="https://CleverThis.com">CleverThis</a>) <a class="u-email email" href="mailto:madeline.pace@CleverThis.com">madeline.pace@CleverThis.com</a>
!Contributor: <a class="p-name fn u-url url" href="https://Madeline.Pace.u.CleverThis.com">Madeline Pace</a> (<a class="p-org org" href="https://CleverThis.com">CleverThis</a>) <a class="u-email email" href="mailto:madeline.pace@CleverThis.com">madeline.pace@CleverThis.com</a>
!Contributor: <a class="p-name fn u-url url" href="https://Josi.Rosenfeld.u.CleverThis.com">Josi Rosenfeld</a> (<a class="p-org org" href="https://CleverThis.com">CleverThis</a>) <a class="u-email email" href="mailto:Josi.Rosenfeld@CleverThis.com">Josi.Rosenfeld@CleverThis.com</a>
!Contributor: <a class="p-name fn u-url url" href="https://Bilal.Benmahria.u.CleverThis.com">Bilal Ben Mahria</a> (<a class="p-org org" href="https://CleverThis.com">CleverThis</a>) <a class="u-email email" href="mailto:Bilal.Benmahria@CleverThis.com">Bilal.Benmahria@CleverThis.com</a>
!Contributor: <a class="p-name fn u-url url" href="https://Hamza.Khyari.u.CleverThis.com">Hamza Khyari</a> (<a class="p-org org" href="https://CleverThis.com">CleverThis</a>) <a class="u-email email" href="mailto:Hamza.Khyari@CleverThis.com">Hamza.Khyari@CleverThis.com</a>
!Contributor: <a class="p-name fn u-url url" href="https://Aditya.Chhabra.u.CleverThis.com">Aditya Chhabra</a> (<a class="p-org org" href="https://CleverThis.com">CleverThis</a>) <a class="u-email email" href="mailto:Aditya.Chhabra@CleverThis.com">Aditya.Chhabra@CleverThis.com</a>
!Contributor: <a class="p-name fn u-url url" href="https://Adnaan.Nazir.u.CleverThis.com">Adnaan Nazir</a> (<a class="p-org org" href="https://CleverThis.com">CleverThis</a>) <a class="u-email email" href="mailto:Adnaan.Nazir@CleverThis.com">Adnaan.Nazir@CleverThis.com</a>
!Contributor: <a class="p-name fn u-url url" href="https://Aleena.Umair.u.CleverThis.com">Aleena Umair</a> (<a class="p-org org" href="https://CleverThis.com">CleverThis</a>) <a class="u-email email" href="mailto:Aleena.Umair@CleverThis.com">Aleena.Umair@CleverThis.com</a>
!Contributor: <a class="p-name fn u-url url" href="https://Eugen.Thaci.u.CleverThis.com">Eugen Thaci</a> (<a class="p-org org" href="https://CleverThis.com">CleverThis</a>) <a class="u-email email" href="mailto:Eugen.Thaci@CleverThis.com">Eugen.Thaci@CleverThis.com</a>
</pre>
# Abstract
Clever Semantic Versioning is a specification for versioning software and related artifacts. It ensures versions are predictable and meaningful by adding semantics to versioning. Unlike the widely known specification at SemVer.org, it extends versioning beyond APIs, refining its scope to address gaps and ambiguities, making it more suited to modern development workflows.
# Status of This Document
*This section describes the status of this document at the time of its publication. A list of current W3C publications can be found in the [W3C technical reports index](https://www.w3.org/TR/) at https://www.w3.org/TR/.*
By publishing this document, W3C acknowledges that the [Submitting Members](https://www.w3.org/submissions/2024/SUBM-semantic-versioning-20241127/) have made a formal Submission request to W3C for discussion. Publication of this document by W3C indicates no endorsement of its content by W3C, nor that W3C has, is, or will be allocating any resources to the issues addressed by it. This document is not the product of a chartered W3C group, but is published as potential input to the [W3C Process](https://www.w3.org/policies/process/). A [W3C Team Comment](https://www.w3.org/submissions/2024/02/Comment/) has been published in conjunction with this Member Submission. Publication of acknowledged Member Submissions at the W3C site is one of the benefits of [W3C Membership](https://www.w3.org/Consortium/Prospectus/Joining). Please consult the requirements associated with Member Submissions of [section 3.3 of the W3C Patent Policy](https://www.w3.org/policies/patent-policy/#sec-submissions). Please consult the complete [list of acknowledged W3C Member Submissions](https://www.w3.org/submissions/).
# Overview
Given a version number
```
MAJOR.MINOR.PATCH-EXTRA+META
```
, increment the:
Given a version number `MAJOR.MINOR.PATCH-EXTRA+META`, increment the:
1. *MAJOR* version when you make backwards incompatible changes
1. *MAJOR* version when you make backward incompatible changes
1. *MINOR* version when you add functionality in a backward compatible manner
1. *PATCH* version when you make backward compatible bug fixes
1. *EXTRA* version when you make a new prerelease, or other extra versioning parameters
1. *EXTRA* version when you make a new pre-release, or other extra versioning parameters
<div class="note">
EXTRA Has a natural ordering, specified below, may contain any alphanumeric characters, in addition to dots, and additional dashes
The EXTRA version follows a natural ordering (specified below) and *MAY* contain alphanumeric characters, dots, and additional dashes.
</div>
<div class="note">
META metadata is non-ordered, this does not increment
The META version consists of metadata, which is non-ordered and does not increment.
</div>
# Clever Semantic Versioning Specification
# Semantic Versioning Specification
The keywords "*MUST*", "*MUST NOT*", "*REQUIRED*", "*SHALL*", "*SHALL NOT*", "*SHOULD*","*SHOULD NOT*", "*RECOMMENDED*", "*MAY*", and "*OPTIONAL*" in this document are to be interpreted as described in [RFC 2119](https://tools.ietf.org/html/rfc2119).
The key words "*MUST*", "*MUST NOT*", "*REQUIRED*", "*SHALL*", "*SHALL NOT*", "*SHOULD*","*SHOULD NOT*", "*RECOMMENDED*","*NOT RECOMMENDED*", "*MAY*", and "*OPTIONAL*" in this document are to be interpreted as described in [BCP 14](https://www.rfc-editor.org/info/bcp14) [\[RFC2119\]](https://datatracker.ietf.org/doc/html/rfc2119) [\[RFC8174\]](https://datatracker.ietf.org/doc/html/rfc8174) when, and only when, they appear in all capitals, as shown here.
<ol class="algorithm">
<li>A normal version number *MUST* take the form `X.Y.Z` where `X`, `Y`, and `Z` are non-negative integers, and *MUST NOT* contain leading zeroes. `X` is the major version, `Y` is the minor version, and `Z` is the patch version. `X`, `Y`, and `Z` *MUST* be representable in a thirty-two-bit unsigned integer, i.e. strictly less than 4,294,967,296.</li>
@@ -79,7 +84,7 @@ The keywords "*MUST*", "*MUST NOT*", "*REQUIRED*", "*SHALL*", "*SHALL NOT*", "*S
<li>Extra version *MAY* be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. Identifiers *MUST* comprise only ASCII alphanumerics and hyphens [0-9A-Za-z-]. Identifiers *MUST NOT* be empty. Numeric identifiers *MUST NOT* include leading zeroes. Extra versions have a lower precedence than the associated normal version. An extra version containing only purely numeric identifiers represents a subversion and will follow the same format and rules as a normal version (see dependent version class below). Any other extra version indicates a pre-release and that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version.</li>
<li>Build metadata MAY be denoted by appending a plus sign and a series of dot separated identifiers immediately following the patch or pre-release version. Identifiers *MUST* comprise only ASCII alphanumerics and hyphens `[0-9A-Za-z-]`.Identifiers *MUST NOT* be empty. Build metadata *MUST* be ignored when determining version precedence. Thus two versions that differ only in the build metadata, have the same precedence.</li>
<li>Build metadata MAY be denoted by appending a plus sign and a series of dot separated identifiers immediately following the patch or extra version. Identifiers *MUST* comprise only ASCII alphanumerics and hyphens `[0-9A-Za-z-]`.Identifiers *MUST NOT* be empty. Build metadata *MUST* be ignored when determining version precedence. Thus two versions that differ only in the build metadata, have the same precedence.</li>
<li>A version number *MUST* be no longer than 255 characters, including extra version and build metadata.</li>
@@ -103,7 +108,7 @@ The keywords "*MUST*", "*MUST NOT*", "*REQUIRED*", "*SHALL*", "*SHALL NOT*", "*S
<li>Numeric identifiers always have lower precedence than non-numeric identifiers.</li>
<li>A larger set of pre-release fields has a higher precedence than a smaller set, if all of the preceding identifiers are equal.</li>
<li>A larger set of extra identifiers fields has a higher precedence than a smaller set, if all of the preceding identifiers are equal.</li>
</ol>
@@ -138,107 +143,134 @@ Example version precedence:
## Version Classes
While the general meaning of a PATCH, MINOR, and MAJOR version are defined in the specification above the specific interpretation is not always clear depending on the class of resources you happen to be versioning. An API, Schema, or even an application would all interpret when to bump a version a bit differently. Therefore we have tried to define explicitly versioning rules for the various classes of resources of interest. Any class not covered in this specification is technically not covered by it, but it is still recommended the general principles outlined in the specification above still be adhered to when possible.
While the general meaning of a PATCH, MINOR, and MAJOR version are defined in the specification above the specific interpretation is not always clear depending on the class of resources you happen to be versioning. An API, Schema, or even an application would all interpret when to increment a version a bit differently. Therefore we have tried to define explicitly versioning rules for the various classes of resources of interest. Any class not covered in this specification is technically not covered by it, but it is still recommended that the general principles outlined in the specification above be adhered to when possible.
<div class="advisement">
When picking a version class we only care about **exposed** components. Internal APIs, internal data, and dependencies shouldn't affect versioning. The exposed components being versions, and the versioning class being used, should always be explicitly stated by the project owners.
When picking a version class we only care about **exposed** components. Internal APIs, internal data, and dependencies *SHOULD NOT* affect versioning. The exposed components being versioned, and the versioning class being used, *SHOULD* always be explicitly stated by the project owners.
</div>
When a artifact covers several exposed components that are either of different versioning classes, or just make sense to version separately then they should always be versioned separately. The overall artifact version can be determined by the hybrid versioning class mentioned below.
When an artifact covers several exposed components that are either of different versioning classes, or just make sense to version separately then they *SHOULD* always be versioned separately. The overall artifact version can be determined by the hybrid versioning class mentioned below.
### API Versioning
When, versioning software with a public API such as libraries, and web endpoints it must match the following criteria:
When versioning software with a public API such as libraries, and web endpoints it *MUST* match the following criteria:
1. The resource *MUST* declare a public API.
1. The API must be declared as code or specification documentation.
1. The API *MUST* be declared as code or specification documentation.
For any artifact of this type the meaning of incrementing the components of a version are as follows:
* *PATCH* - An internal fix to bring behavior in compliance with the documented expected behavior for the public API; this should implement no changes to the public API signatures.
* *MINOR* - If new functionality is added to the public API in a backwards compatible way, including new information in the return values.
* *MAJOR* - Any change to the public API that breaks backwards compatibility.
* *PATCH* - An internal fix to bring behavior in compliance with the documented expected behavior for the public API; this *SHOULD NOT* implement changes to the public API signatures.
* *MINOR* - If new functionality is added to the public API in a backward compatible way, including new information in return values. Additionally, if any public functionality is marked as deprecated, but remains available to maintain backward compatibility, the MINOR version *MUST* be incremented.
* *MAJOR* - Any change to the public API that breaks backward compatibility.
This specification guarantees backward compatibility with [SemVer.org](https://semver.org/) version 2.0 and only version 2.0. However, forward compatibility with future versions is not guaranteed. Implementers *SHOULD* ensure their systems are designed with this limitation in mind.
### UI Versioning
When versioning User Interfaces which may have any nature of input whether it be command-line, GUI, or some other interface, the following paradigm should be used. The following criteria must be satisfied:
When versioning User Interfaces which *MAY* have any nature of input whether it be command-line, GUI, or some other interface, the following paradigm *SHOULD* be used. The following criteria *MUST* be satisfied:
1. The resource must have a user interface of some kind, both command-line and GUI are acceptable.
1. The resource *MUST* have a user interface of some kind, of which both command-line and GUI are acceptable.
For any artifact of this type the meaning of incrementing the components of a version are as follows:
For any artifact of this type the meaning of incrementing the components of a version is as follows:
* *PATCH* - An internal fix to bring behavior in compliance with the documented expected behavior for the UI; this should implement no changes to the user interface of any kind.
* *MINOR* - Any backwards compatible changes to the UI. Backwards compatible means while new entries and elements can be added the existing ones should retain their same name, exist somewhere within the same menu items and menu structure, and behave consistently as they have in the past (or fixed according to the documented and expected behavior). This applies to all language variants of the interface.
* *MAJOR* - Any change to any of the interface in any language, that breaks backwards compatibility.
* *PATCH* - An internal fix to bring behavior in compliance with the documented expected behavior for the UI; this *SHOULD* implement no changes to the user interface of any kind.
* *MINOR* - Any backward compatible changes to the UI. Backward compatible means while new entries and elements can be added the existing ones *SHOULD* retain their same name, exist somewhere within the same menu items and menu structure, and behave consistently as they have in the past (or fixed according to the documented and expected behavior). This applies to all language variants of the interface.
* *MAJOR* - Any change to any of the interface in any language, that breaks backward compatibility.
### Dataset Versioning
When, versioning datasets which may have the schema versioned alongside or separately. A dataset may include such things as a RDBMS database, a Semantic Web Knowledge Graph, or an XML file. Such Datasets must describe the following:
When versioning datasets, the schema (see `([Schema Versioning](#schema-versioning))`) *MAY* be versioned alongside the dataset or separately. A dataset *MAY* include such things as a RDBMS database, a Semantic Web Knowledge Graph, or an XML file. Such Datasets *MUST* describe the following:
1. Public structured data for which access is being provided.
For any artifact of this type the meaning of incrementing the components of a version are as follows:
<div class="advisement">
Anytime the underlying schema experiences an increase in any of its version's parts then the dataset must at least increment its version corresponding part, or a more significant part.
Anytime the underlying schema experiences an increase in any of its version's parts then the dataset *MUST* at least increment its version corresponding part, or a more significant part.
</div>
* *PATCH* - Additional rows / instances have been added to your dataset. This *MUST* also be incremented when incremented on the schema.
* *MINOR* - Additional, backwards compatible, information is provided about existing rows/individuals. This *MUST* increment when MINOR is incremented in the underlying schema (see schema versioning below).
* *MAJOR* - Non-backwards compatible changes to the data or underlying schema. This *MUST* be incremented when MAJOR is incremented in the underlying schema.
* *MINOR* - Additional, backward compatible, information is provided about existing rows/individuals. This *MUST* increment when MINOR is incremented in the underlying schema.
* *MAJOR* - Non-backward compatible changes to the data or underlying schema. This *MUST* be incremented when MAJOR is incremented in the underlying schema.
<div class="advisement">
Backward compatibility for datasets may depend on the specific use case. In general, a dataset change is considered backward compatible if it does not alter existing data structures, remove information, or require modifications to existing queries consuming the dataset.
</div>
### Schema Versioning
When, versioning schemas for reading or interacting with data sets, for example, RDBMS Schema, Semantic Web Ontologies, and XML Schemas. Such schemas must describe the following:
When versioning schemas for reading or interacting with datasets—such as RDBMS Schemas, Semantic Web Ontologies, and XML Schemas—the schema *MUST* describe the following:
1. Public structured data whose schema is being defined.
1. You are versioning the schema independently of the dataset or you are versioning the schema and not the dataset.
For any artifact of this type the meaning of incrementing the components of a version are as follows:
* *PATCH* - Additional or improved validation, indexing, and other backwards compatible improvements that do not introduce new data. Also data's structure and typing is unchanged except for bugs contrary to the documented expected behavior.
* *MINOR* - Additions only to the schema allowing access to new underlying data while not changing the structure of historic data.
* *MAJOR* - Any changes to the structure of the data preventing bachwards-compatible access to historic data.
* *PATCH* - Additional or improved validation, indexing, and other backward compatible improvements that do not introduce new data. Also data's structure and typing is unchanged except for bugs contrary to the documented expected behavior.
* *MINOR* - Additions only to the schema allowing access to new underlying data while not changing the structure of historical data.
* *MAJOR* - Any changes to the structure of the data preventing backward compatible access to historical data.
### Hybrid Versioning
When, versioning artifacts that contain multiple resources that should be versioned separate, which is required when you have public interfaces that represent 2 or more of the version classes listed here, then you must use hybrid versioning. To use Hybrid Versioning the following criteria must be met.
When versioning artifacts that contain multiple resources that *SHOULD* be versioned separately, which is required when you have public interfaces that represent two or more of the version classes listed here, then you *MUST* use hybrid versioning. To use Hybrid Versioning the following criteria *MUST* be met.
1. The artifact must include 2 or more publicly exposed components that can be defined by one of the versioning classes outlined here.
1. The exposed components must be of either different versioning classes, or are versioned separately.
Each versioned public component receives a version that is independent and according to the rules of it's versioning class. In addition the overall artifact gets an additional version, this version will increment one of its parts depending on the *most significant* version change across all its other interfaces. Bumping at most one version step. The specific parts of the version behave as follows:
1. The artifact *MUST* include two or more publicly exposed components that can be defined by one of the versioning classes outlined here.
1. The exposed components *MUST* be of either different versioning classes, or are versioned separately.
When versioning an artifact with multiple hybrid versions each versioned public component receives an independent version according to the rules of its versioning class. In addition the overall artifact gets an additional version, this version will increment one of its parts depending on the *most significant* version change across all its other interfaces, incrementing at most one version step. The specific parts of the version behave as follows:
* *META* - This will be dropped or assigned at the package maintainers discretion. Never expect it to be an ordered value.
* *EXTRA* - Increment this when the most significant version bump among your other components was a bump to the EXTRA version. This field may not reset when a higher position resets. It will always be, at a minimum, the lowest value, if any, after reset, from all its subcomponents.
* *PATCH* - Increment this when the most significant version bump among your other components was a bump to the PATCH version.
* *MINOR* - Increment this when the most significant version bump among your other components was a bump to the MINOR version.
* *MAJOR* - Increment this when the most significant version bump among your other components was a bump to the MAJOR version.
* *EXTRA* - Increment this when the most significant version change among your other components was an EXTRA version increase. This field *MAY* not reset when a higher position resets. It will always be, at a minimum, the lowest value, if any, after reset, from all its subcomponents.
* *PATCH* - Increment this when the most significant version change among your other components was a PATCH version increase.
* *MINOR* - Increment this when the most significant version change among your other components was a MINOR version increase.
* *MAJOR* - Increment this when the most significant version change among your other components was a MAJOR version increase.
<div class="example">
Example hybrid version jumps based on the version changes in its other components.
`1.0.0-alpha` -> `1.0.0-beta` if `2.6.7-alpha` -> `2.6.7-beta`, `1.8.3+102` -> `1.8.3+111`
`1.0.0-alpha` -> `1.0.1-beta` if `2.6.7-alpha` -> `2.6.7-beta`, `1.8.3+102` -> `1.8.4`
`1.0.0-alpha` -> `1.1.0` if `2.6.7-alpha` -> `2.6.7`, `1.8.3+102` -> `1.10.3`
`1.0.0-alpha` -> `1.1.0` if `2.6.7-alpha` -> `2.6.7+112`, `1.8.3+102` -> `1.10.3+113`
<table>
<thead>
<tr>
<th> Composite Artifact </th>
<th> Component 1 </th>
<th> Component 2 </th>
</tr>
</thead>
<tbody>
<tr>
<td><code>1.0.0-alpha → 1.0.0-beta</code></td>
<td><code>2.6.7-alpha → 2.6.7-beta</code></td>
<td><code>1.8.3+102 → 1.8.3+111</code></td>
</tr>
<tr>
<td><code>1.0.0-alpha → 1.0.1-beta</code></td>
<td><code>2.6.7-alpha → 2.6.7-beta</code></td>
<td><code>1.8.3+102 → 1.8.4</code></td>
</tr>
<tr>
<td><code>1.0.0-alpha → 1.1.0</code></td>
<td><code>2.6.7-alpha → 2.6.7</code></td>
<td><code>1.8.3+102 → 1.10.3</code></td>
</tr>
<tr>
<td><code>1.0.0-alpha → 1.1.0</code></td>
<td><code>2.6.7-alpha → 2.6.7+112</code></td>
<td><code>1.8.3+102 → 1.10.3+113</code></td>
</tr>
</tbody>
</table>
</div>
## Dependent Artifact Versioning
On occasion you have software that needs to be versioned relative to the version it is written against. Example projects, and schema-extensions are good examples of this. Such software should have the following criteria.
On occasion you have software that needs to be versioned relative to the version against which it is written. Example projects and schema-extensions are good examples of this. Such software *SHOULD* have the following criteria:
1. Its version only makes sense relative to the base projects version.
1. The version of the base project will always be treated as a more significant digit than the version of this project. Such that.
1. The version of the base project will always be treated as a more significant digit than the version of this project.
When using this versioning paradigm the *EXTRA* field is used to embed this projects encoding. The *EXTRA* field effectively embeds a second version that follows all the same rules as a standalone normal version. The fully expanded format for a version with this paradigm would now be `MAJOR_BASE.MINOR_BASE.PATCH_BASE` which expands to:
```
MAJOR_BASE.MINOR_BASE.PATCH_BASE-MAJOR.MINOR.PATH+META_BASE
MAJOR_BASE.MINOR_BASE.PATCH_BASE-MAJOR.MINOR.PATCH+META_BASE
```
For any artifact of this type the meaning of incrementing the components of a version entirely depend on the versioning class itself.
@@ -249,6 +281,54 @@ Example Dependent Artifact Versioning
`1.2.3-4.5.6` > `1.2.2-5.6.7`
</div>
# Backus-Naur Form
```
<valid semver> ::= <version core>
| <version core> "-" <extra>
| <version core> "+" <build>
| <version core> "-" <extra> "+" <build>
<version core> ::= <major> "." <minor> "." <patch>
<major> ::= <numeric identifier>
<minor> ::= <numeric identifier>
<patch> ::= <numeric identifier>
<extra> ::= <dot-separated extra identifiers>
<dot-separated extra identifiers> ::= <extra identifier>
| <extra identifier> "." <dot-separated extra identifiers>
<build> ::= <dot-separated build identifiers>
<dot-separated build identifiers> ::= <build identifier>
| <build identifier> "." <dot-separated build identifiers>
<extra identifier> ::= <alphanumeric identifier>
| <numeric identifier>
<build identifier> ::= <alphanumeric identifier>
| <digits>
<alphanumeric identifier> ::= <non-digit>
| <non-digit> <identifier characters>
| <identifier characters> <non-digit>
| <identifier characters> <non-digit> <identifier characters>
<numeric identifier> ::= "0"
| <positive digit>
| <positive digit> <digits>
<identifier characters> ::= <identifier character>
| <identifier character> <identifier characters>
<identifier character> ::= <digit>
| <non-digit>
<non-digit> ::= <letter>
| "-"
<digits> ::= <digit>
| <digit> <digits>
<digit> ::= "0"
| <positive digit>
<positive digit> ::= "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9"
<letter> ::= "A" | "B" | "C" | "D" | "E" | "F" | "G" | "H" | "I" | "J"
| "K" | "L" | "M" | "N" | "O" | "P" | "Q" | "R" | "S" | "T"
| "U" | "V" | "W" | "X" | "Y" | "Z" | "a" | "b" | "c" | "d"
| "e" | "f" | "g" | "h" | "i" | "j" | "k" | "l" | "m" | "n"
| "o" | "p" | "q" | "r" | "s" | "t" | "u" | "v" | "w" | "x"
| "y" | "z"
```
# Acknowledgments
We would like to give special thanks to the [SemVer project](https://SemVer.org) for providing an early open-source version of the SemVer specification that highly influenced the development of this specification.