Author-Editor collapse

Dear all,

are author-editor collapses possible (analogously to the editor-translator case)? The specs do not mention this case, in fact, editor-translator is called the single exception in the ‘Names’ description (); however, in the unit test ‘name_AuthorCountWithSameVarContentAndCombinedTerm’ the author and editor variables are indeed collapsed for counting. This is despite the fact that the specification of ‘count’ () clearly mentions that the intended result is ‘the total number of names that would be otherwise displayed by the use of the cs:names element (taking into account the effects of et-al abbreviation and editor/translator collapsing)’.

(*) http://citationstyles.org/downloads/specification.html#names
(**) http://citationstyles.org/downloads/specification.html#name

I would expect the result to be 4 instead of 2 since the spec calls for the author and editor variables to be displayed regardless of the fact that the names in question are identical.

Best,

Sylvester

Dear all,

are author-editor collapses possible (analogously to the editor-translator case)? The specs do not mention this case, in fact, editor-translator is called the single exception in the ‘Names’ description (); however, in the unit test ‘name_AuthorCountWithSameVarContentAndCombinedTerm’ the author and editor variables are indeed collapsed for counting. This is despite the fact that the specification of ‘count’ () clearly mentions that the intended result is ‘the total number of names that would be otherwise displayed by the use of the cs:names element (taking into account the effects of et-al abbreviation and editor/translator collapsing)’.

(*) http://citationstyles.org/downloads/specification.html#names
(**) http://citationstyles.org/downloads/specification.html#name

I would expect the result to be 4 instead of 2 since the spec calls for the author and editor variables to be displayed regardless of the fact that the names in question are identical.

Well spotted, that’s clearly wrong. Adding another test with
translator rather than editor, and amend the result in this one.

(I’ll also be pushing a bunch of tests and amendments that have piled
up locally.)

Frank

Dear all,

are author-editor collapses possible (analogously to the editor-translator case)? The specs do not mention this case, in fact, editor-translator is called the single exception in the ‘Names’ description (); however, in the unit test ‘name_AuthorCountWithSameVarContentAndCombinedTerm’ the author and editor variables are indeed collapsed for counting. This is despite the fact that the specification of ‘count’ () clearly mentions that the intended result is ‘the total number of names that would be otherwise displayed by the use of the cs:names element (taking into account the effects of et-al abbreviation and editor/translator collapsing)’.

(*) http://citationstyles.org/downloads/specification.html#names
(**) http://citationstyles.org/downloads/specification.html#name

I would expect the result to be 4 instead of 2 since the spec calls for the author and editor variables to be displayed regardless of the fact that the names in question are identical.

Well spotted, that’s clearly wrong. Adding another test with
translator rather than editor, and amend the result in this one.

Actually, I may have just stumbled upon another one:

The name_OnlyGivenname test contains only the given name ‘Banksy’ and an ‘initialize-with’ attribute; the expected output is ‘Banksy’ but the spec states that if ‘initialize-this’ is set, given names are to be initialized.

Now, I suppose this one is a feature rather than a bug, because it makes perfect sense to me to not initialize the given name if that is the only name (the choice of ‘Banksy’ seems to point in that direction, too); however, in this case, the specification should read: initialize given names if ‘initialize-with’ is set and … (at least a family name exists?).

Perhaps this is specified somewhere, but it is clearly missing in the description of the ‘initialize-with’ attribute in the ‘Name’ section.

Just wondering.

(I’ll also be pushing a bunch of tests and amendments that have piled
up locally.)

Great! Will you push these to the mercurial repository?

Thanks

Sylvester

PGP.sig (195 Bytes)

Dear all,

are author-editor collapses possible (analogously to the editor-translator case)? The specs do not mention this case, in fact, editor-translator is called the single exception in the ‘Names’ description (); however, in the unit test ‘name_AuthorCountWithSameVarContentAndCombinedTerm’ the author and editor variables are indeed collapsed for counting. This is despite the fact that the specification of ‘count’ () clearly mentions that the intended result is ‘the total number of names that would be otherwise displayed by the use of the cs:names element (taking into account the effects of et-al abbreviation and editor/translator collapsing)’.

(*) http://citationstyles.org/downloads/specification.html#names
(**) http://citationstyles.org/downloads/specification.html#name

I would expect the result to be 4 instead of 2 since the spec calls for the author and editor variables to be displayed regardless of the fact that the names in question are identical.

Well spotted, that’s clearly wrong. Adding another test with
translator rather than editor, and amend the result in this one.

Actually, I may have just stumbled upon another one:

The name_OnlyGivenname test contains only the given name ‘Banksy’ and an ‘initialize-with’ attribute; the expected output is ‘Banksy’ but the spec states that if ‘initialize-this’ is set, given names are to be initialized.

Now, I suppose this one is a feature rather than a bug, because it makes perfect sense to me to not initialize the given name if that is the only name (the choice of ‘Banksy’ seems to point in that direction, too); however, in this case, the specification should read: initialize given names if ‘initialize-with’ is set and … (at least a family name exists?).

Perhaps this is specified somewhere, but it is clearly missing in the description of the ‘initialize-with’ attribute in the ‘Name’ section.

Just wondering.

This does look like a case where an amendment to the specification
would be appropriate.

This covers an edge case; if Banksy were entered as a family name, the
citeproc-js processor would treat it as an institution name. In that
case, leading personal names are treated as affiliated with the
institution, so you would get H. Smith, Banksy, instead of H. Smith &
Banksy.

The institution tests themselves are not in the standard repository,
but if this behavior is reserved it will avoid a conflict down the
line, if that extension to CSL is eventually added to the
specification.

Frank

(I’ll also be pushing a bunch of tests and amendments that have piled
up locally.)

Great! Will you push these to the mercurial repository?

Already there. It’s quite a bundle, sorry; I’d fallen behind.

But isn’t this a case that’s unresolved?

Dear all,

are author-editor collapses possible (analogously to the
editor-translator case)? The specs do not mention this case, in fact,
editor-translator is called the single exception in the ‘Names’ description
(); however, in the unit test
’name_AuthorCountWithSameVarContentAndCombinedTerm’ the author and editor
variables are indeed collapsed for counting. This is despite the fact that
the specification of ‘count’ (
) clearly mentions that the intended result
is ‘the total number of names that would be otherwise displayed by the use
of the cs:names element (taking into account the effects of et-al
abbreviation and editor/translator collapsing)’.

(*) http://citationstyles.org/downloads/specification.html#names
(**) http://citationstyles.org/downloads/specification.html#name

I would expect the result to be 4 instead of 2 since the spec calls
for the author and editor variables to be displayed regardless of the fact
that the names in question are identical.

Well spotted, that’s clearly wrong. Adding another test with
translator rather than editor, and amend the result in this one.

Actually, I may have just stumbled upon another one:

The name_OnlyGivenname test contains only the given name ‘Banksy’ and an
’initialize-with’ attribute; the expected output is ‘Banksy’ but the spec
states that if ‘initialize-this’ is set, given names are to be initialized.

Now, I suppose this one is a feature rather than a bug, because it makes
perfect sense to me to not initialize the given name if that is the only
name (the choice of ‘Banksy’ seems to point in that direction, too);
however, in this case, the specification should read: initialize given names
if ‘initialize-with’ is set and … (at least a family name exists?).

Perhaps this is specified somewhere, but it is clearly missing in the
description of the ‘initialize-with’ attribute in the ‘Name’ section.On Feb 24, 2011 5:56 PM, “Frank Bennett” <@Frank_Bennett> wrote:
On Fri, Feb 25, 2011 at 7:42 AM, Sylvester Keil <@Sylvester_Keil> wrote:

On Feb 24, 2011, at 11:30 PM, Frank Bennett wrote:

On Fri, Feb 25, 2011 at 6:51 AM, Sylvester Keil <@Sylvester_Keil> wrote:

Just wondering.

This does look like a case where an amendment to the specification
would be appropriate.

This covers an edge case; if Banksy were entered as a family name, the
citeproc-js processor would treat it as an institution name. In that
case, leading personal names are treated as affiliated with the
institution, so you would get H. Smith, Banksy, instead of H. Smith &
Banksy.

The institution tests themselves are not in the standard repository,
but if this behavior is reserved it will avoid a conflict down the
line, if that extension to CSL is eventually added to the
specification.

Frank

(I’ll also be pushing a bunch of tests and amendments that have piled
up locally.)

Great! Will you push these to the mercurial repository?

Already there. It’s quite a bundle, sorry; I’d fallen behind.

Thanks

Sylvester


Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT
data

generated by your applications, servers and devices whether physical,
virtual

or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev


xbiblio-devel mailing list
xbiblio-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel


Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT
data
generated by your applications, servers and devices whether physical,
virtual

But isn’t this a case that’s unresolved?

It’s not in the specification, so it’s certainly not settled. The test
could be moved out of the standard suite, and the specification left
open on this item.

But isn’t this a case that’s unresolved?

It’s not in the specification, so it’s certainly not settled. The test
could be moved out of the standard suite, and the specification left
open on this item.

It occurs to me that perhaps we ought to have a category of tests
labelled “experimental” which are understood as proposed solutions to
problems not yet addressed in the spec?

But isn’t this a case that’s unresolved?

It’s not in the specification, so it’s certainly not settled. The test
could be moved out of the standard suite, and the specification left
open on this item.

It occurs to me that perhaps we ought to have a category of tests
labelled “experimental” which are understood as proposed solutions to
problems not yet addressed in the spec?

I like that idea. How might they best be classified? They could be
divided up by proposal, or by processor (assuming that proposals will
be run on at least one system before adoption) and then proposal.

Frank Bennett <@Frank_Bennett> writes:

(I’ll also be pushing a bunch of tests and amendments that have piled
up locally.)

In date_LocalizedDateFormats-kh-KH.txt the default-locale attribute
changed from kh-KH to km-Kh, but there is not a km-KH locale file. Am I
missing something?–
andrea rossato

Frank Bennett <@Frank_Bennett> writes:

(I’ll also be pushing a bunch of tests and amendments that have piled
up locally.)

In date_LocalizedDateFormats-kh-KH.txt the default-locale attribute
changed from kh-KH to km-Kh, but there is not a km-KH locale file. Am I
missing something?

I forgot to push the change. It’s up now.

Frank

Not exactly sure, since I haven’t used the test suite. But a reference
to the schema issue tracker item would be good.

Bruce

But isn’t this a case that’s unresolved?

It’s not in the specification, so it’s certainly not settled. The test
could be moved out of the standard suite, and the specification left
open on this item.

It occurs to me that perhaps we ought to have a category of tests
labelled “experimental” which are understood as proposed solutions to
problems not yet addressed in the spec?

I like that idea. How might they best be classified? They could be
divided up by proposal, or by processor (assuming that proposals will
be run on at least one system before adoption) and then proposal.

Not exactly sure, since I haven’t used the test suite. But a reference
to the schema issue tracker item would be good.

Here’s the one on institutions:

I’ll put up a ticket on the lone given name issue soon.

Frank

Maybe this directory structure would work?:

processor-tests / csl-1.0 /
processor-tests / csl-1.0 / extensions / citeproc-js /
processor-tests / csl-1.0 / extensions / citeproc-hs /
processor-tests / csl-1.0.1 /
processor-tests / csl-1.1 /
processor-tests / proposals /

So we first group tests by CSL version, with a “proposals” folder for
proposed new CSL features. The versioned folders will contain the “core” CSL
tests, as well as the test for processor-specific extensions.

Rintze