Is your feature request related to a problem? Please describe.
When an SSVC Decision Point is being customized to suite a community's needs how will they customize it. Does namespace have to be all lowercase US-ASCII? Should it NOT contain other unicode languages as presumed in the examples? Should the namespace have a minimum of 3 or 4 characters?

Describe the solution you'd like

1. Call a completely adapted SSVC with ONLY language translations as ssvc-jp for Japanese
2. Designate a namespace customized SSVC tree for Acme Inc. as ssvc/acme
3. Provide a namespace for a DNS domain based hierarchy for an organization with example.com as ssvc/example.com

Describe alternatives you've considered
One could use ssvc.acme instead of ssvc/acme - the namespace ssvc will remain authoritative and managed by the SEI.

Additional context
This came up post some discussions from Oasis Group members on cusotmizing and adopting SSVC.