github-starred/semver
2
0
Fork 0
mirror of https://github.com/semver/semver.git synced 2026-11-13 17:56:10 -06:00
Code Issues 2.1k Packages Projects Releases 4 Wiki Activity

<build identifier>'s BNF should be simplified #465

New Issue
Open
opened 2026-02-17 12:07:25 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-17 12:07:25 -06:00
Owner
Copy Link
Copy Source

Originally created by @ogregoire on GitHub (Mar 24, 2021).

Unless I'm missing something, one can write a build identifier as any sequence of digits, letters and dashes.

Therefore I think it'll be easier to understand the format of build identifier if it is simplified as follows:

<build identifier> ::= <identifier characters>

If not, can you provide an example of build identifier that doesn't match <identifier characters>?

Originally created by @ogregoire on GitHub (Mar 24, 2021). Unless I'm missing something, one can write a build identifier as any sequence of digits, letters and dashes. Therefore I think it'll be easier to understand the format of `build identifier` if it is simplified as follows: ```` <build identifier> ::= <identifier characters> ```` If not, can you provide an example of build identifier that doesn't match `<identifier characters>`?
GiteaMirror added the question label 2026-02-17 12:07:25 -06:00
GiteaMirror commented 2026-02-17 12:07:26 -06:00
Author
Owner
Copy Link
Copy Source

@kaldrako1 commented on GitHub (Mar 28, 2021):

Bc

@kaldrako1 commented on GitHub (Mar 28, 2021): Bc
GiteaMirror commented 2026-02-17 12:07:27 -06:00
Author
Owner
Copy Link
Copy Source

@zafarkhaja commented on GitHub (Jan 13, 2024):

Two reasons that I can think of why it's the way it is, are

  1. desire to reuse already defined symbols
  2. desire to differentiate between <alphanumeric identifier> and <digits>

The purpose of the second one is not clear, as opposed to the purpose of differentiating between <alphanumeric identifier> and <numeric identifier> in <pre-release>, which has to do with determining precedence (SemVer 11.iv.c).

@zafarkhaja commented on GitHub (Jan 13, 2024): Two reasons that I can think of why it's the way it is, are 1) desire to reuse already defined symbols 2) desire to differentiate between `<alphanumeric identifier>` and `<digits>` The purpose of the second one is not clear, as opposed to the purpose of differentiating between `<alphanumeric identifier>` and `<numeric identifier>` in `<pre-release>`, which has to do with determining precedence (SemVer 11.iv.c).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
consensus seeking
duplicate
extend
layout
pull-request
Mirrored from GitHub Pull Request
 question
RFC
spelling/grammar
staled
update
waiting for PR
won't fix
No labels question
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#465