In many cultures, family names are high-entropy and given names are lower entropy (two random people are more likely to share a given name rather than a family name). Under this assumption, the family-name citation trend makes more sense as there is a lower chance of collisions.<p>For Korean and Chinese names in particular, it's sort of the opposite: family names are lower entropy (e.g. Lee, Wang, Kim) than given names, which drastically increases the chance of family-name collision. I’m a PhD student of Chinese descent, and I share a family name with lots of academic peers in my specific subfield of research, and have even co-authored with unrelated individuals who share a family name with me. Family-name citations are really ambiguous and confusing to me, so I prefer omitting them altogether and using numeric links.
I don't buy the argument - when I pick the wrong "Wilson" in "Wilson (2002)" then by the time I read the bibliography, I can see that I make a mistake.
Has that ever happened? Not that I know, but I saw something else, without stepping in the trap, namely that the _same_ Wilson wrote more than one paper in 2002, and they cited the _other_ paper, not the one I first thought. Again, the reason I found out is that I read the references, otherwise I could not relate this incident.<p>It's important to scan the references to check oneself if one agrees with the selection of references, or if the author(s) omitted important work that one knows and the authors did not know or did not want to cite due to a hidden agenda (selection bias), in which case one may email them to share additional references so that they cannot say "we never knew".<p>I could accept numeric citekeys if and only if the HTML rendering shows me the
full entry when hovering over it with the mouse cursor (as a "tool tip"); there is absolutely no need in the 21st century to manually scroll/jump to the end without coming back when you can shop the reference inline. Hypertext is there for you to make use of it (Berners-Lee [1], 2000)!<p>References<p>[1] <a href="https://search.library.wisc.edu/catalog/999902745302121/cite" rel="nofollow">https://search.library.wisc.edu/catalog/999902745302121/cite</a> ;-)
One of the nice things about Tufte-Latex is that refs get put into margin notes right at the point of reference.<p>Edit: example <a href="https://mirror.apps.cam.ac.uk/pub/tex-archive/macros/latex/contrib/tufte-latex/sample-handout.pdf" rel="nofollow">https://mirror.apps.cam.ac.uk/pub/tex-archive/macros/latex/c...</a>
If your article is digital, just make it so that the full citation is revealed on hover (as a "tooltip"), so users don't have to jump back and forth.<p>edit: Tooltips supplement the traditional reference section. They are not to be printed.
Two things that I don't see mentioned is that:<p>(a) [Name 2005] is much easier to mentally track if it appears repeatedly in longer text than [5] (at least for me). [5] is just [5]. [Name 2005] is "that paper by Name from twenty years ago".<p>(b) By using [Name 2005], I might not know which exact paper this is, but I get how recent it is w.r.t. what I am reading. In many cases, this is useful context. Saying "[5] proves X" could mean that this is a new result, or a well known fact. Saying "[Name 1967] proves X" clearly indicates that this is something that has been known for some time.
"Fundamentally, the problem with this is that it's actively encouraging guesses to override the communication of ethically required citation information."<p>This is silly. 99% of the time, if you cite Autor et al. (2013), it'll be <i>that</i> Autor et al. (2013). The other 1%, it'll be another David Autor paper. The case when you guess something wrong, and really it's a different author, who then gets hurt, probably happens once a year. Meanwhile, Autor et al. (2013) immediately lets me understand what you're referencing, which [57] does not.
What about being able to use direct voice when reporting related work? e.g. "Secondname invented a yabayaba". I have seen "[1] invented a yabayaba", but doesn't it look kind of odd?
Coming from a field where [n] routinely means {1,2,...,n}, I don't feel like the [1], [2], [3] system can win me over. But I'm ready to see some advantages it has.