Add AlternativeNumber element to v1.1 schema#86
Merged
Conversation
Adds an optional AlternativeNumber string element to the v1.1 draft schema, alongside the existing Number element, and adds tests covering its presence, absence, and duplicate-element validation.
Buried-In-Code
approved these changes
Jul 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
AlternativeNumberstring element to the v1.1 draft schema, placed alongside the existingNumberelement.Why
Marvel and DC (and some other publishers) occasionally publish issues with a legacy or alternate numbering scheme in addition to the primary issue number (e.g. a title relaunches at
#1while also carrying over its "legacy" numbering from a prior volume).AlternativeNumbergives metadata consumers a place to record that secondary number without overloading theNumberelement.Closes #67