Skip to content

Add 'invalid' to the registered namespaces#915

Closed
ahouseholder wants to merge 2 commits intomainfrom
907-reserve-registered-namespace-invalid
Closed

Add 'invalid' to the registered namespaces#915
ahouseholder wants to merge 2 commits intomainfrom
907-reserve-registered-namespace-invalid

Conversation

@ahouseholder
Copy link
Contributor

@ahouseholder ahouseholder commented Aug 26, 2025

The original issue also mentions x_invalid, however, if we add x_invalid to the registered namespaces, it will fail to match the namespace pattern because the pattern assumes anything that starts with x_ will have a fragment. So I'm leaving that out of this PR in the interest of keeping the PR simple.

@ahouseholder ahouseholder linked an issue Aug 26, 2025 that may be closed by this pull request
@ahouseholder ahouseholder self-assigned this Aug 26, 2025
@ahouseholder ahouseholder added tech/backend Back-end tools, code, infrastructure tech/data Data implementation (content of /data, data object instances, etc.) integration Related to integration of SSVC into another framework or system labels Aug 26, 2025
@ahouseholder ahouseholder added this to the 2025-09 milestone Aug 26, 2025
… to validator to skip pattern matching on explicitly registered namespaces.
@ahouseholder ahouseholder changed the title Add 'invalid' and x_invalid to the registered namespaces Add 'invalid' to the registered namespaces Aug 26, 2025
Copy link
Contributor

@tschmidtb51 tschmidtb51 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder whether that makes sense from a usage point and the intended purpose: things should fail with the registered namespace. I know that having a registered namespace that is not registered in the code sounds awkward - but that is actually the point.
So, I think this should just go into the documentation as reserve namespace for special use (similar to example, testand x_example - see also #907 (comment))

Copy link
Contributor

@tschmidtb51 tschmidtb51 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see: #907 (comment)

Edit: After giving it another though: I changed assessment from comment (last night) to request changes as I think invalid can't be in the code if it should work as intended.

@ahouseholder
Copy link
Contributor Author

Withdrawing this PR until we get to resolution on #907

@ahouseholder ahouseholder deleted the 907-reserve-registered-namespace-invalid branch September 9, 2025 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integration Related to integration of SSVC into another framework or system tech/backend Back-end tools, code, infrastructure tech/data Data implementation (content of /data, data object instances, etc.)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reserve registered namespace invalid

2 participants