OK, John MacFarlane is asking for some resolution for this, so that he
can add a link to a repository of 1.0 styles in his README. So I’d
like to deal with this in the next 24-48 hours, but have some
remaining questions to resolve …
This sounds good to me.
So if this is a good, how should we go about proceeding? The detail
questions I have center on the ids/uris:
- Should 0.8 styles have different URIs from 1.0 styles?
Provided we are sure we want to host 0.8 styles at all, and deal with the
associated headache of keeping 0.8 and 1.0 styles in sync, they’d have to
have different URIs for dependent styles to work as implemented in Zotero
I don’t want to host 0.8 styles at all.
So what to do? I guess I’d lean towards having different URIs, and so
inserting a “1.0” as part of the fragment.
This is a pretty big decision so speak now or forever hold your peace.
In an ideal world, I think we’d use the same URI and use either a client
header or a query string appended to the URI to choose which version to
return, or give a 300 Multiple Choices response if neither are present. We
can implement this in Zotero, but we have no plans for a future Zotero 2.0.*
release at present, so maybe this is something that we should implement in
preparation for CSL 1.1 instead.
- how do we deal with the base URI? Do we want
"http://citationstyles.org" and somehow redirect to the github repo?
If the latter, how?
At least for the Zotero use case, this depends on whether we can serve the
styles as text/x-csl off of github. The Zotero repository allows serving as
both text/x-csl and text/xml, but I’m not sure that’s necessary.
We will want an HTML frontend on citationstyles.org that’s generated off of
a checkout anyway, so we could also serve off the checkout and avoid
redirecting, provided we can update it when the github repo changes.
OK, so maybe for the initial repo that John’s asking for, we can just
use the citationstyles.org base domain, but not worry about the
- how do we want to setup the repo and associated policies?
- what account? do we want a new “citationstyles” account with a
few different admins?
- how do we encourage style changes? Sign up at github, fork the
repo, and issue a pull request?
I’ll defer to others with greater DVCS experience on this issue, although
what you suggest sounds fine to me.
Here’s a discussion of github’s “organizations” model:
Is that appropriate for us, such that we want a “Citation Styles” organization?
Some other suggestion(s)?