On Jun 19, 2007, at 2:48 AM, Dan Stillman wrote:
> On 6/18/07 3:09 PM, Bruce D'Arcus wrote:
>> What I'd to be able to do sometime soon is:
>> 1. load a CSL for his journal onto the web
>> 2. send him the URI for it, which he pastes into a field in Zotero
>> The rest (downloading, caching, etc.) would happen automatically.
> Some questions/thoughts:
> 1) How do you see updates being handled? Via an XML-based index file
> that contains version/timestamp information for all CSL files on a
Probably. This is why we were earlier talking about using Atom. So user
would subscribe to a repository (in a large repository, it might be one
for their field though).
I suppose a simple way to start is to use the time-stamp in the file,
> 2) Are the location and name of the index file specified in the CSL, or
> are they implicit (say, a default file name in the same directory of
> already downloaded files, or a walk up the paths until one is found (to
> handle a repository with a hierarchical directory structure))? For
> various reasons, some method of determining the index file from a given
> CSL file would be helpful.
Agreed. And I would say the latter. So we take the APA example. Let's
say we move it to your repository, and we give it the stable URI
I would expect at the styles directory to see something like:
index.xml (probably an Atom file)
Note: some tricky issues with categorizing styles sometimes, so not
sure that's a good idea. I'm just imagining the goal, which is the
possibility that a repository might have hundreds, if not thousands, of
styles. Might be better to just do:
So a feed per subject/field, where each file also gets tagged with
those (from which the index file is generated).
> 3) What's the mechanism for downloading all styles from a repository? I
> imagine you'd be able to specify either a single CSL file or an entire
> repository (which might be the URL of the index file). If you point to
> the index file, can you pick and choose, or do you get them all?
I think ideally both.
I'd imagine a user would subscribe to a repository or repository
section just as they would a news feed. Perhaps they get a list of all
styles in that feed/repo, and can either select all or choose
individual styles to ... I don't know the verb ... activate (?).
> (This is a client implementation question, and I can't guarantee that
> approach or another would be implemented in Zotero, but I'm curious how
> you see it working.)
> 4) How are duplicates handled? If you post a style for your colleague
> test, and he installs it via the URL you provide, and then the style is
> moved into the main Zotero repository (to which my Zotero client is
> subscribed by default), what happens to the installed style on his
> computer? He can just delete the old one manually, of course, but
> citation processors should probably be expected to handle 301 redirects
> correctly for both index files and CSL files and switch to the
> redirected URL (at least if it resolves to a valid index/CSL file). If
> the index file exists and specifies a CSL file URL not below its path,
> that should probably also be treated as a permanent redirect for
> existing subscribers.
I agree this is a detail that's important. You probably have a better
sense than I. And perhaps the Atom spec might be helpful?