Element tagging is out of scope in this thread, but all else being equal, I’d be interested in <meta itemprop> as it both allows non-URI content (at:// is valid) and it’s also allowed in flow content. Meaning using it would resolve our standard site issue:
<head>
<meta itemprop="renders-at-uri" content=”at://did:plc:whoever/site.standard.publication/abc123”>
<head>
And leave the door open for discussing element tagging in a separate thread:
<blockquote>
<meta itemprop="renders-at-uri" content=”at://did:plc:vc7f4oafdgxsihk4cry2xpze/app.bsky.feed.post/3l6n7c6cyx42i”>
people will think anything on bluesky. "he's got thousands of followers! he must have good posts." no they aren't. that isn't true.
</blockquote>
I really don’t want to restart the closed conversation about element tagging, but I wanted to highlight that—unlike <link rel="canonical"> tags (see here)—<meta itemprop> specifically is allowed in flow content and can hold any text we want (avoiding the URI issue).
(I picked renders-at-uri as I think it’s semantically descriptive of what the link is doing—rather than eg. at:uri which, like the at-uri itself, is only descriptive of what it is—but I have no attachment to it specifically)