Schema put in SVN attic

CSL Development
1

I just noticed that most of the SVN repository was thrown into the
attic, including the schema. I didn’t notice any announcement about
this, though.

I realize that development of the schema has migrated to bitbucket.
However, there are a lot of CSL files and probably still some
documentation that points to the old SVN schema. While the README
http://xbiblio.svn.sourceforge.net/viewvc/xbiblio/README is useful, I
don’t know if it is best to make everything that still links to the
pre-bitbucket version lead to a 404.

I don’t know if it was really planned to retire the SVN version of cthe
schema this abruptly: back in May of last year, there was talk of moving
citeproc-js to the attic & back in October, there was some discussion of
what to do with the old SVN stuff, but I haven’t seen much since then.

So, I’d propose being a little bit more conservative here: move only the
scema back out of the svn attic, add a comment to relevant files that
say the new version is at bitbucket, and make a concerted effort to
update all links to the schema.

Was there ever a purl for the schema? I don’t know what will happen
when/if we ever decide to migrate from bitbucket. It’d be nice to have
very stable URIs for the release versions of the schema.

–Rick

2

I just noticed that most of the SVN repository was thrown into the
attic, including the schema. I didn’t notice any announcement about
this, though.

Yeah, I just did that yesterday. Sorry about that.

For clarification, the reason is that we want to make clear most of
the stuff in the repo is out-of-date.

I realize that development of the schema has migrated to bitbucket.
However, there are a lot of CSL files and probably still some
documentation that points to the old SVN schema. While the README
http://xbiblio.svn.sourceforge.net/viewvc/xbiblio/README is useful, I
don’t know if it is best to make everything that still links to the
pre-bitbucket version lead to a 404.

I don’t know if it was really planned to retire the SVN version of cthe
schema this abruptly: back in May of last year, there was talk of moving
citeproc-js to the attic & back in October, there was some discussion of
what to do with the old SVN stuff, but I haven’t seen much since then.

So, I’d propose being a little bit more conservative here: move only the
scema back out of the svn attic, add a comment to relevant files that
say the new version is at bitbucket, and make a concerted effort to
update all links to the schema.

So what are the relevant links? The oxygen-specific PIs in the CSL
instances? If yes, then:

a) they’re not really critical (they don’t impact the validity of the
style, and are only an inconvenience for people that are using oxygen)

b) we need to update existing styles to the 1.0 schema anyway, so can
strip out the PIs then

So is it really necessary to move the schema back?

Was there ever a purl for the schema? I don’t know what will happen
when/if we ever decide to migrate from bitbucket. It’d be nice to have
very stable URIs for the release versions of the schema.

The PURL for the namespace URI nows points to citationstyles.org.

Bruce

3

Yeah, this broke Zotero’s build script, too, since Zotero was using an
svn:externals to pull in the locale files. For now I’ve committed the
0.8 locale files directly to Zotero’s SVN.

Is there an SVN interface to Bitbucket that would allow us to continue
using svn:externals? If not, I’m guessing we’re going to need to do this
manually, with the locales duplicated in Zotero’s SVN (to allow for
running Zotero directly from a working copy) and periodically updated
manually.

4

Well, so maybe we ought to back up and ask devs: is there any problem
with this path we’ve taken?

Bruce

5

I put up some files so users won’t get the 404’s (
http://sourceforge.net/apps/trac/xbiblio/changeset/1223):

CSL 0.8 schema:
http://xbiblio.svn.sourceforge.net/viewvc/xbiblio/csl/schema/tags/0.8/csl.rnc

CSL 0.8.1 schema:
http://xbiblio.svn.sourceforge.net/viewvc/xbiblio/csl/schema/tags/0.8.1/csl.rnc
and
http://xbiblio.svn.sourceforge.net/viewvc/xbiblio/csl/schema/trunk/csl.rnc

I also changed the readme to point towards citationstyles.org.

Rintze

6

Is there an SVN interface to Bitbucket that would allow us to continue
using svn:externals?

I don’t think so. There seem to be some ways to automate synchronization
though:
http://mercurial.selenic.com/wiki/WorkingWithSubversion

If not, I’m guessing we’re going to need to do this
manually, with the locales duplicated in Zotero’s SVN (to allow for
running Zotero directly from a working copy) and periodically updated
manually.

Note that the current directory structure of
http://bitbucket.org/bdarcus/csl-locales/src/ isn’t suitable for integrating
translation updates coming from Babelzilla. We need at least two
directories: a trunk and a branch for CSL 0.8.x, as CSL 0.8.x and 1.0 use
different layouts for the locale files.

Rintze