Alright, how about let’s make this specific?
An example:
American Sociological Review http://purl.org/net/xbiblio/csl/styles/am_sociol_rev.csl http://purl.org/net/xbiblio/csl/styles/am_sociol_rev.cslProposed guidelines (subject to radical revision if people think it
sucks!)========================================================================
Identifiers and URLs
Style naming and identification are important to properly manage
styles, particularly in a distributed context. A style title provides a
natural language description to a user, while ids, links and file names
all provide information critical so that tools can properly access
styles.
CSL metadata borrows its content model from Atom. As with Atom, the id
element should contain a globally unique and stable identifier, encoded
as a uri.
In many cases, the value for the link element will be the same as the
id, but strictly speaking they need not be. An id provides for
identification, while link for resolution. Ideally, they are
coincident, but practically speaking, it is common that urls change.
Both of these are important because other aspects of the design are
based on them. For example, styles may contain an optional "basedOn"
element, which is a uri reference to the style from which it inherits.
The CSL namespace provides a convenient uri base for just this, and the
site to which it points a convenient place to store the styles. But one
can host a directory of styles anywhere, of course.
Style Names
For purposes of constructing the id and link values, and thus the file
name, you should abbreviate long titles, use underscores to replace
spaces, and use the “csl” filename extension. For example, a style file
for the “American Sociological Review” would be: am_sociol_rev.csl.
Core styles alone – such as APA and MLA – use shorter acronyms for
theiir file names and id and link values (apa.csl and mla.csl
respectively).
Questions:
Versions?
Variants?
Bruce