-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define how to express "anonymous" and "et al" as names #34
Comments
|
Why the need for explicit "anonymous" support? E.g. what's wrong with the On "et al" I'm reluctant to support this without clearly demonstrated need;
|
The cases I see for et al. are (1) that of reused citations-- it is possible
|
The previous post is mine.
|
The first case isn't really our problem in my view (if people want their The second could be an issue, but I've never seen it myself. Can you post a
|
Re the second case, one could use a name suffix as a workaround. I've made a
|
Taking stock on this ticket, the call for real-world examples where explicit "Anonymous" is required hasn't been answered, and we have coverage of explicit "et al." in one of the implementations. The supporting tests are here (for long-form names) and here (for short-form names). Without a concrete use case, the potential issue of explicit Anonymous can be dropped, at least for the present. For explicit et al, the only question seems to be whether the behavior illustrated in the tests should be adopted as an expectation of CSL processors or not. If it is adopted, the tests can stay where they are (in the standard test suite), with supporting language in the specification. If it is not, the tests should be removed from the standard test set. If anyone has an objection to amending the spec to include this behavior, I'll move the tests out and we can close this ticket. Otherwise, we can close this ticket and open one against the specification. I don't have an opinion either way; if there is a single veto, I'm happy to pull the tests. |
I agree; we still have yet to have the "clearly demonstrated need" I asked about (e.g. practical examples of where CSL can't now support particular output expectations). The most common anonymous case I'm aware of just has the author listed as "Anonymous" and can be deduced by the lack of any listed contributor. I'm not fond of treating the "et al" string as a component of the family name for the first author in that test; doing so effectively blesses a particular, non-ideal, solution. I'd urge just dropping this for now. |
Just to think of how we might deal with this if we wanted to, I'd suggest two reserved names, that might be deployed like this in a legacy format like RIS:
... and:
... but that's a bit ugly, and opens up the can-o-worms I mentioned above (like why use english traditions for the reserved words; even if they're latin). |
Hi! I'm reviving this issue. I have a use-case where I parse citations and use CSL-JSON to format the parsed citations. A non-trivial number of the citations I encounter contain "et al." In many of these cases, because my team and I are working at scale, it is time consuming and/or not possible to find the complete author list. The current workaround we have been using is to append "et al." as the last author literal. However, I don't like this workaround because it is not the most correct. Technically speaking. we are encoding the last author to include et al. It would be more correct to have a specific tag for et al in these instances. Is there interest in adding an "et al." tag to the formal spec? I would be happy to work on this. |
I really don't understand why "et al" would ever be entered in item data--that should be handled by the citation style, not the item data; the data should include all of the authors. |
I think they're dealing with data that does not include all author names,
and they want to indicate that?
|
In general my response is to get better data. Beyond that, this would be covered by #240, and "et al" could be specified by entered |
Beside normal names (either literal or build of given, familiy etc.) there are two special cases:
In combination with normal names you can have the following cases
Alice and Bob.
Alice, Bob et al.
anonymous.
anonymous et al.
Alice, Bob, and anonymous
Alice, Bob, anonymous et al. (maybe)
It is not clearly defined how to express this in CSL data input format.
Existing CSL styles typically test whether a name variable is empty. If it is, the "anonymous" term can be used. Here is a guess how to express the cases above (question marks = unclear):
"author" : [ {"given":"Alice"}, {"given":"Bob"} ]
"author" : [ {"given":"Alice"}, {"given":"Bob"}, ??? ]
"author" : [ ] or "author" : [ { } ] or no author field at al ???
"author" : [ ??? ]
"author" : [ {"given":"Alice"}, {"given":"Bob"}, { } ] ???
"author" : [ {"given":"Alice"}, {"given":"Bob"}, ??? ]
The "et al" case could be be solved by a specific type of name, but this needs to be discussed:
The text was updated successfully, but these errors were encountered: