XSLT 2.0 and XPath 2.0 Programmer's Reference, 4th Edition

ISBN: 978-0-470-19274-0

Hardcover

1368 pages

May 2008

List Price:	US $75.00
Government Price:	US $48.00
Enter Quantity: Buy

XSLT 2.0 and XPath 2.0 Programmer's Reference, 4th Edition (0470192747) cover image

This is a Print-on-Demand title. It will be printed specifically to fill your order. Please allow an additional 15-20 days delivery time. The book is not returnable.

< >

Do you think you've discovered an error in this book? Please check the list of errata below to see if we've already addressed the error. If not, please submit the error via our Errata Form. We will attempt to verify your error; if you're right, we will post a correction below.

Chapter	Page	Details	Date
	9	Error in Text In the last paragraph on the page, "There's a choice of Xalan-J product" Should be "There's a choice of XSLT 1.0 products."	12/14/08
	10	Error in Text Bullet 1, last sentence: "will only run with a basic XSLT processor" should be "will only run with a schema-aware XSLT processor"	12/14/08
	15	Typo in Text In line 8 on the page, "ability invoke" Should be "ability to invoke"	12/14/08
	39	Typo "The fact that XPath was designed to be embedded in other language has some specific consequences:" should be: "The fact that XPath was designed to be embedded in other languages has some specific consequences:" notice the added "s" to "launguages"	5/18/11
2	47	Error in Figure 2-4 Figure 2-4 Text: "send out (goods)" disagrees between XML example and diagram: In the box in the diagram whose content is "send out goods to another country", change the text to "send out (goods) to another country."	09/08/08
2	57	Error in Text first line: PossibleParent/Child vs PotentialParent/Child terminology disagrees between text and diagram: "PotentialParent" and "PotentialChild" should be: "PossibleParent" and "PossibleChild" respectively	09/08/08
2	67	Error in Text middle of page: represented in as a CDATA Should be: represented as a CDATA	09/08/08
6	334	Error in Example Stylesheet example (template match="staff") Example repeats "Location" heading at each level: In line 5, change "Location " to "Location: " AND In line 11, change "Location " to "Department: " AND Delete line 17	09/08/08
6	437	Error in Code code at the bottom of the page: <xsl:perform-sort select? = {expression} <!-- Content: (xsl:sort+, sequence-constructor) -> </xsl:perform-sort> should be: <xsl:perform-sort select? = expression> <!-- Content: (xsl:sort+, sequence-constructor) --> </xsl:perform-sort> That is: - no curly braces around "expression" (it's not an attribute value template) - closing angle bracket after "expression" - two hyphens, not a dash, at the end of the comment	10/02/08
6	467	Error in Text extension-element-prefixes No mention of the options #default or #all. (In the text, there is mention of #default on page 474, but no mention of #all). The value #default is also allowed for extension-element-prefixes In the entry for attribute exclude-result-prefixes, column "value" : ADD ", or #default, indicating the default namespace, or #all, indicating all namespaces" In the entry for attribute extension-element-prefixes, column "value" : ADD "or #default, indicating the default namespace"	09/08/08
13	783	Error in Text 2nd paragraph last sentence: If n is omitted, it is assumed to be equal to m Should be: If n is omitted, ?*? is assumed.	10/02/08
13	805	Error in Example XML XML is not well-formed: <name="Queen Elizabeth II"/> should be: <name>Queen Elizabeth II</name> AND <name="Prince Charles"/> should be: <name>Prince Charles</name>	09/08/08
13	882	Error in Text In the Signature table, Result row, Type column: "xs:string" should be: "item()*"	09/08/08
13	900	Error in Statement Second bullet list, last bullet: Statement is incorrect. As stated later on the page, types imported using xsl:import-schema are not part of the static context of the use-when expression. Delete the bulleted paragraph "A user-defined simple type or complex type defined in a schema that has been imported using an "	09/08/08
15	948	Errata in code Code currently reads: <xsl:sequence select="translate($in, '<&>apos;"', '&doe-lt;&doe-amp;&doe-gt;&doe-apos;&doe-quot;')"/> Should read: <xsl:sequence select="translate($in, '<&>''"', '&doe-lt;&doe-amp;&doe-gt;&doe-apos;&doe-quot;')"/>	21-Nov-16
	996-999	Error in download files For this worked example, there are discrepancies between the printed input, output, and stylesheet and the downloaded code; furthermore, the stylesheet does not produce the output in the format shown. Corrected versions of all three files are available. The logic of these corrected files corresponds to the description of the logic that appears in the narrative accompanying the example.	2/28/11
19	1063	Error in Text 2nd paragraph: GedcomParser is not in download file as stated	09/08/08
	1127	Error in Code left-hand column <xsl:message terminate="$z"/> should read: <xsl:message terminate="{$z}"/>	09/07/08