This doesn't make any sense, though. Once you recognize that the two may represent different addresses, you're arbitrarily choosing the first one in your system as the right one, when the second one is just as right. Just give up at that point and lowercase ’em.
which one should be considered the correct one?
users/me feels like a bad idea because REST prefers to have one url per resource. You will then have: users/me users/123myId Which point to the same resource.
Here is a method using the fontTools Python library (which you can install with something like pip install fonttools ):
canonical version/location: Probably https://stackoverflow.com/questions/4458696/finding-out-what-characters-a-given-font-supports
superseded by: https://hyp.is/Z1f9kFuaEe2eHAdj5fbY2Q/stackoverflow.com/questions/4458696/finding-out-what-characters-a-given-font-supports
I'd say the author's updated version is canonical: https://hyp.is/2lzvXK4sEeu3s1Piywmzww/www.hteumeuleu.com/2016/using-flexbox-in-an-email/
This post was originally published on my blog in french and on the Litmus forums in June 2015. It was updated with information about support in the new Outlook Web App in January 2016.
Was trying to figure out where the canonical repo even is. Hard to figure out. Could be made clearer (like a prominent notice on one saying this is an unofficial clone with a link to the canonical source).
Ended up here via link from https://unix.stackexchange.com/questions/86879/suppress-rsync-warning-some-files-vanished-before-they-could-be-transferred to https://git.samba.org/?p=rsync.git;a=blob_plain;f=support/rsync-no-vanished;hb=HEAD
But then found https://github.com/WayneD/rsync, which I now believe to be canonical based on:
This is a copy of the "AMD" document in the repo, kept here to maintain historical links. If this document differs from the one in the repo, the repo version is the correct one.
Why not just make this document empty (besides a link) and link/redirect to the canonical version?
That way it is impossible for them to disagree.
RDFa is intended to solve the problem of marking up machine-readable data in HTML documents. RDFa provides a set of HTML attributes to augment visual data with machine-readable hints. Using RDFa, authors may turn their existing human-visible text and links into machine-readable data without repeating content.
Every AMP document needs to have a link referencing the "canonical" version of that document. We'll learn more about what canonical pages are and different approaches to canonical linking in the Making your page discoverable step of this tutorial.
Canonical linking in regular HTML pages is a common technique for declaring which page should be considered the preferred page when multiple pages include the same content.