Update purl-type-definition.schema-1.1.json to add registered values for namespace and qualifiers - #945
Open
mjherzog wants to merge 5 commits into
Open
Conversation
Updated schema to add enumerated values for namespace and qualifiers Also upgraded to JSON Schema version 2020-12 Signed-off-by: Michael Herzog <mjherzog@aboutcode.org>
This was
linked to
issues
Aug 10, 2026
Updated JSON Schema to version 2020-12 Signed-off-by: Michael Herzog <mjherzog@aboutcode.org>
Correct URL for JSON Schema version 2020-12 Signed-off-by: Michael Herzog <mjherzog@aboutcode.org>
Corrected braces for qualifiers key registered values Signed-off-by: Michael Herzog <mjherzog@aboutcode.org>
mjherzog
changed the title
12 tasks
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
1 participant
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.
Updated schema to add "registered values" for namespace and qualifiers keys.
The "registered values" are implemented as an optional enumerated list within a PURL type definition for these 2 PURL components.
The use of "registered" here is intended to parallel the naming convention of "registered" PURL types (instead of the vague "common" or "known" terminology), but we might want to use the terminology "enumerated values" to convey that the values are contained/enumerated within the a PURL type definition and not "registered" elsewhere.
Also upgraded to JSON Schema version 2020-12