I currently make sure that new CSL styles have a file name that is the
expanded title of the publisher/journal title/citation guide. Non-roman
characters are not allowed, ampersands in titles are replaced by "-and-",
and diacritics are just dropped.
A few months ago I went over most of the independent styles, adding ISSNs
and default-locales where they were missing, adding "The" to style titles
if they were clearly part of the journal title, and expanding many of the
abbreviated CSL style names. Having expanded style names makes it much
easier for me to visually browse the github style repo (e.g. I don't have
to remember that ajps.csl stands for the American Journal of Political
Science). There are still a few styles with abbreviations in the style
name. Those are mostly popular styles with abbreviations that should be
familiar to most people (like plos.csl), that have a lot of dependent
styles, or that ship with Zotero (like apa.csl). Ideally I would like to
have all names expanded.
I understand that changing file names (and thus style IDs, since our
current scheme aligns the two) can give some trouble, but the repository
was a bit of a mess, and things should be much more stable going forward. I
think the current system works fine, as long as Zotero keeps hosting its
Style Repository and we adhere to some basic guidelines regarding style
names.
Rintze
On Tue, Jun 19, 2012 at 2:10 PM, Bruce D'Arcus <[email protected]> wrote:
> Right. Just to clarify on the discrepancy between the two answers here
> I was mainly referring to larger issues, like id name changes, the
> fact on the base URI, whether in the future we want to entirely
> decouple identity from resolution (for example, using UUIDs for one,
> and URLs for the other), etc.
>
> On Tue, Jun 19, 2012 at 1:40 PM, Sebastian Karcher
> <[email protected]> wrote:
> > Yes, we have a convention for new styles:
> >
> https://github.com/citation-style-language/styles/wiki/Style-Requirements
> > "In most cases the name should be written out in full, e.g.
> > "journal-of-results.csl" instead of "jor.csl""
> > While that's not worded very firmly, in practice we've been spelling
> > out all ids for new styles.
> >
> > Changing IDs for existing styles seems trickier - I'm OK with using
> > dependent styles for transition, we did that when we removed the
> > Chicago styles w/o bibliography. Rintze is the main guardian of style
> > naming, so he'd have to say.
> > S.
> >
> >
> > On Tue, Jun 19, 2012 at 11:28 AM, Carles Pina <[email protected]>
> wrote:
> >> Hello,
> >>
> >> I know that I'm way late for this (this mail talks about old commits),
> >> but the same could happen in the future. Maybe I missed some
> >> discussion.
> >>
> >> The commit 457fea7b69fc4851f806ee81dce1e7a68db701fc or
> >> dbaa2c4d08a7839f585f90bdc8a76e63e34514ab changed the ID of some styles
> >> (while changing the name of some files), e.g.
> >>
> >> - <link href="http://www.zotero.org/styles/nlm"; rel="self"/>
> >> + <id>http://www.zotero.org/styles/national-library-of-medicine</id>
> >>
> >> Did we ever setup a style ID convention? This one has been expanded,
> >> but we have other styles that are just using the acronym.
> >>
> >> A new style should be using the abbreviation or the long name?
> >>
> >> At Mendeley, styleID is used in the document properties to identify
> >> the style. If styles changes the styleID at the moment Mendeley
> >> Desktop would ask the user to select another style, handled but not
> >> nice. Or we could leave for a while some dependant styles, etc.
> >>
> >> Not critical and mainly wondering if we have some convention.
> >>
> >> Regards,
> >>
> >> --
> >> Carles Pina | Software Engineer
> >> http://www.mendeley.com/profiles/Carles-Pina/
> >>
> >> Mendeley Limited | London, UK | www.mendeley.com
> >> Registered in England and Wales | Company Number 6419015
> >>
> >>
> ------------------------------------------------------------------------------
> >> Live Security Virtual Conference
> >> Exclusive live event will cover all the ways today's security and
> >> threat landscape has changed and how IT managers can respond.
> Discussions
> >> will include endpoint security, mobile security and the latest in
> malware
> >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> >> _______________________________________________
> >> xbiblio-devel mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
> >
> >
> >
> > --
> > ------
> > Sebastian Karcher
> > Ph.D. Candidate
> > Department of Political Science
> > Northwestern University
> >
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > xbiblio-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> xbiblio-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
