Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of
 andy.seaborne.apache@gmail.com designates 209.85.214.47 as permitted sender)
Sender: Andy Seaborne <andy.seaborne.apache@gmail.com>
Message-ID: <4FA3CA06.2000600@apache.org>
Date: Fri, 04 May 2012 13:22:30 +0100
From: Andy Seaborne <andy@apache.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:11.0) Gecko/20120410 Thunderbird/11.0.1
MIME-Version: 1.0
To: jena-dev@incubator.apache.org
Subject: ARQ changes: Rework date/time handling
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

I've just committed some changes to ARQ for how it handles dates and 
times (XSD dateTime, date, time, g*).

This set of changes adds nothing at the moment - it switches from using 
Jena's XSDDateTime class to java's XMLGregorianCalendar).  Jena's class 
is derived from Xerces but it does not provide arithmetic.

That's the reason for this change - now date/time arithmetic, including 
durations, can be added to SPARQL processing.

I kept using XSDDatetime for checking and parsing -- the Java library 
code adopts a "parse any lexical formlegal" approach so passing in a 
legal date and you mean a dateTime is not detected very nicely.


	Andy

PS One Java bug : Java does not accept a gMonth with a timezine of "Z", 
which is legal, albeit unusual.  A timezone of +00:00 is accepted, as is 
"Z" on gYear and other g*.