13

There are a few fairly wide-spread extensions to the set of "standard" BibTeX entry types and fields: @webpage is fairly common, I think, and url and eprint are fairly common fields. In some cases (eg, url) it is obvious what should be in the field; in others (eg, eprint) there's more than one natural convention for what the value should be.

I maintain the urlbst package, and have contributed to the maintenance of a couple of other .bst styles, so I've a fairly clear interest in consistency, here.

I suspect that the answer is "no" (I can't find one now, and I've never in the last couple of decades become aware of such a thing), and to that end I've called for some consensus-building, but if such a repository or effort already exists, I'd rather join in rather than create something anew.

  • I don't think that such a repository exists. If it does, no one knows about it which would make it rather useless. But don't we already have a more or less accepted standard for extensions in the form of biblatex? I see that you mention biblatex on the linked page, and just to make myself clear: I don't suggest that you must switch to biblatex, but since it is used widely it makes sense to stick to the fields it has introduced. – Simifilm Mar 5 '19 at 8:56
  • A local mapping step of the more commonly-occurring relevant ones just before your splicing step, plus a default catch-all, would be a long-term solution. Because the spec is open-ended (I've had to define new entry types and new fields, as well as parent-child inheritances, e.g., for legal materials, and for popular media, to get down to the relevant level of granularity to be useful), a master list will never be finished. But a gatekeeper function at your end, as to relevance and applicability of and for incoming material, will work, in a practical sense (and even be a de-facto standard). – Cicada Jan 19 at 9:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.