indexing repo (was call for comments on base URI issue)

I committed the start of what I’d done earlier on the HTML index genration:

https://github.com/citation-style-language/csl-utils/commit/0eaec33acee8093db1dd212dea2c09607fb5ed70

Basic idea is a script that takes a csl git repo as input, with three
options for output:

  • json
  • html
  • all

If anyone has time and inclination, please feel free to fork. And no,
I don’t care what language it’s in, so long as it’s Ruby or Python :slight_smile:

Bruce

I think that this index idea threatens to undermine the whole idea of
resolvable style IDs-- if clients are supposed to ask
citationstyles.org for a list of style statuses and update styles
accordingly, what do they do for styles not indexed by
citationstyles.org? A system that hinges primarily on the individual
style URIs is much easier to implement (at least on the client side,
and on the server side too, if we don’t mind the traffic), and it
makes it possible for organizations to host styles for internal use
that update automatically, using the same mechanism as
citationstyles.org styles. It’s all about loose coupling, right?

Avram2011/3/19 Bruce D’Arcus <@Bruce_D_Arcus1>:

I’m agnostic on this (as I said, it may be a bad idea), but …

I think that this index idea threatens to undermine the whole idea of
resolvable style IDs-- if clients are supposed to ask
citationstyles.org for a list of style statuses and update styles
accordingly, what do they do for styles not indexed by
citationstyles.org? A system that hinges primarily on the individual
style URIs is much easier to implement (at least on the client side,
and on the server side too, if we don’t mind the traffic), and it
makes it possible for organizations to host styles for internal use
that update automatically, using the same mechanism as
citationstyles.org styles. It’s all about loose coupling, right?

  1. isn’t what I’m suggesting here already how Zotero and Mendeley work?

  2. I don’t necessarily think this precludes direct access, for styles
    external to the indexed repositories.

Bruce

Avram

I committed the start of what I’d done earlier on the HTML index
genration:

<
https://github.com/citation-style-language/csl-utils/commit/0eaec33acee8093db1dd212dea2c09607fb5ed70On Mar 19, 2011 2:09 PM, “Avram Lyon” <@Avram_Lyon> wrote:
2011/3/19 Bruce D’Arcus <@Bruce_D_Arcus1>:

Basic idea is a script that takes a csl git repo as input, with three
options for output:

  • json
  • html
  • all

If anyone has time and inclination, please feel free to fork. And no,
I don’t care what language it’s in, so long as it’s Ruby or Python :slight_smile:

Bruce


Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d


xbiblio-devel mailing list
xbiblio-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel


Was just looking at the headers on github files. Turns out they
include the sha1, which should be enough to know whether a local style
is out of date.

Not sure what the RateLimit-Remaining means in practice, as it doesn’t
change if I issue multiple head requests, or even multiple file
downloads.

$ curl -I https://github.com/citation-style-language/styles/raw/master/apa.csl
HTTP/1.1 200 OK
Server: nginx/0.7.67
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Status: 200 OK
X-RateLimit-Limit: 100
ETag: "7215ee9c7d9dc229d2921a40e899ec5f"
X-GitHub-Blob-Type: text/plain
X-RateLimit-Remaining: 100
X-Runtime: 21ms
Content-Length: 1
X-GitHub-Blob-Size: 12371
X-GitHub-Blob-Sha: 78d2134e44a05f261364ee8e34d391911a24fe8a
Set-Cookie: _gh_sess=BAh7BzoRbG9jYWxlX2d1ZXNzMCIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA%3D%3D–719def2ab2d99283383e374327fcdbb716c45c12;
path=/; expires=Fri, 01 Jan 2021 00:00:00 GMT; secure; HttpOnly
X-GitHub-Blob-Mode: 100644
X-Content-Type-Options: nosniff
Cache-Control: private, max-age=0, must-revalidateDate: Sun, 20 Mar 2011 15:26:16 GMT