Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
"The fractional second string, if present, must not end in '0'"
2006-11-18T12:22:10.010Z vs. 2006-11-18T12:22:10.01Z (the former is incorrect).
Logged In: YES
I believe this behavior was introduced with the RI refactoring in 2.2.
BaseTripleGenerator.add(SubjectNode subject, PredicateNode predicate, Date dateValue, Set<Triple> set) is calling DateUtility.convertDateToString() which (rightfully) isn't mindful of XSD dateTime considerations.
I'll commit a fix for this in dev-143888 (Update Trippi for Mulgara).
I've committed a fix for this in dev-143888.
I'm not sure if this should be backported to maintenance-2.2. For users who are expecting the broken behavior (e.g. as input to DateFormat) this might break things. On the other hand, it *is* a bug and I believe it's new behavior (i.e., 2.1 didn't exhibit this behavior). Thoughts?
Fixed in trunk and maintenance-2.2 branch