I don’t think we’ve set a revised target for the completion of CSL 1.0.
Shall we do that?
I think we need two milestones. The first would be 1.0RC2 (feature-freeze).
The second one would be 1.0 final, which should preferably coincide with the
release of updated documentation (specification & upgrade notes).
I wouldn’t mind updating the docs, but I’ll probably need 4-6 weeks to
(re)write everything after RC2 has been tagged (I happen to be quite busy 
).
Rintze
Just to let you know that I started working on the Haskell
implementation again, after a long stop. I’m finishing with the
implementation of everything needed by the test suite - BTW, Frank,
you did really a great job!
When the tests will be working (very soon since I just need to write
the HTML formatter for the output, now) I’ll update everything and
implement what’s still missing. So, if we set a target I’ll try to
comply with it.
Just a question: is the “input” array in the JSON test object meant to
be a reference API, for instance with regards to name structures? The
citations object could be a reference API too, for citation prefixes,
modifiers and locators. I saw a thread above about something like
this, but I must confess that catching up with the discussions of the
last 6 month is hard… 
Nice job, though, even if it makes mine quite challenging.
Andrea
Yeah, me too. I will have some time over the holiday break, but am not
sure how much.
How about we say Jan 31 for RC2, and March 1 for final?
Is that sensible, or too conservative?
Bruce
Good to see you again, Andrea.
I don’t think we’ve set a revised target for the completion of CSL 1.0.
Shall we do that?
Just to let you know that I started working on the Haskell
implementation again, after a long stop. I’m finishing with the
implementation of everything needed by the test suite - BTW, Frank,
you did really a great job!
Let’s hope it works. 
When the tests will be working (very soon since I just need to write
the HTML formatter for the output, now) I’ll update everything and
implement what’s still missing. So, if we set a target I’ll try to
comply with it.Just a question: is the “input” array in the JSON test object meant to
be a reference API, for instance with regards to name structures? The
citations object could be a reference API too, for citation prefixes,
modifiers and locators.
The specific structures in the tests (and in the citeproc-js manual at
http://gsl-nagoya-u.net/http/pub/citeproc-doc.html) haven’t been
agreed as a CSL-wide API. They are just my own idea of what seemed
workable as I was putting things together in the processor. There’s
not a requirement that the processor accept these specific JSON
structures as far as I know.
In fact, the interface for the citation object is about to change,
from Monday next week or so. The twinned arrays will be collapsed
into a single JS object, with the string representing the ID moved
inside it as an “id” field.
Despite this change, things are pretty quiet now, both with CSL and
with the citeproc-js code.
I saw a thread above about something like
this, but I must confess that catching up with the discussions of the
last 6 month is hard…Nice job, though, even if it makes mine quite challenging.
There are lots of twists and turns lurking in the specification. Post
if you run into issues, I should at least be able to describe whatever
solution I came up with.
I think we need two milestones. The first would be 1.0RC2 (feature-freeze).
The second one would be 1.0 final, which should preferably coincide with the
release of updated documentation (specification & upgrade notes).I wouldn’t mind updating the docs, but I’ll probably need 4-6 weeks to
(re)write everything after RC2 has been tagged (I happen to be quite busy
).Yeah, me too. I will have some time over the holiday break, but am not
sure how much.How about we say Jan 31 for RC2, and March 1 for final?
Is that sensible, or too conservative?
+1 for sensibly conservative
Just to give you guys a heads-up. I went through the upgrade notes, spec and
schema, and all three have been cleaned up and made up to date. The spec is
still missing a few details with regards to sorting, the display attribute
and disambiguation, but Frank agreed to fill those in when he finds the time
(being the disambiguation expert and all).
I’ll probably go through all of it once more to check everything’s there,
but I think we’re getting close to the event horizon of CSL 1.0. This might
be a good time for comments on the documentation before we call 1.0 final.
Rintze
Awesome!
Do you want to give a deadline for these comments?
Bruce
That partially depends on how busy you are :). We can still make our target
of March 1st, but maybe it’s better to take a bit more time to iron out any
bugs in the schema and unclarities in the spec. I still have to check
whether upgrade.xls works properly for the current draft, and CSL 1.0 locale
files need to be generated (using the data in the 0.8 locale files). It
might also be nice if citeproc-js supports CSL 1.0 at launch.
So how about 2 weeks (i.e. March 8th)? If all goes smoothly we can then call
1.0 a week or so later.
Rintze
Sounds good to me.
Bruce
Another short update: with the locale.sh and update-styles.sh scripts
available at http://bitbucket.org/bdarcus/csl-utils/, I’ve generated CSL 1.0
locale files (http://bitbucket.org/bdarcus/csl-locales/src/tip/trunk/) and
CSL 1.0 styles (
http://citationstyles.org/downloads/csl-styles-1.0-2010-2-27.zip.gz). The
locale files are based on the CSL 0.8 locale files from the Zotero SVN
(which I copied to
http://bitbucket.org/bdarcus/csl-locales/src/tip/branches/0.8/), whereas the
styles are based on a snapshot of the Zotero Style Repository (
http://citationstyles.org/downloads/csl-styles-0.8.1-2010-2-27.zip.gz). I
had to make some manual adjustments to a select number of styles (
https://www.zotero.org/trac/changeset/5797), but at the moment the entire
repository can be automatically converted.
Rintze
Another short update: with the locale.sh and update-styles.sh scripts
available at http://bitbucket.org/bdarcus/csl-utils/, I’ve generated CSL 1.0
locale files (http://bitbucket.org/bdarcus/csl-locales/src/tip/trunk/) and
CSL 1.0 styles
(http://citationstyles.org/downloads/csl-styles-1.0-2010-2-27.zip.gz). The
locale files are based on the CSL 0.8 locale files from the Zotero SVN
(which I copied to
http://bitbucket.org/bdarcus/csl-locales/src/tip/branches/0.8/), whereas the
styles are based on a snapshot of the Zotero Style Repository
(http://citationstyles.org/downloads/csl-styles-0.8.1-2010-2-27.zip.gz). I
had to make some manual adjustments to a select number of styles
(https://www.zotero.org/trac/changeset/5797), but at the moment the entire
repository can be automatically converted.
Congrats! Splendid work.