Hi,
just one addition to my previous post:
- When selecting as XML, the literal value is carrying a ' ' (space)
rather than a 'T' between date and time for xsd:dateTime, e.g.
"2010-04-05 10:01:34.232"
This applies to xsd:dateTime values WITH OR WITHOUT TIMEZONE, i.e. cases
2 and 3 below.
Cheers,
Martin
On 15.12.2011 12:04, Martin Gerlach wrote:
Hi,
has there been any progress on the DateTime/timezone bug as reported
by Timo in May?
Are there any patches or even new releases containing a fix?
In Virtuoso OS 6.0.1.3127 I observed the following behaviours not
conforming to the XSD data type specifications:
1. Using the SPARQL endpoint, insert a DATE WITH TIMEZONE as xsd:date
literal, e.g. "2010-04-05+02:00"^^xsd:date
- The timezone information does not seem to be even stored at all,
resulting in triples overwriting each other if the objects to be
inserted are xsd:date literals with different time zones
- At least it is not returned by SELECT for result types HTML, JSON,
XML, NTriples, Javascript, RDF/XML, Spreadsheet (HTML table)
2. Using the SPARQL endpoint, insert a DATETIME OR TIME WITHOUT
TIMEZONE as xsd:time literal, e.g.
"2010-04-05T10:01:34.232"^^xsd:dateTime or "10:01:34.232"^^xsd:time
- The timezone seems to be automatically added which is incorrect, it
should be left unspecified internally.
- At least the literal value is returned incorrectly as "...+01:00"
(I'm in Berlin) for all result types except XML
- When selecting as XML, no timezone is returned (probably as a result
of bug 3, see below)
3. Using the SPARQL endpoint, insert a DATETIME OR TIME WITH TIMEZONE
as xsd:time literal, e.g.
"2010-04-05T10:01:34.232+02:00"^^xsd:dateTime or
"10:01:34.232+02:00"^^xsd:time
- When selecting as XML, the literal value is carrying a ' ' (space)
rather than a 'T' between date and time for xsd:dateTime, e.g.
"2010-04-05 10:01:34.232"
- When selecting as XML, no timezone is returned no matter which one
was set
- The correct literal value is returned for both types when selecting
as another result type (tested HTML, JSON, XML, NTriples, Javascript,
RDF/XML, Spreadsheet (HTML table))
4. Using the SPARQL endpoint, insert a literal with type
xsd:gYearMonth, e.g. "2010-04"^^xsd:gYearMonth
- The literal seems to be incorrectly stored as
"2010-04-01T00:00:00+01:00"^^xsd:gYearMonth - i.e. wrong padding, and
incorrect automatic addition of the current timezone
- When querying with result type XML, the literal value is returned
incorrectly as "2010-04-01 00:00:00" (see 1 above), for all other
types the incorrectly padded and timezoned lexical representation is
returned.
5. Using the SPARQL endpoint, insert literal with type xsd:gYear, e.g.
"2010"^^xsd:gYear
- The literal seems to be incorrectly stored as
"2010-01-01T00:00:00+01:00"^^xsd:gYear - i.e. wrong padding, and
incorrect automatic addition of the current timezone
- When querying with result type XML, the literal value is returned
incorrectly as "2010-01-01 00:00:00" (see 1 above), otherwise the
incorrectly padded and timezoned lexical representation is returned.
xsd:gMonth, xsd:gMonthDay, xsd:gDay seem to be handled correctly.
Regards,
Martin
On 16.05.2011 01:09, Hugh Williams wrote:
Hi Timo,
No ETA yet, I shall seek one from development ...
Best Regards
Hugh Williams
Professional Services
OpenLink Software
Web: http://www.openlinksw.com
Support: http://support.openlinksw.com
Forums: http://boards.openlinksw.com/support
Twitter: http://twitter.com/OpenLink
On 13 May 2011, at 07:39, Timo Westkämper wrote:
Hi Hugh.
Is there any ETA for the bug fix?
Br
Timo Westkämper
On 05/08/2011 01:41 AM, Hugh Williams wrote:
Hi Timo,
This is logged on our internal bugzilla system which external users
do not have access to ...
Best Regards
Hugh Williams
Professional Services
OpenLink Software
Web: http://www.openlinksw.com <http://www.openlinksw.com/>
Support: http://support.openlinksw.com <http://support.openlinksw.com/>
Forums: http://boards.openlinksw.com/support
Twitter: http://twitter.com/OpenLink
On 6 May 2011, at 12:50, Timo Westkämper wrote:
Hi Hugh.
Could you send me a link to the ticket? Thanks.
Br,
Timo Westkämper
On 05/06/2011 02:48 PM, Hugh Williams wrote:
Hi Timo,
This problem and been recreated and reported to development for
resolution ...
Best Regards
Hugh Williams
Professional Services
OpenLink Software
Web: http://www.openlinksw.com <http://www.openlinksw.com/>
Support: http://support.openlinksw.com
<http://support.openlinksw.com/>
Forums: http://boards.openlinksw.com/support
Twitter: http://twitter.com/OpenLink
On 4 May 2011, at 14:52, Timo Westkämper wrote:
Hi.
Sorry for my amount of mails on this list, but I had really lots
of troubles with Virtuoso lately.
I found a reproducable sequence which presents one of my
problems with dateTime literal handling in Virtuoso :
* Insert the following triples via the ttlp function :
ttlp ('<http://test> <http://test/> <http://test1>
<http://test1/>
"2000-01-01T00:00:00.000Z"^^<http://www.w3.org/2001/XMLSchema#dateTime>
. <http://test> <http://test/> <http://test2> <http://test2/>
"2000-01-01T00:00:00.000+02:00"^^<http://www.w3.org/2001/XMLSchema#dateTime>
.', '', 'http://test <http://test/>', 0);
* Execute the following query via the Interactive SQL window :
sparql select * where { <http://test> <http://test/> ?p ?o }
The results are :
http://test1 <http://test1/> 2000-01-01 00:00:00
http://test2 <http://test2/> 2000-01-01 00:00:00
* Execute the same query via the SPARQL query form :
select * where { <http://test> <http://test/> ?p ?o }
The results are :
http://test1 <http://test1/> 2000-01-01T00:00:00Z
http://test2 <http://test2/> 2000-01-01T00:00:00+02:00
I am having the same issue when using SPARQL via JDBC. The
timezone offset is ignored when using SPARQL via JDBC or the
Interactive SQL form.
Br,
Timo Westkämper
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
<mailto:Virtuoso-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
<mailto:Virtuoso-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
<mailto:Virtuoso-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
<mailto:Virtuoso-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/virtuoso-users