The standard definition of the SchemeLanguage.
Quoting from http://www.schemers.org/ :
Since August 2007 the new standard is R6RS. It adds quite useful stuff: a module system, unicode, an exception system, and so on, see http://www.r6rs.org/.
One of the reasons for the small size of standard Scheme is the UniformConsentRule?, according to which all the authors of the report have to agree to a proposal in order for it to be accepted. I.e. a feature will only be added to the language if all authors agree that it is the RightThing. This explains why R5RS doesn't define e.g. a ModuleSystem even though the authors agree that a module system would be a GoodThing. (However see http://library.readscheme.org/page5.html for an online bibliography of Scheme-related papers about modules and ComponentOrientedProgramming.)
The archives of the RnRS authors' mailing list are available online at http://www.swiss.ai.mit.edu/projects/scheme/rrrs-archive.html. They provide valuable background information and insight into the decisions for inclusion and omission of some of the more controversial features of Scheme.
Not only is it the definition of Scheme, but it is a model of how all standards should look:
The title is surely a reference to the AlgolSixty report ("Revised Report on the Algorithmic Language Algol 60") - see http://www.masswerk.at/algol60/report.htm . Algol 60 was lexically scoped, like Scheme, but unlike the default behaviour of earlier versions of LispLanguage. (CommonLisp's (mostly-)LexicalScope was taken from Scheme.)