Errata

JSON at Work

Errata for JSON at Work

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
PDF
Page 115
Second line from top of page

Appearing in Chapter 4, "If you'll recall from Chapter 6 (JSON Search), jq is an amazing command"

- except that there is no previous mention of jq before page 115, so the reader cannot be expected to recall something that has not been previously introduced.

Was chapter 6 (JSON Search) meant to appear earlier in the book?

 Mark Harrison  Apr 07, 2017  Jun 16, 2017
PDF
Page 109
Top of page

The screenshot shows the command that should be entered - but this should also be shown in the text of the page, before the screenshot, for clarity and to make it available for copy/paste or screen readers (which generally cannot read text from bitmap graphics).



 mgh128  Apr 05, 2017  Jun 16, 2017
PDF
Page 88
First line after json:api header

standardizingß --> standardizing

(spurious German ess zset character should be removed )

 mgh128  Apr 05, 2017  Jun 16, 2017
PDF
Page 86
Fifth line below Collection+JSON heading

Change:

+application/vnd.collection+json

to

application/vnd.collection+json

(the MIME type does not have a leading + symbol before 'application' )

 mgh128  Apr 05, 2017  Jun 16, 2017
PDF
Page 83
middle of page

http://schema.org/Person[http://schema.org/
Person

has no closing square bracket. Probably can just remove [http://schema.org/Person and ensure that the original http://schema.org/Person is hyperlinked.

Note also that schema.org now use https:// throughout, rather than http:// , although they provide an auto-redirect to the https:// equivalent.

 mgh128  Apr 05, 2017  Jun 16, 2017
PDF
Page 82
Second line under JSON-LD heading

ttps://www.w3.org/TR/json-ld-api

should read

https://www.w3.org/TR/json-ld-api

 mgh128  Apr 05, 2017  Jun 16, 2017
PDF
Page 60
Final paragraph

The following sentence:

The following document is valid because the length of the lastName exceeds 20 characters.

should read:

The following document is invalid because the length of the lastName exceeds 20 characters.


(invalid - not valid) - looks like a copy/paste error from previous sentence with the <= typo reported previously.

 mgh128  Apr 05, 2017  Jun 16, 2017
PDF
Page 60
2nd paragraph

The following sentence:

The following document is valid because the length of the lastName is ⇐ 20

should read:

The following document is valid because the length of the lastName is <= 20

(less than or equal to 20 - looks like the word processing software has unhelpfully auto-miscorrected the <= into a left block arrow)

 mgh128  Apr 05, 2017  Jun 16, 2017