Developing Feeds with RSS and Atom by Ben Hammersley This errata page lists errors outstanding in the most recent printing. If you have technical questions or error reports, you can send them to booktech@oreilly.com. Please specify the printing date of your copy. This page was updated March 13, 2006. Here's a key to the markup: [page-number]: serious technical mistake {page-number}: minor technical mistake : important language/formatting problem (page-number): language change or minor formatting problem ?page-number?: reader question or request for clarification Confirmed errors: (9) 2nd Paragraph; "And, of course, some people didn't use the additional features of 0.91 and so were de facto RSS 0.91 users as well." it should read: "And, of course, some people didn't use the additional features of 0.92 and so were de facto RSS 0.91 users as well." (9) 7th paragraph; "After a great deal of acrimony, UserLand released a specification they it RSS 2.0 and declared RSS frozen." should be: "After a great deal of acrimony, UserLand released a specification they called RSS 2.0 and declared RSS frozen." [12] 3rd paragraph; "This might sound a little radical to the average company vice president, but remember: there is nothing in the RSS feed that didn't, in some way,in the actual source information in the first place." insert the word "appear" before "in the actual source..." (25) 4th paragraph; "The answer is this: although many people are still learning to produce 0.91, 0.91, et al, we will not." should be: "The answer is this: although many people are still learning to produce 0.91, 0.92, et al, we will not." Note the second 0.91 has been changed to 0.92. Also notice that in the book, the line breaks after the second "0." (28) 4th paragraph; The example for the 'lastBuidDate' subelement reads: Sun, 12 Sep 2004 19:01:55 GMT but obviously it should use lastBuildDate instead of pubDate, i.e.: Sun, 12 Sep 2004 19:01:55 GMT [81] In the Element section, the final three paras should read as below:; However, this element can also take subelements of its own from the Dublin Core modules, mod_dublincore and mod_DCTerms. We'll see these modules soon, but the first example in the next section will give you an idea. Do you see how the namespaces system works? The first example shows a feed using only the mod_annotation system. We've added one additional namespace and used the element correctly. In the second example, we want to use another module to describe something in terms that the currently available elements can't. So we decide upon mod_dublincore, add in the namespace declaration, and go ahead. Also notice that in the first example, annotate is a one-line element, with a closing />, whereas in the second example, annotate contains the mod_dublincore elements before closing. This means that the mod_dublincore elements ref .... [108] The last sentence before the Example section should read as below:; The taxo:topic element itself can contain taxo:topics, as shown in the following section. {60} midpage, code below "The contents of the element then describe..."; The code is broken into two lines, and the statement is terminated at the end of the first line, leaving the real end of the statement hanging: xnlns:rdf="http://purl.org... " > it should be: