You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During writing text for oasis-tcs/csaf#1152 (especially 6.2.34), I realized that the choice to rename the "private namespaces" into "unregistered namespaces" might have been a move with interesting consequences.
For now, this is just for documentation purposes. So, I suggest, we keep this open and discuss and resolve it in our next meeting.
Potentially related to #802 - but my current assessment would be non-blocking.
During writing text for oasis-tcs/csaf#1152 (especially 6.2.34), I realized that the choice to rename the "private namespaces" into "unregistered namespaces" might have been a move with interesting consequences.
As written, this issue is not currently actionable: I don't know what the "interesting consequences" are, and I don't know what to do about them.
Activity
ahouseholder commentedon Sep 9, 2025
As written, this issue is not currently actionable: I don't know what the "interesting consequences" are, and I don't know what to do about them.
ahouseholder commentedon Sep 10, 2025
The current question is whether there is anything further to do beyond
ahouseholder commentedon Sep 15, 2025
Removing this from the 2025-09 milestone as there's no obvious action to be taken at present.
sei-vsarvepalli commentedon Sep 8, 2026
resolved confirmed with Thomas.