Errata

RESTful Web APIs

Errata for RESTful Web APIs

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
Introduction
"Administrative Notes" section

The link to "the RESTful Web APIs GitHub repository" is incorrect. The correct link is:

https://github.com/RESTful-Web-APIs

The link given is:

https://github.com/organizations/RESTful-Web-APIs

 Leonard Richardson  Sep 23, 2013  May 22, 2015
ePub
TOC, Introduction, Understanding Standards, Para 5

Text in this part includes the following:

"... and if you go against them you’re causing a lot of trouble for yoursef. "


"yoursef" should be "yourself"

 pob  Nov 12, 2014  May 22, 2015
ePub
Chapter 1, Resource State, Para 1

In the first para, you say (more or less) that there are two states, and you omit the individual message state.

In addition, there is the *About* state, which you fail to identify, or omit.

Note from the Author or Editor:
"The server also manages a resource for each individual message." should be "The server also manages a resource for each individual message, and one for the 'About this site' page."

 pob  Nov 12, 2014  May 22, 2015
Other Digital Version
9
6th paragraph (?)

"This time, the browser responds with 200 (“OK”) and an HTML document:"

I think that it should read

"This time, the server responds with 200 (“OK”) and an HTML document:"

 Anonymous  Feb 12, 2015  May 22, 2015
Printed
Page 32
1st paragraph

The end of the first paragraph says...

'But they're clearly different representations of the same resource: a microblog entry that says, "Squid."'

The problem is that the first microblog entry being referred to on page 31 does not say "Squid", instead it says, "tasting." The microblog entry on page 32 does say "Squied", however. The microblog representations are not consistent with each other and with the description.

Note from the Author or Editor:
On page 31 "value": "tasting" should be "value": "Squid!"

On page 32, "Squid." should be "Squid!", both in the sample JSON and in the text of the book.

 Dean Mathias  Feb 16, 2014  May 22, 2015
Printed
Page 52
"Guiding the Request" section

The HTML form presented uses a method="get" which sends a HTTP GET request on submission.

The following description in the text references the entity-body which isn't appropriate for a GET request. Should the form have used method="post" to match the subsequent discussion?

Thanks!

Note from the Author or Editor:
In the HTML form on page 52, method="get" should be method="post".

value="Lookup" should be value="Add".

 Anonymous  Nov 15, 2013  May 22, 2015
Printed
Page 61
Image of Maze

Text describes an entry from the south into room M.
Image shows a view facing a wall, but shows caption "You are facing: east" which should be an exit, not a wall.

Note from the Author or Editor:
In Figure 5-2, "east" should be "north". Changing this figure may be annoying; it's okay to paste over some new text that says "north".

 Kirk Israel  Feb 25, 2014  May 22, 2015
Printed
Page 88
Second to last line.

The word "out" is repeated.

The book has:

"The human chooses an API and figures out out which state transitions..."

I believe it should be:

"The human chooses an API and figures out which state transitions..."

Note from the Author or Editor:
confirmed. the "out out" should be reduced to "out"

 Daniel Fava  Jul 30, 2020 
Printed
Page 116
3rd paragraph

The first sentence of the 3rd paragraph on page 116 begins...

"HTML Microdata4.] introduces..."

4 is a footnote and the two characters following the footnote marker should not be there. Instead, they should be part of the actual footnote.

Note from the Author or Editor:
The period and the right angle bracket are part of the footnote, not part of the text.

 Dean Mathias  Feb 16, 2014  May 22, 2015
PDF
Page 166
Figure 9-6

In the diagram the link relation for "edit" connecting "Switch" to itself is labelled as (unsafe, non-idempotent). In the accompanying text it is stated that the advantage of the "edit" relation over the "flip" relation that it replaces is that it makes the state transition idempotent.

Note from the Author or Editor:
In Figure 9-6, "edit (unsafe, non-idempotent)" should be "edit (unsafe, idempotent)"

 Michael Constans  Oct 14, 2013  May 22, 2015
ePub
Page 371
Chapter 12, Section 'When to Use the Descriptive Strategy', 3rd paragraph

The markup for the book's formatting has been escaped or otherwise inadvertently exposed:

“phrase:[<phrase role="keep-together">hypermedia</phrase>]”

Note from the Author or Editor:
This is ORA-internal markup, possibly for adding a link to a glossary. I'm not familiar with it. It shouldn't show up in the print edition.

 Jordan Ryan Reuter  Sep 13, 2014  May 22, 2015
PDF, ePub, Mobi
Page 9912
text

"was was rarely used" should be "was rarely used"

"langauges" should be "languages"

"which is is her current" should be "which is her current"

"What if there there were" should be "What if there were"

Note from the Author or Editor:
change "was was rarely used" to "was rarely used"

change "langauges" to "languages"

change "which is is her current" to "which is her current"

change "What if there there were" to "What if there were"

 Anonymous  Sep 23, 2019