The hyperlink equivalent would be "you can find this book at this library in this town, as of the time this was written".
I imagine that in real life lawyers don't need to worry about that sort of instruction because those books are printed and widely distributed across the country, while on the web documents tend to exist in only a single location, maintained by a single person or organization. USENET might be the closest on the internet we have gotten to that sort of distribution model.
The difference is that a citation is a reference to an immutable object. No matter what happens to Roe v. Wade, say it is overruled, the document at 410 U.S. 113 won't change. A URL on the other hand is a reference to a location. Like with the memory address pointed-to by a C pointer, what is at that location can change.
One can imagine a system of hyperlinks that behaved differently. In this system, a URL would uniquely identify an immutable document. A new version of a document would get a new URL, and servers would be required by the protocol to preserve all previous versions of the document. This is essentially the premise of Git: every blob is stored forever and different revisions are stored as deltas such that older versions always remain accessible.
What we need is a technical mechanism for embedding referenced source documents into a document, in a way that is as easy as hyperlinking to add the references and follow them. Probably also a new fair-use provision in copyright law as well.
Agreed on having a way to embed documents. Especially in a way that supported some kind of signing. If I could have a reputable third party (web.archive.org or anybody else) sign an embedded snippet of a page and say "Yes, this was actually posted on X website at Y time" that would be fantastic.
It's a fantastic system (and a wonderful demonstration of the advantages of immutable graph data structures). You can read cases from a century ago and still find every cited reference. Hyperlinking pales in comparison.