Challenges and Opportunities for NSLP in Scientific Publishing – A Case Study

Thomas Kleinbauer, Michael Didas, Michael Wagner


Abstract
Research software is not always meant to reach production-grade quality. The same requirements, for instance, regarding performance, security, or reliability that are imposed on professional software do not necessarily apply in the lab. However, recent years have seen an increased interest to bring cutting-edge research results into production. Specialized natural language processing, such as NSLP, is no exception. In this paper, we discuss three real-life challenges in scientific publishing as they relate to NSLP, and also highlight the potential NSLP has to offer in overcoming these challenges. Specifically, we identify issues related to the elicitation of metadata – particularly with respect to what we term the /metadata externality problem –, privacy and data protection laws, and software reliability. This is not a research paper; rather than introducing novel research results, our intention is to contribute to the academic discourse in the NSLP community by providing the perspective of a potential end-user.
Anthology ID:
2026.nslp-1.5
Volume:
Proceedings of Natural Scientific Language Processing (NSLP) @ LREC 2026
Month:
May
Year:
2026
Address:
Palma, Mallorca (Spain)
Editors:
Georg Rehm, Stefan Dietze, Danilo Dessi, Diana Maynard, Sonja Schimmler
Venues:
NSLP | WS
SIG:
Publisher:
ELRA Language Resources Association (ELRA)
Note:
Pages:
44–48
Language:
External URL:
https://lrec.elra.info/lrec2026-ws-nslp-05
DOI:
10.63317/2mao8u4u3jbv
Bibkey:
Cite (ACL):
Thomas Kleinbauer, Michael Didas, and Michael Wagner. 2026. Challenges and Opportunities for NSLP in Scientific Publishing – A Case Study. In Proceedings of Natural Scientific Language Processing (NSLP) @ LREC 2026, pages 44–48, Palma, Mallorca (Spain). ELRA Language Resources Association (ELRA).
Cite (Informal):
Challenges and Opportunities for NSLP in Scientific Publishing – A Case Study (Kleinbauer et al., NSLP 2026)
Copy Citation: