Sebastian Karcher wrote > 1. Minor Update (terms, types, and variables) > There's a fair number of proposed terms, variable&types that we should add > to CSL, most of them listed here > https://github.com/avram/zotero-bits/issues/ We'd also, in that process, > re-license the schema under MIT in line with our general governance > standards. > Any addition of these should be very straightforward for processors to > include and obviously the change would be backward compatible for old > styles. Our tentative goal for this would be within the next 3-4 months > > Two things for people to comment/check on: > a) if you have something you'd like to see added that fits in this broad > description and isn't listed at the link above, now would be a good time > to > bring that up.
One set of changes that probably still needs substantial discussion is determining the set of fields that should be added for "nested" events (e.g., a paper in a symposium in a conference). Initial discussion was here: https://github.com/avram/zotero-bits/issues/60 The minimum set of fields I think satisfy all use cases are: (1) the title of the paper (smallest unit), (2) the title of the paper sessions where the paper is presented, (3) the title of the sub conference, section, or track at the conference (this could also be used for things like lecture series), (4) the name of the overall event. Mapping to CSL fields: Title of paper <--> title Title of session <--> session-title Title of track/subconference <--> track-title (could also use series-title here if that isn't perverting the use of that term too much) Title of conference <--> event-name Sebastian Karcher wrote > 2. Major update (unclear timeline, maybe summer 2016?) > The main things we'd like to see would be > a) distinction between continuously paginated journals and those that are > not for APA and similar styles. This comes up a lot & is super annoying to > automate. We think that from the CSL side, we would just introduce a > variable like "continuously-paginated" which defaults to true (since most > journals are) and leave it to reference managers on how exactly to > implement, though we'd be happy to host metadata to help automatize this, > crowdsourced or otherwise. If the default for "continuously-paginated" is true, would it be easier for clients and processors to implement if the variable were "paginated-by-issue" with default to false, so that the absence of the variable implies false? As for implementation, I imagine this could be handled in a similar way as journal abbreviations with either a set curated list (ala Zotero) or user-editable database (ala Frank's Abbreviations Plugin for Juris-M) being first choice and whatever is defined for the item in the client being used as a fallback. Sebastian Karcher wrote > b) Implementing a distinction between (author date) and author (date). > This > is being requested a lot and the lack of proper support makes things hard > particularly for citation styles like APA with changing et al. > requirements > depending on position of the cite. To assure that one of CSL's key > features > -- one click conversion between author-date and footnotes styles, remains > in tact this means authors also need to be included in corresponding > citations for numeric and note styles, i.e. Smith (1776) needs to turn > into > Smith [1] or Smith ^1 respectively. Pandoc-citeproc already does this, and > up to this point this could all be handled in the ref managers, > processors. > > Where we would need a CSL chance is to allow for different formatting > outside of the parentheses. E.g. APA (again!) has (Smith & Marx, 1776), > but > Smith and Marx (1776), so we would need to allow for two formats in > cs:citation depending on the type of citation. APA's specific in-text formatting requirements are: 1. "Smith and Marx (1776)" versus "(Smith & Marx, 1776)" 2. "Smith, Marx, and Jones (1776)" for first appearance, "Smith et al. (1776)" for subsequent appearances 3. "Smith et al. (1776)" for the first appearance in a paragraph, "Smith et al." for subsequent appearances in the same paragraph (unless this is ambiguous, in which case the year is included each time) 4. Alternative phrases (e.g., "and colleagues") are allowed instead of et al. for in-text citations 5. The year can be free-floating, instead of in parentheses (e.g., "In their 1776 review, Smith and Marx argued...") The first two are what Sebastian already brought up. The third requires that a system similar to the "near-note" or "ibid" functionality exist (note that multiple in-text citations can be referred to without a year so long as they are unambiguous--e.g., when comparing two papers) and that it can be separately applied to in-text versus standard citations. The fourth item is probably not worth dealing with in CSL. It is probably best handled by just surpassing the author (current practice). The fifth item would require both in-text citation formatting and the option to suppress the year (which citeproc-js can already do). This way, the user could manually type the year, then add a citation formatted as "Smith et al." so that it is formatted corrected. Including an option to format a reference as "Year" without the parentheses is probably not worth the hassle. (For feature comparison, Endnote provides (Author, Year), Author (Year), suppress Author, and suppress Year options.) -- View this message in context: http://xbiblio-devel.2463403.n2.nabble.com/CSL-2016-second-instalment-specification-updates-tp7579446p7579447.html Sent from the xbiblio-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ xbiblio-devel mailing list xbiblio-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
