grouping/sections

CSL Development
1

Re: this issue:

https://sourceforge.net/tracker/?func=detail&atid=678021&aid=2180714&group_id=117435

Here’s my proposal:~~~~~~~~

a bibliography list may have one or more sections

biblist = element cs:list { heading, section+ }

If a section has a name attribute, it only includes entries placed

in that group by

an optional parameter on the citation reference with the same

value. All other

references go in the default (unnamed) section.

section = element cs:section { heading, attribute name { string }? }

heading = element cs:heading { formatting, attribute term { [TBD] }


I quickly looked at some of the bibtex options, but none seemed ideal.
For example, bibtopic indicates the different groups by using
different .bib files; that's not realistic in this context. Multibib
appears to require you to create a separate configuration to assign
items to the respective groups.

This approach seems simply and flexible, and also avoids
implementation headaches (an implementation can gradually add it
without having problems).

Comments?

Bruce

PS - We still need a way to have per/chapter bibs; probably an option
would be fine.
2

Re: this issue:

https://sourceforge.net/tracker/?func=detail&atid=678021&aid=2180714&group_id=117435

Here’s my proposal:

## a bibliography list may have one or more sections
biblist = element cs:list { heading, section+ }

## If a section has a name attribute, it only includes entries placed
in that group by
## an optional parameter on the citation reference with the same
value. All other
## references go in the default (unnamed) section.
section = element cs:section { heading, attribute name { string }? }

heading = element cs:heading { formatting, attribute term { [TBD] }

Nice.

A few thoughts … I wonder if the heading is needed in CSL? It might
be sufficient to allow the user to place the reference blocks
(sections) in their document individually, with the heading written as
part of the document. That would give users complete control over
formatting, and they could divide their reference list for a project
into subsections and whatnot without further complications in CSL.

… Would it be possible to allow runtime definition of section names
through an API to the processor? That would avoid the need for
modifications to a style just to get, say, a bibliography with
separate reference sections for the 1950’s, 1960’s and 1970’s.

… If section assignments are passed with citations, different
citations might attempt to assign the same item to different sections.
If the assignment is a property of the item, should the first
assignment win, or the last (or should this throw an error)?

3

…

A few thoughts … I wonder if the heading is needed in CSL? It might
be sufficient to allow the user to place the reference blocks
(sections) in their document individually, with the heading written as
part of the document. That would give users complete control over
formatting, and they could divide their reference list for a project
into subsections and whatnot without further complications in CSL.

… Would it be possible to allow runtime definition of section names
through an API to the processor? That would avoid the need for
modifications to a style just to get, say, a bibliography with
separate reference sections for the 1950’s, 1960’s and 1970’s.

Yeah, it’s occurred to me that this is an ambiguous case where it’s
unclear whether sectioning is generic to a style, or specific to a
user. In many cases, it seems to me, it will be the latter.

So in that case, either CSL doesn’t include this at all, or it allows
it to be overridden by a user.