gistfile1.txt

NEW

``disambiguate-add-year-suffix`` [Step (4)]
    If set to "true" ("false" is the default), an alphabetic year-suffix is
    added to ambiguous cites (e.g. "Doe 2007, Doe 2007" becomes "Doe 2007a, Doe
    2007b") and to their corresponding bibliographic entries. The assignment of
    the year-suffixes follows the order of the bibliographies entries, and
    additional letters are used once "z" is reached ("z", "aa", "ab", ..., "az",
    "ba", etc.). By default the year-suffix is appended to the cite, and to the
    first year rendered through ``cs:date`` in the bibliographic entry, but its
    location can be controlled by explicitly rendering the "year-suffix" variable
    using ``cs:text``. If "year-suffix" is rendered through ``cs:text`` in the
    scope of ``cs:citation``, it is suppressed for ``cs:bibliography``, unless
    it is also rendered through ``cs:text`` in the scope of ``cs:bibliography``,
    and vice versa.

OLD

``disambiguate-add-year-suffix`` [Step (4)]
    If set to "true" ("false" is the default), a year-suffix is added to
    ambiguous cites (e.g. "Doe 2007, Doe 2007" becomes "Doe 2007a, Doe 2007b").
    The placement of the year-suffix, by default appended to each cite, can be
    controlled by explictly rendering the "year-suffix" variable using
    ``cs:text``.

If that's true, then there may be two different rules to create a
suffix, and so consequently both of us are also wrong (your
explanation does not work for APA and Chicago, and mine doesn't work
for Elsevier, etc.).

There might be, but again, we haven't seen any examples that are not correctly handled under the existing specification. The APA, Chicago and Elsevier guides describe disambiguation in different language, but as they are editorial guides (rather than specification documents), none of them dictate a comprehensive set of mandatory rules, complete with a description of the logical sequence of operations needed for machine-driven disambiguation. The question should not be whether these guides can be read to require output that CSL is incapable of producing, but whether copy editors actually do read them in that way. It never hurts to gather more information about editorial processes, but at the moment we have zero evidence of that.

That's not precise enough. Year-suffixes can be required even when the names aren't the same. E.g (Doe 2000a, b) for a style that doesn't do name disambiguation, and has to disambiguate papers, one by John and one by Jane Doe.

True, but the examples are sensible. Perhaps Bruce would be willing to see the text amended to read "multiple cites to the same author and year"?

On Fri, Jun 17, 2011 at 11:08 PM, fbennett ***@***.*** wrote: > That's not precise enough. Year-suffixes can be required even when the names aren't the same. E.g (Doe 2000a, b) for a style that doesn't do name disambiguation, and has to disambiguate papers, one by John and one by Jane Doe.

Is this a hypothetical concern, or a real one? If a real one (and so there are style editors perverse enough to actually require this), then I think a description of these cases should be included in that placeholder I put at the end. I wasn't intending it to be all-encompassing.

True, but the examples are sensible. Perhaps Bruce would be willing to see the text amended to read "multiple cites to the same author and year"?

Does that really address Rintze's concern? Bruce

On Sat, Jun 18, 2011 at 3:59 AM, bdarcus [email protected] wrote:

On Fri, Jun 17, 2011 at 11:08 PM, fbennett ***@***.*** wrote: > > That's not precise enough. Year-suffixes can be required even when the names aren't the same. E.g (Doe 2000a, b) for a style that doesn't do name disambiguation, and has to disambiguate papers, one by John and one by Jane Doe. Is this a hypothetical concern, or a real one?

It's a real case, there are styles that work this way.

If a real one (and so there are style editors perverse enough to actually require this), then I think a description of these cases should be included in that placeholder I put at the end. I wasn't intending it to be all-encompassing. > True, but the examples are sensible. Perhaps Bruce would be willing to see the text amended to read "multiple cites to the same author and year"? Does that really address Rintze's concern?

I don't know. Rintze?

…

Bruce ## Reply to this email directly or view it on GitHub: https://gist.github.com/1029888

I'll have to think about it a bit more.

The description of "disambiguate-add-year-suffix" should only discuss the reason for disambiguation if it differs from the reason for the other disambiguation options. Any shared requirements that activate disambiguation should be discussed in the introduction of the disambiguation section of the spec.

Would it be correct to say that, for all disambiguation methods, except for "disambiguate-add-givenname" with "givenname-disambiguation-rule" set to "all-names", "all-names-with-initials", "primary-name", or "primary-name-with-initials", disambiguation is performed to create an unambiguous link between the cite and the target bibliographic entry?

Yes. In those four cases, adding initials or full given names is more aggressive than strictly necessary for resolving cite/bib ambiguities. If one were to be picky, it would be a little more accurate to say "disambiguation is performed only when needed to create an unambiguous link between the cite and the target bibliographic entry".

Yes. In those four cases, adding initials or full given names is more aggressive than strictly necessary for resolving cite/bib ambiguities. If one were to be picky, it would be a little more accurate to say "disambiguation is performed only when needed to create an unambiguous link between the cite and the target bibliographic entry".

+1 Picky is good in specification work.