On Thu, Jun 12, 2014 at 9:52 PM, Bruce D'Arcus <bdar...@gmail.com> wrote:
> I get confused by long messages ;-)
>
> Can we start with big picture? Please confirm the following:
>
> 1) this question is driven by the idiosyncrasies of supra referencing?*
>
Yes.
> 2) CSL doesn't currently support supra referencing, and so this is an
> extension in MLZ?
>
It does, actually: first-reference-note-number is one of the standard CSL
variables, from CSL 1.0:
http://citationstyles.org/downloads/specification.html#standard-variables
CSL also supports the "five-footnote rule" imposed by some legal styles:
http://citationstyles.org/downloads/specification.html#note-distance
> If both are true, perhaps you should go with your suggestion (which seems
> reasonable), see how it works, and use that experience to suggest possible
> additions or changes to CSL proper?
>
Yep!
> Bruce
>
> * I do know this is an important feature, but man I hate it; not only is
> it a PITA to implement, it's hostile to readers (me!). One additional
> wrinkle here related to both: what's the scope for back referencing in 600
> page book? The book? The chapter? The page? Do you need to allow this to be
> configured? If yes, how would you even implement it. ;-)
>
It's used almost exclusively in article-length works, scoped to the
individual article.
> On Jun 11, 2014 8:31 PM, "Frank Bennett" <biercena...@gmail.com> wrote:
>
>> A note on some fresh developments in citeproc-js land that affect the CSL
>> test suite.
>>
>> In response to feedback on the MLZ Bluebook style, I put in some work in
>> citeproc-js to get backreference glosses working. The form implemented for
>> Bluebook support looks like this:
>>
>> Smith, His Very Long Book Title (2000) [hereinafter Smith, His Book]
>>
>> The tricky bits are that (a) the gloss should be applied only if there
>> are subsequent back-references; and (b) the note number should be included
>> for disambiguation purposes. A test that captures the behaviour is here:
>>
>>
>> https://bitbucket.org/bdarcus/citeproc-test/src/737afd7171005f9d53cf221f8a71f21007d10386/processor-tests/humans/disambiguate_BasedOnSubsequentFormWithBackref2.txt
>>
>> A question for the list is whether first-reference-note-number should
>> always be included for disambiguation purposes, or whether it should be
>> discretionary. In the current implementation, it is included only if
>> givenname-disambiguation-rule="by-cite" (the default). When another rule is
>> used, the cite to Roe in the test fixture linked above would have the
>> gloss, and the backreference would show the title.
>>
>> While the name of givenname-disambiguation-rule suggests that it affects
>> only given names, the general effect of the "by-cite" rule is to make
>> citations as compact as possible; and dropping the gloss where is is not
>> strictly necessary has that effect.
>>
>> While testing the implementation, I found it necessary, in styles that
>> use disambiguate="true", to force a rerun of disambiguation for first
>> references that are moved in the document, together with all
>> back-references that point to it, to assure that the document reflects the
>> actual disambiguation state of each reference in the set. This change in
>> behaviour affected three tests in the test suite:
>>
>>
>> https://bitbucket.org/bdarcus/citeproc-test/commits/737afd7171005f9d53cf221f8a71f21007d10386
>>
>> Finally, to control the appearance of the gloss on first references, I
>> had to introduce a test condition (which I've added to the CSL-m schema)
>> that returns true only if there are subsequent references to the item:
>>
>>
>> https://github.com/fbennett/schema/commit/6881c98ae752e106b9c62673c5aa42d743fc0c7b
>>
>> A condition that tests for subsequent back-references is needed to
>> implement back-reference glosses, regardless of whether note numbers are
>> included for disambiguation purposes.
>>
>> Frank
>>
>>
>>
>> ------------------------------------------------------------------------------
>> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
>> Find What Matters Most in Your Big Data with HPCC Systems
>> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
>> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
>> http://p.sf.net/sfu/hpccsystems
>> _______________________________________________
>> xbiblio-devel mailing list
>> xbiblio-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>>
>>
>
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> xbiblio-devel mailing list
> xbiblio-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>
>
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
xbiblio-devel mailing list
xbiblio-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
