rev="shorturl" (Score 1)

Disclaimer: I'm an author of a competing RFC so my opinions might be biased - although i hope my reasons are as rational as possible ;)

An alternate approach to this problem:

http://wiki.snaplog.com/short_url

Summary

Short URL auto-discovery is a simple way to link a long URL with a short URL. The following code should be placed in the section of the HTML page.

<link rel="shorturl" href="http://short.com/1234" />

or add the following to the HTTP Headers of the page

Link: ; rel=shorturl

In most real-world situations, the short URL then redirects with an HTTP code 302 to the long URL, but that behavior is not covered by this RFC.

That's it! :)

why not use rel="alternate .... "

Sam Johnson pointed out alternate doesn't make sense since it implies a link to same content but different format like PDF for example

why not rel="shortcut"

Shortcut in the web context not well understood nomenclature referring to short URLs (OK to define shortcut icons with rel="shortcut icon" though and if we wanted to follow that model we'd use rel="shortcut url", but that seems excessive)

Potential legacy code breakage as suggested by http://twitter.com/soypunk/status/1509403319

Also somehow shortcut seems like the wrong wording... implies a link that will bypass something ... a splash screen, etc...

why not rel="shorter" or rel="short"

Implies shorter version of the content

why not rev="canonical"

rev is absent from HTML5 and confusing with rel="canonical", breaks Google's proposed definition of canonical for search purposes.

why not rel="shorturi"

Part of making a new RFC to describe a simple concept is simple naming. People know that a URL is what's in the location bar in their browser. Besides we'd never see a URI that's not an URL in this context.

why not rel="short_url"

The _ is ugly.