Rename ivo://ivoa.net/std/sso to ivo://ivoa.net/sso?

[Markus Demleitner]

Hi Pat,

On Mon, Jun 16, 2025 at 12:11:29PM -0700, Patrick Dowler via dsp wrote:
> On Mon, 16 Jun 2025 at 04:23, Markus Demleitner via dsp <dsp at ivoa.net> wrote:
> Still, fixing the standard does seem overly painful and we'd probably
> leave the backwards-compat identifiers there forever because no one
> would want to pull them.

Yes.  That's another point going against adapting the standard.

> On the other hand, what does it mean in the future that a standard
> kind of squats on the root of the ivo://ivoa.net/ namespace with it's
> short name? What other top-level paths are used (other than "std") in
> the ivoa.net authority that we need to consider?

None so far, except for the inevitable authority and registry
records (cf.
<https://dc.g-vo.org/wirr/q/ui/fixed?field0=ivoid&operator0=%3D&operand0=ivoa.net>).
And I have a hard time imagining a scenario where from all the 17576
three-letter combinations there are we would have to have "sso" and
no other as the single path element.  That I'd be relaxed about.

The larger problem might be that people could copy sso rather than
all the standards that do it right.  But that's what we have TCG
reviews for.  I think "Make sure all ivoids mentioned in the text
resolve and make sense" should be an item on a review checklist for
the registry chair.

        -- Markus