plk

I'm keen on the idea of using n2t's meta-resolving service which seems to be able to resolve most "eprint" services (see #1183 ) and I would agree that `@article` is...

Since we have default driver-level maps distributed with biblatex, we should use them. I agree with @moewew that the semantics derived from typical interpretation of field names matter to the...

Just to add to the semantic argument. The goal of latex markup is to be semantic and so I tend to prefer semantic classification in entrytypes too. I really don't...

I would like to deprecate anything that is really a state of publication or a location of publication rather than an entrytype. So, `@unpublished` would be deprecated and `@article` would...

I would recommend using `pubstate` since it's a supported field for many types, including `@article`. This already supports a variety of localised strings for the state and it would be...

I quite like the idea of relaxing the requirement of `journaltitle` for article - that would solve a lot of problems.

This is really difficult - the refsection number is part of almost every internal variable - just search for `c@refsection` in `biblatex.sty` and to be safe, every variable containing this...

However, I do wonder if you might try saving the refsection number of the postnote definition with the postnote and then doing: ``` \c@refsection#1\relax ``` Before anything else, where the...

@moewew - N2T seems to be the main "meta-resolver" and seems rather useful. For example, it resolves DOIs, I just tried: https://n2t.net/DOI:/10.17605/OSF.IO/9P7CB which works fine PubMED IDs: https://n2t.net/PMID:/36890230 ISSNs and...

Is there any consensus that `biblatex-software` covers the CFF requirements? If so, I would suggest to close this. I don't think we are going to merge styles into the core...