David, you do not see a need to define a new URI scheme for
anything, do
you?. If I you do, please enumerate the requirements for a protocol
that
would save it from the http black hole.
SSH is not a new protocol, and the "adoption rate" does not depend
on the
URI; it is an agreement between the owner and the user that counts.
This
agreement already provides all technical information the user needs,
and
explaining it over HTTP would not be useful.
And how would you persuade the Web browser to send an HTTP SSH URI
to an
external handler instead of navigating to it? (Think Internet
Explorer, for
clarity.)