Hi, see my comments inline below
On 2013-06-10 09:42, Michael Kay wrote:
> On 7 Jun 2013, at 12:35, Eric Lilja wrote:
>> Hi! Thank you so much for releasing version 9.5, it's always exciting
>> when a new version of Saxon comes out! I have a few questions/comments.
>> By the way, I am using the professional version of Saxon.
>> Comment 1: In the changelog part of the documentation page at
>> http://saxonica.com/documentation/index.html#!changes, it would nice if
>> there was a category 'all', which would list all the changes in a single
>> page for easy reading (with headers taken from the categories). Also,
>> changelogs for maintenance releases don't seem to be present in the page
>> mentioned above, where can they be found? Maybe I missed them, but it
>> would also be nice with announcement emails to this list with changelogs
>> for maintenance releases to this list. I believe I only saw sporadic
>> such messages.
> Thanks for the suggestion. I have noted it as a feature request at
Thanks, I will keep an eye on it.
>> Question 1: I noticed that when I tried to compile one of my programs
>> which use Saxon with the new 9.5 version, it didn't build anymore
>> because of changes made to the definition net.sf.saxon.om.Item (relating
>> to generics). I want to stress that I have no problem with those changes
>> in themselves, but I think I missed it in the changelog. Maybe it wasn't
>> documented or I didn't read carefully enough.
> It comes under the scope of this change: "The classes ValueRepresentation and Value have been replaced by the new class Sequence. " mentioned at http://www.saxonica.com/documentation/#!changes/spi/9.4-9.5, though you would be excused for failing to spot that. When we make changes to interfaces like this (and we don't do it casually), we tend to assume that people will discover the change by virtue of a compile failure rather than by seeing it in the documentation.
Ah, I see.
>> Question 2: Looking at the same of my code mentioned in the first
>> question, I see that I am using the s9api for XQuery and
>> net.sf.saxon.om-classes for XPath. Is s9api the recommend api for
>> XQuery? I believe I saw on this list once it is recommended api to use.
>> What about XPath, is the net.sf.saxon.om-classes what I should be using
>> or something else?
> For XQuery there are three interfaces, s9api, XQJ, and the "legacy" interface using StaticQueryContext. I would recommend use of s9api, unless XQJ is preferred for portability reasons.
> For XPath similarly there are three interfaces, s9api, JAXP, and the "legacy" interface using package net.sf.saxon.sxpath. Again, I would recommend s9api unless there are portability reasons for preferring JAXP.
Thank you, I will try using s9api for XPath as well then!