plk
Produce the XML files needed for upload to CrossRef.org
In the beginning (some 20 years ago) the XML files for CrossRef data upload were produced by a series of sed+awk+perl scripts on recipes that got passed around. About 10 years ago Boris Veytsman, placed this under a more solid framework with the script ltx2crossrefxml.pl... But alas it works with bbl produced by bibtex, but not with the ones produced by biber.
A lot of people are building kludges on their workflows by creating dummy tex files that can produce the XML with the help of Boris suite, but this is way less than optimal. Biber would be able to produce much better quality XML files because the bbl contains detailed information about each entry.
It also would help make biblatex more palatable to publishers.
This would be a lot of work as it would need to be customisable by the user too. How widely used is this format?
Tell me what is the plan you have in mind. The way I thought this would be possible was to write a "style" that would then proceed to produce a simpler BBL file that could be further processed for the final CrossRef XML. The XML required by CrossRef is much simpler (in information) than a normal Biblatex BBL file, which contains much more information.
I also would expect that there would be no need for customization. Tell us what you are thinking of....
CrossRef is a unique agency for everybody. You can deposit the XML files with several agencies around the world and they all make their way to CrossRef servers. The forma is the same for every publisher around the world that makes a CrossRef deposit, which these days, is everyone ...
On Wed, Dec 18, 2024 at 10:12 AM plk @.***> wrote:
This would be a lot of work as it would need to be customisable by the user too. How widely used is this format?
— Reply to this email directly, view it on GitHub https://github.com/plk/biblatex/issues/1399#issuecomment-2551974971, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAR7WYU2SGMXOSCQUTQQZJL2GG3ITAVCNFSM6AAAAABSICYA7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJRHE3TIOJXGE . You are receiving this because you authored the thread.Message ID: @.***>
Wel it would be possible to have a new output format from biber as we did with biblatexml or the deprecated bblxml. Crossref it seems is more like bibtex semantics than bbl semantics (that is, data, not formatting). It would basically need customisability as the data mode in biber is customisable so users would need to be able to map bibtex/biber data fields to the Crossref schema in an extensible manner.
Thanks! I understand a lot better now. This would be really great because it is one of the steps that prevent publishers from adopting biblatex more widely.
On Thu, Dec 19, 2024 at 11:15 AM plk @.***> wrote:
Wel it would be possible to have a new output format from biber as we did with biblatexml or the deprecated bblxml. Crossref it seems is more like bibtex semantics than bbl semantics (that is, data, not formatting). It would basically need customisability as the data mode in biber is customisable so users would need to be able to map bibtex/biber data fields to the Crossref schema in an extensible manner.
— Reply to this email directly, view it on GitHub https://github.com/plk/biblatex/issues/1399#issuecomment-2555593714, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAR7WYTIVOUCSPUVNDRPJ4L2GMLN3AVCNFSM6AAAAABSICYA7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJVGU4TGNZRGQ . You are receiving this because you authored the thread.Message ID: @.***>