The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted by |
Date submitted |
| PDF |
Page 41
In the example |
There are links to
http://api.formats.wrml.org/application/json
But when we point to the link we are getting 404 .
Many of the examples are having a domian name. I loved it should be changed to example.com , else it always confuse a developer.
This happens many places in Book. I am interested to hear your thoughts.
On 41 st page there is a sentence "The application/wrml media type?s IANA registration is pending" , so I feel it would have been a good idea to introduce once it is published. Just a thought.
Thanks
|
harikt |
Jul 17, 2012 |
| PDF |
Page 74
2nd line from the bottom |
in the section on 'Response Representation Composition' the author clearly intended to show a syntax for not including certain fields in a response while showing others. I believe the syntax he used for the example if parsed by a program should result in different behavior than is described in the next page.
Here is what is written:
GET /students/morgan?fields=!(address,schedule!(wednesday, friday)) HTTP/1.1
It appears from the syntax that both address and schedule should be excluded since it is clear that both wednesday and friday were supposed to be excluded from schedule. I am not entirely sure what this should mean for schedule. Perhaps it is a double negation and wednesday and friday should be shown instead of hidden?
Perhaps the following would have been correct?
GET /students/morgan?fields=(!address,schedule!(wednesday, friday)) HTTP/1.1
|
Avery J. Regier |
Apr 19, 2012 |