I am old enough to remember the first time the session pattern was used in a web framework, I remember cringing then just as I do now when I see it used.
I think when most normal people say REST, they simply mean some sort of vague messages-over-HTTP metaformat that doesn't necessarily enforce odd restrictions about POST vs. PUT, is somewhat self-documenting and easy to work with due to the limited scope of the medium, etc.
And I think of Fielding's dissertation, together with a few RFCs like 2616, as the founding documents of REST.
so you will have something like
<api>
<projects>http://../projects/</projects>
</users>http://../users</users>
</api>
or even this: <service>
<name>projects</name>
<href>http://.../projects/</href>
</service>
...
and then your project list should not just return you projects ids to construct a url with, instead it should provide you full urls to access the relevant resources.The rule of thumb is: with a PROPER REST API you should never do any "url generation", you should get ALL your urls (except for the SINGLE entry one) form the API.
check out this link for some more info: http://www.theamazingrando.com/blog/?p=107
For example, "your public API should not depend on the structure of your URIs. Instead there would typically be a single XML file that points to the components of your service." It's difficult to understand this kind of point without an example in hand - preferably an example taken from an actual website.
The whole list presupposes a familiarity with REST theory and jargon. And the assertion that 'sessions are irrelevant' instantly raises my suspicions about the author's relationship with reality.