-
Notifications
You must be signed in to change notification settings - Fork 42
Update namespace documentation #938
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
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
…erved namespaces
Contributor
Author
sei-vsarvepalli
approved these changes
Sep 9, 2025
Contributor
sei-vsarvepalli
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also has other probability stuff updates in it - all okay.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
content/representation
Formatting, page layout, syntax, etc.
content/semantic
Changes to the semantic content of the SSVC documentation
enhancement
New feature or request
integration
Related to integration of SSVC into another framework or system
python
Pull requests that update Python code
tech/backend
Back-end tools, code, infrastructure
tech/data
Data implementation (content of /data, data object instances, etc.)
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.




This PR:
invalid#907invalidandx_invalidare blocked from useexampleandx_exampleare reserved for examples and documentationtestandx_testare reserved for testsnistnamespacenistnamespace.jsonfiles, hence what appears to be an unrelated change to data/json/decision_points/basic/probability_scale_in_5_weighted_levels_ascending_1_0_0.jsonnamespaces.mddocumentation diagrams for clarityCopilot Summary
This pull request refactors the probability scale decision point definitions and updates the documentation for namespace structure and extension usage. The main changes are the migration of the NIST-based probability scale to its own namespace, a redesign of the "basic" weighted probability scale, and comprehensive improvements to the documentation on namespace conventions and extensions.
Decision Point Refactoring:
P_5X) from thebasicnamespace to a newnist#800-30namespace, restoring its original value definitions and associated registry entries. [1] [2]basicprobability scale (P_5W) to use ascending probability ranges with higher resolution as probability increases, replacing the previous NIST-based value definitions.basic.P_5Xentry and add the newnist#800-30.P_5Xentry. [1] [2]src/ssvc/decision_points/basic/probability/__init__.pyto remove the NIST probability scale from the basic namespace and ensure only the correct decision points are registered.Documentation Improvements (Namespace and Extension Structure):
docs/reference/code/namespaces.mdto clarify reserved namespace strings, the use and requirements of fragments in registered and unregistered namespaces, and the semantic and structural requirements for namespace extensions. This includes new diagrams, notes, and examples for better understanding. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]These changes improve the clarity and maintainability of the decision point definitions and provide more robust guidance for namespace usage and extension in SSVC.