eXist

Errata for eXist

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
ePub
Page ch 1
United Kingdom

Para headed 'More than you relise' s/prodcedural/procedural/ Para headed 'Document Oriented' s/Unlinke/Unlike/

Note from the Author or Editor:
Procedural needs to be fixed. Unlike has been fixed.

Dave Pawson  Feb 05, 2014 
ePub
Page ch 1
United Kingdom

"A NoSQL Document database (XML and Binary)." Does this exclude e.g. plain text? Para headed 'Forms' "eXist provides support XForms (another W3C standard) " suggest eXist supports XForms (another W3C standard)

Note from the Author or Editor:
I have reworded both issues in the first copy-edit.

Dave Pawson  Feb 05, 2014 
ePub
Page ch 1
United Kingdom

Para starting "With version 1.4 of eXist released in 2009, " "Switching to the official version is neigh impossible " Suggest neigh misspelled.

Note from the Author or Editor:
The editors have proposed correcting 'neigh' to 'virtually', and I agree that would be a good change.

Dave Pawson  Feb 05, 2014 
ePub
Page ch 2
United Kingdom

"view, installand uninstall" Missing space, install and Para headed 'installing and using the example code' "Click on the upload application icon (top left, looks like a cogwheel)" It doesn't - it appears as a stack of disks? functionality as described. Para headed Getting Stuff In and Out of the Database "eXist is an XML database. Amongst other file types, its primary concern for storage is XML documents. As such it can also hold your executing XQuery" xQuery is not (normally) XML, which makes this statement suspect? ex 2.2, 2.3 - No suggestion how these might be run? Using Saxon from the cmd line? Using oXygen? If from within eXist, how please?

Note from the Author or Editor:
Typos handeld in editing phase icon description changed in stack of disk There is a description on how to run the examples.

Dave Pawson  Feb 06, 2014 
ePub
Page ch 2
United Kingdom

"that returns to you the value of a parameter" Suggest clarify, delete 'to you'

Note from the Author or Editor:
that returns to you the value of a parameter

Dave Pawson  Feb 07, 2014 
ePub
Page ch 2
United Kingdom

"(The ! bang or simple map operator)." Link provided without explanation? Suggest insert 'See' prior to link or whatever the O'Reilly convention is. Later, section headed 'Searching the Plays' s/advice/advise/ since it is a verb. Same para "Letís assume there is a need or searching the plays for certain words or phrases." s/or/for typo? ======== Early in the book you said you would not show the result of running code, yet it is done repeatedly?

Note from the Author or Editor:
Handled in final editing phase

Dave Pawson  Feb 09, 2014 
ePub
Page ch 3
United Kingdom

"A module must have a namespace and its custom to use something that starts with a URL you own (to avoid name clashes)." s/custom/customary/ ??? ======== Changing permissions in the log collection, ticking the box then save, close, has no effect on the viewed permissions? Since the jnlp link has no effect (the java admin client) - no association perhaps? I'm stuck here.

Note from the Author or Editor:
Typo Handled in final editing phase I don't uinderstand the problems with the permission changes. Will investigate.

Dave Pawson  Feb 10, 2014 
ePub
Page ch 4
United Kingdom

"connect to a database sever with a fat client" s/sever/server/ ============= Again the java admin client is mentioned. Initially I assumed it was now outdated, yet again and again it comes up. Please note on my recent Linux box it fails to work.

Note from the Author or Editor:
The typo "sever" needs to be corrected to "server". It looks like the editors have already corrected this. The rest can be ignored.

Dave Pawson  Feb 10, 2014 
ePub
Page ch 4
United Kingdom

ch 4 / Collections "To a certain extend this can be mitigated" s/extend/extent/ ================ "All that being said, our approach would be to advise you to make decisions about document granularity " Could be greatly simplified? [Curiously, no mention is made of searchable plain text documents, neither binary or XML? ]

Note from the Author or Editor:
The typo "extend" needs to be corrected to "extent", I think the Editors already have that one. The rest does not need to change.

Dave Pawson  Feb 13, 2014 
ePub
Page ch 5
United Kingdom

Chap 5, Terminology. This is the third time you've equated collection | directory etc? =================== "Properties of collections and resources" First mention of 'client tool' ?? Should that be java admin client? ============== Under 'system collections' First mention of 'securitymanager' ? Perhaps link to ch 8? ======================== "according to the URL encoding rules," Perhaps a link to where they are defined? Perhaps http://tools.ietf.org/html/rfc3986#page-12 ? ===================== 'XMLDB URI's. "xmldb:exist:///db/mycollection/test.xml" It may be worth emphasising the 3 / characters?

Note from the Author or Editor:
FIrst three: evaluated but discarded Last two: text changed:

Dave Pawson  Feb 13, 2014 
ePub
Page ch 5
United Kingdom

However, we definitely advice against doing this! Suggest s/advice/advise/

Note from the Author or Editor:
Handled in final editing phase

Dave Pawson  Feb 24, 2014 
ePub
Page ch 5
United Kingdom

"Unfortunately, xmldb:encode-uri does not check for the optional xmldb:exist:// database prefix (see XMLDB URIís) and happily encodes xmldb:exist:///a/b/c into xmldb%3Aexist%3A/a/b/c which is probably not what you want." Query 'happily'. I can see it as being the fact that exist fails to recognise this string, but it could be misinterpreted as indicating 'happily for the user'? How about s/happily/erroneously/ ?

Note from the Author or Editor:
Changed

Dave Pawson  Feb 24, 2014 
ePub
Page ch 5
United Kingdom

"HTTP GET requests are the working horse for accessing data" s/working/work/ English? ======================= "Warning Applying an XSLT stylesheet this way always changes the responseís MIME type to text/html." Illogical surely if the transform output type is XML?

Note from the Author or Editor:
Handled in final editing phase

Dave Pawson  Mar 01, 2014 
PDF
Page 35
Paragraph before "Hello XQuery"

There is a missing "that" (or extra "There are") on There are other query parameters will let you limit the size...

Note from the Author or Editor:
Handled in final editing phase

Luis Tavera  Mar 09, 2014 
PDF
Page 38
Second paragraph in "HelloXForms" section

eXist has two third-party XForms processor built-in: should be eXist has two third-party XForms processorS

Note from the Author or Editor:
Handled in final editing phase

Luis Tavera  Mar 09, 2014 
PDF
Page 43
thrid and fourth bullets

References to "Romeo and Julia" should be "Romeo and Juliet"

Note from the Author or Editor:
Already changed.

Luis Tavera  Mar 09, 2014 
ePub
Page 46
second-last para

Using the /text() function will ensure we get the result as a text node. If we would not use this, the PLAY element itself would be returned (try it out if you want to). Should be Using the /text() function will ensure we get the result as a text node. If we would not use this, the TITLE element itself would be returned (try it out if you want to).

Note from the Author or Editor:
Pleas change the sentence (in the eXist 101 chapter): Using the /text() function will ensure we get the result as a text node. If we would not use this, the PLAY element itself would be returned (try it out if you want to). Should be Using the /text() function will ensure we get the result as a text node. If we would not use this, the TITLE element itself would be returned (try it out if you want to).

Alister Pillow  Sep 05, 2014 
PDF
Page 49
last line

functions that performs things not easily done with... should be functions that perform things not easily done with...

Note from the Author or Editor:
Handled in final editing phase

Luis Tavera  Mar 09, 2014 
PDF
Page 300
2nd note

Right margin goes outside of page.

Note from the Author or Editor:
Will be handled by final editing

Boris Lehečka  Aug 03, 2014 
Printed, PDF
Page 359
middle of page

Internal link in book was not rendered correctly. The question marks should be replaced with the second code callout icon (and thus refer the reader to code callout #2).

mhacker  Dec 09, 2014  Dec 09, 2014