Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Markus, Fabian, and all:
In my tests of the enhanced Date datatype, I've encountered a minor
problem with annotating imprecise dates in models other than the
Gregorian. Specifically, when I annotate a date with a year and a month,
in a model other than Gregorian (specifically the Ussher-Jones Biblical
model), and then browse or query the result, I get back a value that is
one month earlier than originally annotated, though the year remains the
same. I believe that what is happening is this: Having preserved the
original imprecision of the date, the script, when parsing an XSD value
and unit (the unit is the calendar preference), creates a new JD out of
a proleptic Gregorian month and year. But this JD is significantly
earlier than the original--early enough to fall back one month.
I tried changing the form of the XSD value to a model other than the
proleptic Gregorian. The result was that the printouts simply disappeared.
I believe that the best solution is to pass the JD itself as one of the
DB Keys. The problem: in SMW 1.4.2, the function parseDBKeys($args)
seems to be called by parseXSDValue($value,$unit), in the form
If, on the other hand, the functions getDBKeys() and parseDBKeys($args)
are the primary functions, then in theory the array returned by
getDBkeys() could have any number of elements--in which case I could
pass as many elements of the datatype as I needed to.
As I said, this is a minor problem, and one that I do not wish to solve
by creating another. Perhaps I should wait to try to solve it, until I
port my enhancements to the current version of SMW (1.4.3).
If I'm missing anything, I'd like someone to let me know.