Shibboleth Developers

> All I suggested is you use a name that has a more abstract meaning than a
> hostname. I used this example a while back...if OSU wanted to export our
> DSpace service to the world, but it was running on a box named "frobnitz", I
> would use a providerId like https://dspace.osu.edu/shibboleth or perhaps
> urn:mace:osu.edu:shibboleth:dspace
>
> Of course, in reality, any real DSpace service would already have a reserved
> alias in the DNS and wouldn't be accessed using a physical host name anyway.
> So it goes with just about any commercial SP.
>
> If I'm proposing anything, it's probably
> https://<logicalservicename>.<subdomain>/shibboleth

so there's  the balance point.... using logicalservicename makes 
reconfig easier if you move the service to another  host; it makes 
life a bit harder for the person managing the shibboleth.xml if your 
host is serving several applications with the same/similar session 
and attribute requirements.

Its also worth noting that this approach could create names that are 
readable and have some meaning, altho that's not a requirement, and 
that's a very slippery slope