The inaugural European Small Mammal Conservation Conference (SMCC 2026) took place in Sofia, Bulgaria, from 21 to 25 September 2026, bringing together researchers, conservationists and practitioners from across Europe and beyond to address gaps in small mammal research and monitoring.
\n\n\nOrganised jointly by the Habitat Foundation, the Institute of Biodiversity and Ecosystem Research at the Bulgarian Academy of Sciences, the Dutch Mammal Society and Mammal Conservation Europe, with support from the Faculty of Biology at Sofia University, the conference formed part of the Life for Falcons project, funded by the EU LIFE Programme.
\n\n\n\nThis year’s conference was held jointly with the 33rd Hamster Working Group and the VIII European Ground Squirrel Meeting, making hamsters and sousliks the primary focus, alongside broader topics including renewable energy development, agricultural impacts, reintroductions, predator\u2013prey interactions and innovative methodologies in small mammal research.
\n\n\n\nWe were delighted to participate in SMCC 2026 with an exhibition booth, showcasing the breadth of publishing services we offer to the biodiversity and conservation community. It was a pleasure to present our portfolio of journals dedicated to advancing research across ecology, biodiversity and conservation.
\n\n\n\n\n\n\n\nWe were particularly proud to present the following journals:
\n\n\n\nMeeting delegates from across the small mammal research community was tremendously rewarding, and we thoroughly enjoyed discussing how our journals can support and amplify their work.
\n\n\n\nBeyond our academic offerings, we were particularly excited to showcase beautiful art prints illustrated by our in-house scientific illustrator, Denitsa Peneva. The collection featured stunning depictions of otters, olinguitos and hamsters.
\n\n\n\n![\"\"](\"https://i0.wp.com/blog.pensoft.net/wp-content/uploads/2026/09/IMG_6783-scaled.jpg?ssl=1\")
The scientific programme was exceptional, and we were privileged to attend many outstanding presentations that demonstrated the importance of innovative monitoring approaches and conservation action.
\n\n\n\nLessons from Citizen Science for Small Mammal Conservation Monitoring in Great Britain
\n\n\n\nWe were delighted to attend a talk by Matt Larsen-Daw, Chief Executive of the Mammal Society (UK), which presented a portfolio of citizen science programmes designed to address distribution knowledge and population monitoring across Great Britain. The programmes, united by the Mammal Mapper smartphone app, included the National Harvest Mouse Survey, the Searching for Shrews initiative, and the University Mammal Challenge.
\n\n\n\nThe presentation highlighted the value of standardised effort data, the differing trade-offs between structured and opportunistic recording, and the potential for these approaches to be applied across European contexts.
\n\n\n\n![\"\"](\"https://i0.wp.com/blog.pensoft.net/wp-content/uploads/2026/09/IMG_6718-scaled.jpg?ssl=1\")
Strong Decline of Hamster Populations in Bulgaria
\n\n\n\nWe were equally impressed by Nedko Nedyalkov’s presentation documenting the significant decline in distribution and abundance of both the common hamster (Cricetus cricetus) and the Romanian hamster (Mesocricetus newtoni) across Bulgaria. The research revealed that population reductions, detected through owl pellet analysis and trapping methods, likely began in the 1950s with agricultural intensification and continue today.
\n\n\n\nGiven that both species are strictly protected under the EU Habitats Directive yet lack active conservation projects, the presentation substantiated the urgent need for targeted conservation measures. We are also pleased to note that Nedko serves as a subject editor for two of our open-access journals, ZooKeys and the Biodiversity Data Journal.
\n\n\n\n![\"\"](\"https://i0.wp.com/blog.pensoft.net/wp-content/uploads/2026/09/IMG_6757-1-scaled.jpg?ssl=1\")
Reintroduced Saker Falcons and Their Dependence on European Ground Squirrels
\n\n\n\nYana Andonova's presentation on the diet of Bulgaria’s reintroduced saker falcon population provided compelling evidence of the breeding birds' overwhelming dependence on the European ground squirrel (Spermophilus citellus) as a primary food source.
\n\n\n\nThrough food-remain analysis, visual observations and camera-trap monitoring, the research documented that ground squirrels comprised over 80 per cent of identified prey items, with small rodents accounting for 89 per cent overall! It is also worth mentioning that Andonova is an author in our open-access Biodiversity Data Journal.
\n\n\n\n![\"\"](\"https://i0.wp.com/blog.pensoft.net/wp-content/uploads/2026/09/IMG_6793-1-scaled.jpg?ssl=1\")
Attending SMCC 2026 was a genuine pleasure and particularly meaningful given that the conference took place in Sofia, the city in which our company is based. Connecting with researchers and conservationists working at the forefront of small mammal conservation, and sharing our commitment to advancing biodiversity research through open-access publishing, reinforced our dedication to supporting this important field.
\n\n\n\nWe look very much forward to engaging with this community again at future events!
\n\n\n\nFollow us on Bluesky, Facebook, X, and LinkedIn for future conference updates.
\n\n","doi":"https://doi.org/10.59350/hmn14-8zj12","guid":"https://blog.pensoft.net/?p=20924","image":"https://blog.pensoft.net/wp-content/uploads/2026/09/SciComm-PR-2026-Instagram-2026-09-23T165239.066.png","language":"en","license":"https://creativecommons.org/licenses/by/4.0/legalcode","published_at":1790294400,"rid":"n5rb6-tqh12","summary":"Tweet The inaugural European Small Mammal Conservation Conference (SMCC 2026) took place in Sofia, Bulgaria, from 21 to 25 September 2026, bringing together researchers, conservationists and practitioners from across Europe and beyond to address gaps in small mammal research and monitoring.","tags":["Biodiversity Data Journal","Frontiers Of Biogeography","Individual-based Ecology","Nature Conservation","One Ecosystem"],"title":"Pensoft at the European Small Mammal Conservation Conference 2026","updated_at":1790337914,"url":"https://blog.pensoft.net/2026/09/25/pensoft-at-the-european-small-mammal-conservation-conference-2026/","version":"v1"}},{"document":{"authors":[{"contributor_roles":[],"family":"Franziska Altemeier","given":"Nina D\u00fcvel"}],"blog":{"authors":null,"community_id":"db0d8909-9e37-46d0-b16c-0551f575e86b","created":1749772800,"current_feed_url":null,"description":"Das Blog der TIB \u2013 Leibniz-Informationszentrum Technik und Naturwissenschaften und Universit\u00e4tsbibliothek","doi":"https://doi.org/10.65527/tib","favicon":"https://rogue-scholar.org/api/communities/db0d8909-9e37-46d0-b16c-0551f575e86b/logo","feed_format":"application/atom+xml","feed_url":"https://blog.tib.eu/feed/atom/","filter":null,"generator":"WordPress","home_page_url":"https://blog.tib.eu/","issn":null,"language":"deu","license":"https://creativecommons.org/licenses/by/4.0/legalcode","prefix":"10.65527","relative_url":null,"secure":true,"slug":"tib","status":"active","subfield":"1802","title":"TIB-Blog","updated":1790331374,"use_api":true},"blog_name":"TIB-Blog","blog_slug":"tib","content_html":"![\"Gruppenfoto](\"https://blog.tib.eu/wp-content/uploads/2026/09/SERIOUS-3D-in-Art-and-Architectural-History_hoch-728x1024.jpg\")
Am 21. und 22. September 2026 fand an der Bibliotheca Hertziana \u2013 Max-Planck-Institut f\u00fcr Kunstgeschichte in Rom das Kick-off-Meeting des DFG/AHRC-gef\u00f6rderten Forschungsprojekts \"SERIOUS 3D in Art and Architectural History\" statt.
\nWissenschaftlerinnen und Wissenschaftler aus den Bereichen Kunst- und Architekturgeschichte (AAH), 3D Engineering (ENG) und Data Science in Cultural Heritage (DSC) diskutierten \u00fcber Forschungsziele, technische Anforderungen, methodische Herausforderungen und anstehende Arbeiten des gemeinsamen Projekts.
\nDas interdisziplin\u00e4re Projekt bringt Expertise aus der Bibliotheca Hertziana, der Hochschule Mainz, der TIB \u2013 Leibniz-Informationszentrum Technik und Naturwissenschaften in Hannover sowie den Universit\u00e4ten Cambridge und Exeter zusammen.
\nIm Mittelpunkt steht die Frage, wie historische R\u00e4ume mithilfe digitaler Technologien rekonstruiert, interpretiert und vermittelt werden k\u00f6nnen.
\nEin zentrales Thema des Kick-off-Meetings war die praktische Umsetzung der Verbindung kunsthistorischer Forschungsfragen mit digitalen 3D-Modellen als Teil strukturierter Forschungsdaten.
\nHistorische Rekonstruktionen beruhen auf unterschiedlichen Quellen, wissenschaftlichen Interpretationen und mitunter unvollst\u00e4ndigen Informationen; nicht alle Informationen lassen sich ohne Weiteres in ein digitales Geb\u00e4udemodell \u00fcbertragen,
\nDas Projekt untersucht deshalb auch, wie sich solche Unsicherheiten und die zugrunde liegenden Entscheidungen nachvollziehbar dokumentieren lassen.
\nDie Gruppe Data Science in Cultural Heritage (DSC), bestehend aus dem Open Science Lab der TIB und dem DH Lab der Bibliotheca Hertziana, befasst sich unter anderem damit, wie sich diese Informationen in einer gemeinsamen technischen Infrastruktur zusammenf\u00fchren lassen.
\nEin Baustein ist das im Open Science Lab entwickelte 3D-Viewer- und Annotationswerkzeug Semantic Kompakkt f\u00fcr interoperable und nachnutzbare Forschungsdaten, das mit Wikibase4Research ein Backend f\u00fcr die semantischen Informationen beinhaltet.
\nIm Projekt Herrenh\u00e4user des Ostseeraums wird Semantic Kompakkt bereits f\u00fcr einen vergleichbaren architekturhistorischen Anwendungsfall eingesetzt und entsprechend der Bedarfe einer architekturhistorischen wissenschaftlichen Community weiterentwickelt, unter anderem die Visualisierung von Punktwolken und den historischen oder \u00f6rtlichen Zusammenh\u00e4ngen.
\nBereits eine Woche vor dem Kick-off hatte das TIB-Team seine Arbeiten zur Integration des in Serious 3D genutzten Building Information Modeling (BIM) in Semantic Kompakkt auf der Konferenz FAIR 3D Heritage in Mainz vorgestellt. Der Beitrag \"Towards (H)BIM Integration in Semantic Kompakkt: Evaluation of Web Libraries for a Modular Import Pipeline\" lieferte konkrete Ans\u00e4tze f\u00fcr die anschlie\u00dfende Arbeit in Rom. Weitere Informationen finden sich im Konferenzprogramm der FAIR 3D Heritage.
\n![\"\"](\"https://blog.tib.eu/wp-content/uploads/2026/09/SERIOUS-3D-in-Art-and-Architectural-History_3-768x1024.jpg\")
Die Diskussionen machten deutlich, dass die Anforderungen der beteiligten Disziplinen bereits bei der kunsthistorischen Recherche und der Erstellung der ersten digitalen Geb\u00e4udemodelle ber\u00fccksichtigt werden m\u00fcssen. Dazu geh\u00f6rt insbesondere die Frage, welche Informationen sp\u00e4ter f\u00fcr die semantische Modellierung, wissenschaftliche Annotation und Visualisierung ben\u00f6tigt werden.
\nAls n\u00e4chster Schritt sollen exemplarische 3D-Modelle mit unterschiedlicher Informationstiefe seitens der ENG-Partner bereitgestellt werden. An ihnen will das DSC-Team den gesamten Workflow vom Datenimport bis zur interaktiven Darstellung erproben.
\nDie Modelle sollen historische Raumsituationen nicht nur veranschaulichen, sondern auch als Arbeitsgrundlage f\u00fcr kunsthistorische Fragestellungen der AAH-Beteiligten dienen. Daf\u00fcr m\u00fcssen Quellen und unterschiedliche Rekonstruktionshypothesen mit den modellierten Objekten verkn\u00fcpft werden k\u00f6nnen.
\nThematisiert wurde au\u00dferdem, wie sich historische R\u00e4ume durch webbasiertes Storytelling interaktiv erkunden und zugleich mit Quellen, Forschungsfragen und Erl\u00e4uterungen verbinden lassen.
\n![\"\"](\"https://blog.tib.eu/wp-content/uploads/2026/09/SERIOUS-3D-in-Art-and-Architectural-History_2-768x1024.jpg\")
In der abschlie\u00dfenden Diskussion wurde nochmals betont, dass SERIOUS 3D als gemeinsamer Forschungsprozess, und nicht nur als Zusammenarbeit voneinander getrennter Arbeitsgruppen verstanden werden soll.
\nDie unterschiedlichen fachlichen Perspektiven sollen bereits bei der Entwicklung der Forschungsfragen, der Auswahl historischer Objekte und der Erarbeitung digitaler Methoden zusammengef\u00fchrt werden.
\nIm Anschluss an das Kick-off-Meeting reist das Projektteam vom 23. bis 25. September 2026 zur Feldforschung nach Florenz. Dort werden Teile des Palazzo Medici, das zentrale Forschungsobjekt von SERIOUS 3D, mithilfe von 3D-Laserscanning und Photogrammetrie digital erfasst.
\nDie gewonnenen Daten bilden die Grundlage f\u00fcr die weitere Entwicklung des historischen Geb\u00e4udemodells und die Erprobung der in Rom diskutierten technischen Workflows.
","doi":"https://doi.org/10.65527/ehvpv-0zn69","guid":"https://blog.tib.eu/?p=33673","image":"https://blog.tib.eu/wp-content/uploads/2026/09/SERIOUS-3D-in-Art-and-Architectural-History_2_quer.jpg","language":"de","license":"https://creativecommons.org/licenses/by/4.0/legalcode","published_at":1790294400,"rid":"4b751-nmd91","summary":"Am 21. und 22. September 2026 fand an der Bibliotheca Hertziana \u2013 Max-Planck-Institut f\u00fcr Kunstgeschichte in Rom das Kick-off-Meeting des DFG/AHRC-gef\u00f6rderten Forschungsprojekts \"SERIOUS 3D in Art and Architectural History\" statt.","tags":["OPENNESS","FORSCHUNG & PROJEKTE","Lizenz:CC-BY-4.0-INT","Open Science Lab","Open Science"],"title":"SERIOUS 3D: Kunst- und Architekturgeschichte im digitalen Forschungsraum","updated_at":1790331830,"url":"https://blog.tib.eu/2026/09/25/serious-3d-kunst-und-architekturgeschichte-im-digitalen-forschungsraum/","version":"v1"}},{"document":{"authors":[{"contributor_roles":[],"family":"Eden","given":"Terence"}],"blog":{"authors":null,"community_id":"61ce553a-bafd-4aba-a952-d3bab5e85bcc","created":1788652800,"current_feed_url":null,"description":"Regular nonsense about tech and its effects \ud83d\ude43","doi":"https://doi.org/10.59350/shkspr","favicon":"https://rogue-scholar.org/api/communities/61ce553a-bafd-4aba-a952-d3bab5e85bcc/logo","feed_format":"application/atom+xml","feed_url":"https://shkspr.mobi/blog/feed/DOI","filter":"category:-1982","generator":"WordPress","home_page_url":"https://shkspr.mobi/blog","issn":"2753-1570","language":"eng","license":"https://creativecommons.org/licenses/by/4.0/legalcode","prefix":"10.59350","relative_url":null,"secure":true,"slug":"shkspr","status":"active","subfield":"1712","title":"Terence Eden's Blog","updated":1790328333,"use_api":true},"blog_name":"Terence Eden's Blog","blog_slug":"shkspr","content_html":"One of the great things about modern HTML is that it tries to standardise stuff that developers are already doing. If there are a myriad ways of, for example, loading video onto a page - then browsers and other interested parties should work out how to make a standard <video> element.
An interesting new proposal has been brought forth by Microsoft. There are a dozen ways to show a preview of an <img> element before the src= attribute has loaded. So why not standardise on previewsrc=? There's an excellent explainer on Patrick Brosset's blog.
I instinctively like the idea - if only to simplify source code and reduce JS usage. But I do have some concerns which I've shared with the team.
\n\nThis is the thing I always bang on about when I'm discussing standards. Additions to HTML should primarily benefit end users, not developers.
\n\nDo end users want this? Is there a bunch of research that shows normal people are confused that they don't see a preview image? Do they recoil in fear and distress while waiting for a full resolution picture to appear?
\n\nWhen people see a blurry or blocky image, do they understand that they need to wait for the full thing - or do they assume their computer is broken?
\n\nMicrosoft has a bazillion dollars - it can afford to spend a few thousand on interviewing some real users and mapping out what they're likely to want from this.
\n\nI begrudgingly admit that developers need love too.
\n\n\n\nWhat are the pain points of the current implementations? Is it hard to dynamically generate multiple images? Is the syntax hard to use? Do blurs slow down the page?
\n\nAgain, MS needs to pony up some cash to talk to developers. At the very least run a survey of all existing websites in the BING! database and see what they use.
\n\nWhen an image doesn't load, or loads slowly, a user will normally be shown some alt text - like this:
\n\n![\"Terence](\"http://example.test/unicorn.avif\")
\n\nIs that more or less useful than this?
\n\n![\"A](\"https://shkspr.mobi/blog/wp-content/uploads/2026/09/unicorn.webp\")
\n\nAccessibility isn't just for people with visual impairments! This is an issue I've raised with them.
\n\nI've written before about the usability of HTML elements. Some of the newer ones like <picture> have very poorly named attributes in my opinion.
One alternative for previewsrc is poster. That would match with the poster attribute on the <video> element. They both show a preview image before the main content is loaded.
Given their functionality is identical, I think it makes sense for them to have the same name. You wouldn't expect to see <video horizontal=\"1920\" vertical=\"1080\"> would you? No. That's why they use the same width and height attributes as images.
There are several interesting objections and discussions on the GitHub repo. I'm delighted that this is being talked about in the open, rather than just being presented as a fait accompli (remember the toast proposal?).
\n\nAs I said, I genuinely think that there's a useful idea in here. But after writing all of this, I think it would be better and simpler for developers to use progressive images rather than overload HTML with a new attribute.
\n\nIf website owners can't be bothered to save progressive images, I don't see why they'd bother to create a separate preview image.
\n\nKeeping preview images in sync with their full images is also likely to be a problem.
\n\nIf you think I'm wrong, read the explainer and then chat with Microsoft.
![](\"https://shkspr.mobi/blog/wp-content/themes/edent-wordpress-theme/info/okgo.php?ID=75856&HTTP_REFERER=DOI\"){kind=small}
","doi":"https://doi.org/10.59350/twr9x-eh003","guid":"https://shkspr.mobi/blog/?p=75856","image":"https://shkspr.mobi/blog/wp-content/uploads/2018/01/HTML5_Badge_512.png","language":"en","license":"https://creativecommons.org/licenses/by/4.0/legalcode","published_at":1790208000,"rid":"bke8v-4h802","summary":"One of the great things about modern HTML is that it tries to standardise stuff that developers are already doing. If there are a myriad ways of, for example, loading video onto a page - then browsers and other interested parties should work out how to make a standard element. An interesting new proposal has been brought forth by Microsoft.","tags":["/etc/","HTML","Standards"],"title":"Some thoughts on HTML's proposed previewsrc attribute","updated_at":1790328376,"url":"https://shkspr.mobi/blog/2026/09/some-thoughts-on-htmls-proposed-previewsrc-attribute/","version":"v1"}},{"document":{"authors":[{"affiliation":[{"id":"https://ror.org/02feahw73","name":"Centre National de la Recherche Scientifique"}],"contributor_roles":[],"family":"Hinsen","given":"Konrad","url":"https://orcid.org/0000-0003-0330-9428"}],"blog":{"authors":null,"community_id":"2488dc7f-4f82-4051-8490-22d2cd8d472d","created":1719792000,"current_feed_url":null,"description":null,"doi":"https://doi.org/10.59350/khinsen","favicon":"https://rogue-scholar.org/api/communities/2488dc7f-4f82-4051-8490-22d2cd8d472d/logo","feed_format":"application/atom+xml","feed_url":"https://blog.khinsen.net/feeds/all.atom.xml","filter":null,"generator":"Other","home_page_url":"https://blog.khinsen.net/","issn":null,"language":"eng","license":"https://creativecommons.org/licenses/by/4.0/legalcode","prefix":"10.59350","relative_url":null,"secure":true,"slug":"khinsen","status":"active","subfield":"1802","title":"Konrad Hinsen's blog","updated":1790294400,"use_api":null},"blog_name":"Konrad Hinsen's blog","blog_slug":"khinsen","content_html":"Knowledge refinement is the ever ongoing process in science (and beyond it) that shepherds knowledge from lab notebooks into journal articles and then on to review articles, monographs, reference handbooks, university textbooks, and finally professional domain expertise and school education for a wider public. It has been going on for a few centuries, but we hardly talk about it. In fact, I made up the term because I couldn't find an established one. Computational knowledge has not yet found its place in the knowledge refinement process. Why not? And what can we do to make it happen?
\n\nFirst of all, what is the role of knowledge refinement?
\nOne answer is that knowledge becomes more reliable in the refinement process. Any single experiment, no matter how carefully done, can turn out to be wrong for lots of reasons. In contrast, the synthesis of hundreds of independent related experiments will remain trustworthy even if one flaky input experiment has to be withdrawn.
\nAnother role of knowledge refinement is making knowledge more accessible. When we learn from others, rather than from our own experience, we start with a highly refined view of a domain, and dive into the details only later and when we see a need for it. Schools teach only refined knowledge, which thus shapes general culture.
\nFinally, with refinement, knowledge also becomes more long-lived. A useful picture here is pace layers: each refinement step pushes knowledge down into a more slowly evolving layer.
\nEach knowledge refinement step has several interrelated aspects:
\nSummarization. A large number of works from the preceding step are cooked down into a common essence that emerges from them.
Curation. Domain experts select what they see as most relevant, discarding what they consider technical details, or only of historical importance.
Integration. Each step draws on broader domain coverage than the preceding one. The relation to already established knowledge is made clearer.
Simplification and clarification. Each step is written for a wider and less specialized audience than the preceding one. Jargon is replaced by more widely understood vocabulary. New concepts are introduced and the explanation is structured around them.
All these processes require reformulation. The output of a refinement step is not simply an annotated collection of quotes from its inputs. You can't edit a journal article into a chapter for a university textbook.
\nIn the digital era, it has become widely accepted that software and electronic datasets are representations of scientific knowledge. See for example pages 9 to 11 of the UNESCO Recommendation on Open Science, which discuss \"open scientific knowledge\". For now, however, this is mostly wishful thinking. While code and data certainly are scientific information, it is difficult to consider them to be knowledge as long as they don't participate in the knowledge refinement process.
\nLet me illustrate this with analogies from pre-digital science. The predecessors of today's digital datasets are tables of observations recorded in lab notebooks. The predecessors of today's scientific software are mathematical equations. Consider the foundational research on electromagnetism that was done in the 19th century. Examples of original sources are the lab notebooks of Michael Faraday, or on the theoretical side James Clerk Maxwell's paper \"A Dynamical Theory of the Electromagneticm Field\" (already a refined version of his personal notes, which are probably lost). Today's textbooks in physics or electrical engineering mention both Faraday and Maxwell in historical overviews, but they don't ask you to consult their original work, nor do they cite passages from it in their pedagogical presentation. Instead, they show highly refined versions of Maxwell's theory in modern vector notation, which was largely created for this purpose. The textbooks also summarize the kind of experiments done by Faraday and many others, with pictures and diagrams of modern rather than historical instruments and experimental setups. Instead of real data, they show plots of idealized synthetic data for illustration.
\nWhereas nobody would seriously consider publishing a lab notebook as a journal article after just some light editing, many researchers seem to believe that computational notebooks, such as the popular Jupyter notebooks, could replace journal articles. However, the history and practice of Jupyter shows that it is by design a tool for interactive computational exploration. A Jupyter notebook is an annotated chronological record of a single computation. There is no way to summarize multiple computations. There is no way to focus on the essential aspects of a computation while relegating implementation details to an appendix. There is no way to explain, in more than words, algorithms from a library that is used in the notebook. Moreover, the order of presentation is constrained by the flow of the computation. In a typical Jupyter notebook, one of the very first lines says import matplotlib, a technical detail that in a journal article should be relegated to a reference list, because it is irrelevant to the scientific message.
If you look at today's published Jupyter notebooks, most of them are complements to journal articles. The play the role of an appendix, a repository for technical details. Notebooks that are independent publications do exist, for example in the Journal of Digital History, but the computations they contain, basic data analysis and visualization, are simple and not the main topic of the paper. Moreover, the Journal of Digital History has developed its own extensions to Jupyter that add support for hiding technical details from view while reading the article.
\nWhile I focused on Jupyter because of its popularity, other notebook technologies such as Quarto or Emacs' Babel extension to org-mode are not fundamentally different. As long as the executable content is a single computation that runs from top to bottom, the above criticisms remain valid.
\nVarious ideas for improving the publishing technology for code are being explored. One of them is removing the linear execution constraint, e.g. by using the dataflow paradigm. A few notebook systems have adopted this approach, most notably Observable. The most interesting system I have seen so far in this space is Lopecode, which adds a hypertext structure to Observable's dataflow model for computation. My own experiment on supporting the publication of refined digital knowledge is HyperDoc, which focuses on (1) integrating code and its execution into hypermedia networks and (2) building bridges to existing hypermedia systems. It has the advantage of being applicable to existing code in any programming language (though this requires significant implementation work that hasn't been done yet), and thus avoids a complete break with the past six decades of computational research.
\nMuch more remains to be done, however, before computational knowledge can become an integral part of the refinement process. Computational knowledge is most of all formalized knowledge, meaning knowledge expressed in terms of a formal system that can be processed mechanically, by a computer. Refinement techniques for formalized knowledge are constrained by the formal system they depend on. Program source code lives in a formal system defined by a programming language. It is processed mechanically by a compiler or an interpreter. The focus of a programming language is, not surprisingly, the construction of executable programs. There is a well-established refinement process for source code: scripts become library modules, which are complemented by tests and documentation and then published to become off-the-shelf ingredients for constructing more complex programs. Like knowledge refinement, code refinement makes code more reliable, more accessible, and long-lived, but only from the \"code as a tool\" perspective. It tends to reduce rather than augment its value as a knowledge repository. Software engineering priorities such as optimization and reducing redundancy tend to make the code less readable for researchers who are not professional software developers, and impenetrable to anyone who is just starting to explore a new domain of knowledge.
\nThis is why knowledge refinement in computational science remains limited to non-formal language. Textbooks remain printed books (or their digital twins, PDF files), merely referring to and writing about machine-readable artifacts such as code. The textbooks discuss concepts, including algorithms and data structures, but don't provide examples that readers could run and then build on in their own explorations. On the code side, there are often highly refined implementations for use as off-the-shelf tools, but their correspondence to what the textbooks say is unclear and not verifiable by the reader.
\nThere has been work on improving the explanation side, for example Bret Victor's explorable explanations that integrate interactive exploration tools into formerly passive textbook material. However, the strict divide between explanation and code for use in practice remains.
\nThis state of the art is tolerable for low-complexity computational knowledge, e.g. in linear algebra or signal processing. A textbook on Fourier transforms and good FFT library are good enough for learning these methods. But we need something better for complex models and methods.
\nConsider computational models of complex systems such as force fields for biomolecules, or climate models. On the machine side, they are implemented as software modules for use in simulation, using standard programming languages. On the human side, there are papers describing the principles behind their design, but lacking many details because these details would be overwhelming to a human reader. So if you really want to know how such models work, your only choice is wading through enormous amounts of source code, taking notes carefully of the findings that are relevant to your question. And if you ever want to compare two such complex models... good luck exploring two large software packages in parallel. Unfortunately, that's something you can't avoid doing during knowledge refinement. For example when you write a review paper on protein force fields, or on climate models.
\nWhen models become too complex to be represented in traditional scientific notations (equations, diagrams, etc.), they need to be represented in digital scientific notations. They need to be represented in formal systems that are made for documentation and exploration, rather than for plugging into a simulator. And they require tools that treat them as data, not code.
\nAn idea I have been pursuing for a while is the use of specification languages as digital scientific notations. See my project Leibniz for the details. Specification languages are more general than programming languages in the same way that mathematical equations are more general than mathematical functions (see here for a discussion). In particular, specification languages do not impose an executability condition on everything you write. This allows you to write incomplete function definitions or data structures. I am working on this idea and I remain optimistic that it will work out, but I won't declare victory before I have actually written that review of biomolecular force fields. Meanwhile, I'd be happy to see other work in this space, ideally pursuing very different ideas.
\nDigital scientific notations are a necessary first step for enabling the refinement of digital scientific knowledge, but the real works starts once we have them. We must then develop the tools that let researchers explore and examine publications containing formalized knowledge. We must also find refinement strategies that actually work in practice. There remains a lot to be done!
","doi":"https://doi.org/10.59350/5vb7q-rnw59","guid":"https://blog.khinsen.net/posts/2026/09/25/knowledge-refinement.html","language":"en","license":"https://creativecommons.org/licenses/by/4.0/legalcode","published_at":1790294400,"rid":"kn021-31216","summary":"Knowledge refinement is the ever ongoing process in science (and beyond it) that shepherds knowledge from lab notebooks into journal articles and then on to review articles, monographs, reference handbooks, university textbooks, and finally professional domain expertise and school education for a wider public.","title":"Knowledge refinement in the digital era","updated_at":1790328281,"url":"https://blog.khinsen.net/posts/2026/09/25/knowledge-refinement.html","version":"v1"}},{"document":{"authors":[{"contributor_roles":[],"name":"Team OA Brandenburg"}],"blog":{"authors":null,"community_id":"00dd7e11-a802-44c1-9584-5c56d1f8d417","created":1706832000,"current_feed_url":null,"description":"Vernetzungs- und Kompetenzstelle Open Access Brandenburg","doi":"https://doi.org/10.59350/oabrandenburg","favicon":"https://rogue-scholar.org/api/communities/00dd7e11-a802-44c1-9584-5c56d1f8d417/logo","feed_format":"application/atom+xml","feed_url":"https://open-access-brandenburg.de/feed/atom","filter":null,"generator":"WordPress","home_page_url":"https://open-access-brandenburg.de/","issn":null,"language":"deu","license":"https://creativecommons.org/licenses/by/4.0/legalcode","prefix":"10.59350","relative_url":null,"secure":true,"slug":"oabrandenburg","status":"active","subfield":"1802","title":"Open Access Brandenburg","updated":1790261676,"use_api":false},"blog_name":"Open Access Brandenburg","blog_slug":"oabrandenburg","content_html":"F\u00fcr die Erfolgsbewertung der Open-Access-Transformation schauen wir als Vernetzungs- und Kompetenzstelle Open Access Brandenburg erwartungsgem\u00e4\u00df mit erheblichem Interesse darauf, was an den Hochschulen des Landes an Wissenschaft nach dem Open-Access-Modell erscheint. Zugleich \u00fcberlegen wir, wie wir diesen Entwicklungen st\u00e4rker sichtbar machen. Denn tats\u00e4chlich geschieht im Land Brandenburg erstaunlich viel und Open Access an vielen Stellen erstaunlich selbstverst\u00e4ndlich.\n\nEin Ansatz, denn wir aktuell etwas ausprobieren m\u00f6chten, sind kleine Textbohrungen in das Datenmaterial. Heute haben wir daf\u00fcr exemplarisch mit OpenAlex einen Blick darauf geworfen, welches die \u2013 bislang \u2013 meistzitierten Open-Access-Publikation der Forschung mit Beteiligung von an der Europa Universit\u00e4t Viadrina affiliierten Forschenden aus dem Jahr 2025 sind. \"Bislang\" bezieht sich auf die Tatsache, dass gerade beim F\u00e4cherspektrum der Viadrina l\u00e4ngere Zeitzyklen f\u00fcr Zitationen zu ber\u00fccksichtigen sind und je thematischer Entwicklung weitere Zitationen zu erwarten sind. Eine wissenschaftliche Arbeit braucht erfahrungsgem\u00e4\u00df eine Weile, bis sie in ihrer Zielcommunity sichtbar rezipiert und von dieser f\u00fcr neue Forschung verarbeitet wird. Diese Studie konstatiert beispielsweise generell eine durchschnittliche Zitationsverz\u00f6gerung von sieben bis acht Jahren. Und f\u00fcr die Geisteswissenschaften wurde gar eine \"Ruhezeit\" von f\u00fcnf Jahren ermittelt. Zugleich wollen wir nicht allzu weit zur\u00fcckgehen, weil uns auch interessiert, welche Forschungsthemen sich aktuell in der Aufmerksamkeit aktuell. Das bedeutet aber keinesfalls, dass wir uns nicht bei Gelegenheit auch einmal einen l\u00e4ngeren Zeitraum anschauen. Und ganz sicher beleuchten wir auch unsere anderen Einrichtungen im Land Brandenburg.\u00a0\nDie nachfolgende Rangliste erfolgt auf Angaben von OpenAlex. Die Zahl der Zitationen entspricht dem Stichtag 23.09.2026. Es wurden ausschlie\u00dflich Open-Access-Publikationen ber\u00fccksichtigt.\nZitierhinweis:
\nVernetzungs- und Kompetenzstelle Open Access Brandenburg (2026): \"Brandenburger OA-Top 10: Forschung aus der Europa Universit\u00e4t Viadrina Frankfurt (Oder), 2025.\" DOI: 10.59350/mp0vb-23e71
\nZitierhinweis:
\nKaden, Ben (2026): \"OA-Takeaways: Wie l\u00e4sst sich ein teilhabeorientiertes Open Access besser gestalten?.\" DOI: 10.59350/8kxzb-3k358
\nThis post describes how I extended the work in my previous\npost that axiomatizes\nneutron numbers and nucleon numbers for isotopes that appear in ChEBI as\nchildren of atom terms, then materializes isotope (same atomic number), isotone\n(same neutron number), and isobar (same nucleon number) relationships between\nthem.
\nWhile the previous post was directly motivated by needs for the upcoming basis\nset ontology for NFDI4Chem, extending the axiomizations from partially qualified\natoms (with just atomic number) to fully qualified atoms (with both atomic and\nneutron number) was an obvious next step once I was already familiar with the\nChEBI atom hierarchy.
\nThe code and data presented in this post were added in\ncthoyt/chebi-atomic-numbers-ontology@2\nand\ncthoyt/chebi-atomic-numbers-ontology#3.
\nWhile ChEBI has full coverage through element 117 in the atoms branch, it only\nhas partial coverage of isotopes. I used the following script to produce an\ninitial ROBOT template:
\n![\"\"](\"https://i0.wp.com/blog.pensoft.net/wp-content/uploads/2026/09/IMG_6657-2-scaled.jpg?resize=840%2C662\")
![\"\"](\"https://i0.wp.com/blog.pensoft.net/wp-content/uploads/2026/09/IMG_6660-2-scaled.jpg?resize=840%2C630\")
![\"\"](\"https://i0.wp.com/blog.pensoft.net/wp-content/uploads/2026/09/IMG_6668-2-scaled.jpg?resize=840%2C1120\")
![\"\"](\"https://i0.wp.com/blog.pensoft.net/wp-content/uploads/2026/09/IMG_6670-2-scaled.jpg?resize=840%2C1120\")
import pandas as pd\nimport pyobo\n\nelements_df = pd.read_csv(\"elements.tsv\", sep=\"\\t\", skiprows=2, header=None)\nrows = []\nfor curie, _, label, number in elements_df.values:\n for child in pyobo.get_descendants(curie) or []:\n full_name = pyobo.get_name(child, strict=True)\n name = full_name.removesuffix(\"atom\").strip()\n _, _, total = name.partition(\"-\")\n if total:\n total = int(total)\n rows.append((child.curie, \"class\", name, total, total - number))\n else:\n print(f\"failed on {child.curie} - {full_name}\")\n\nisotopes_df = pd.DataFrame(rows)\nisotopes_df.to_csv(\"isotopes.tsv\", sep=\"\\t\", index=False)\nExcept the three isotopes of hydrogen, which each have their own labels, all\nisotopes' labels have the following form:
| curie | \ntype | \nlabel | \nnucleon number | \nneutron number | \n
|---|---|---|---|---|
| ID | \nTYPE | \n\u00a0 | \nSC 'ChEMROF:nucleon_number' value % | \nSC 'ChEMROF:neutron_number' value % | \n
| CHEBI:29236 | \nclass | \nprotium atom | \n1 | \n0 | \n
| CHEBI:29237 | \nclass | \ndeuterium atom | \n2 | \n1 | \n
| CHEBI:29238 | \nclass | \ntritium atom | \n3 | \n2 | \n
| CHEBI:30218 | \nclass | \nhelium-3 | \n3 | \n1 | \n
| CHEBI:37004 | \nclass | \nhelium-8 | \n8 | \n6 | \n
| CHEBI:30219 | \nclass | \nhelium-4 | \n4 | \n2 | \n
| CHEBI:37003 | \nclass | \nhelium-6 | \n6 | \n4 | \n
This template works the same way I described in the previous post, now using two columns for data value\nconstraints instead of just a single column. Note, the links are added here for\nconvenience, and don't/shouldn't actually appear in ROBOT templates.
\nInterestingly, a related\ndiscussion\nwill be taking place at the\nOntologies4Chem Workshop 2026.\nI would like to add the missing isotopes to ChEBI, but this will probably take a\nwhile!
\nI had high hopes that formalizing the atomic number, nucleon number, and neutron\nnumber would allow for me to encode inference rules to cover what it means for\ntwo fully qualified atoms to be isotopes, isobars, or isotones of each other,\nfor example, using\nSemantic Web Rule Language (SWRL). However,\nI had a pretty typical experience that the OWL and semantic web technologies\ndon't directly support this (IMO) rather obvious use case.
\nInstead, I opted to write several SPARQL queries that can be used with\nrobot query to manipulate OWL as\nRDF and add in new object property constraints directly with a command like:
$ robot query \\\n --update src/isobar-construct.ru \\\n --update src/isotone-construct.ru \\\n --update src/isotope-construct.ru\nSee the full incorporation into the build in the repository's\njustfile.
\nIsotopes are atoms of the same element\nwith different number of neutrons. They can be produced, e.g., through the\nprocess of neutron capture. For\nexample, thallium-199 (CHEBI:37805),\nthallium-201 (CHEBI:37804),\nthallium-203 (CHEBI:37802), and\nthallium-205 (CHEBI:37803) are isotopes of\nthallium.
\nThe following SPARQL materializes isotope relationships between atoms using the\nChEMROF:isotope_of relationship.
\nINSERT {\n ?x rdfs:subClassOf [\n owl:onProperty ChEMROF:isotope_of;\n owl:someValuesFrom ?y\n ] .\n}\nWHERE {\n ?atom rdfs:subClassOf [\n owl:onProperty ChEMROF:atomic_number;\n owl:hasValue ?atomic_number\n ] ;\n ?x rdfs:subClassOf ?atom .\n ?y rdfs:subClassOf ?atom .\n FILTER(?x != ?y)\n}\nIsotones are atoms of different\nelements with the same number of neutrons. They can be produced, e.g., through\nthe process of proton capture.\nFor example, nitrogen-17 (CHEBI:36937)\noxygen-18 (CHEBI:33815), and\nfluorine-19 (CHEBI:36940) each have 10\nneutrons.
\nThe following SPARQL materializes isotone relationships between atoms using the\nChEMROF:isotone_of relationship.
\nINSERT {\n ?x rdfs:subClassOf [\n owl:onProperty ChEMROF:isotone_of;\n owl:someValuesFrom ?y\n ] .\n}\nWHERE {\n ?x rdfs:subClassOf [\n owl:onProperty ChEMROF:neutron_number;\n owl:hasValue ?value\n ] .\n ?y rdfs:subClassOf [\n owl:onProperty ChEMROF:neutron_number;\n owl:hasValue ?value\n ] .\n FILTER(?x != ?y)\n}\nIsobars are atoms of\ndifferent elements with the same number of nucleons. They can be produced, e.g.,\nthrough the process of beta decay.\nFor example, nitrogen-15 (CHEBI:36934) and\noxygen-15 (CHEBI:36932) are isobars with\nthe same nucleon number of 15.
\nThe following SPARQL materializes isobar relationships between atoms using the\nChEMROF:nucleon_number\nrelationship.
\nINSERT {\n ?x rdfs:subClassOf [\n owl:onProperty ChEMROF:isobar_of;\n owl:someValuesFrom ?y\n ] .\n}\nWHERE {\n ?x rdfs:subClassOf [\n owl:onProperty ChEMROF:nucleon_number;\n owl:hasValue ?value\n ] .\n ?y rdfs:subClassOf [\n owl:onProperty ChEMROF:nucleon_number;\n owl:hasValue ?value\n ] .\n FILTER(?x != ?y)\n}\nWhile I exhausted the current ChEMROF predicates, there still remain a few that\nI found while reading up on Wikipedia:
\nIsodiaphers are atoms\nwith equal neutron excess (i.e., neutron number minus atomic number). They can\nbe produced, e.g., through the process of\nalpha decay. For example,\ncarbon-13 (CHEBI:36928),\nnitrogen-15 (CHEBI:36934), and\noxygen-17 (CHEBI:33819) are isodiaphers\nwith a neutron excess of 1. I made a\npull request to ChEMROF to add this\nrelationship - after some discussion, I might also include an additional SPARQL\nquery.
\nMirror nuclei are atoms whose\nneutron numbers and atomic numbers are swapped. They can be produced, e.g.,\nthrough the process of\npositron emission. For\nexample, tritium (CHEBI:29238) and\nhelium-3 (CHEBI:30218) are mirror nuclei.
","doi":"https://doi.org/10.59350/8sztc-csq48","guid":"https://cthoyt.com/2026/09/24/chebi-nuclides","language":"en","license":"https://creativecommons.org/licenses/by/4.0/legalcode","published_at":1790208000,"rid":"ts8h5-vpr83","summary":"This post describes how I extended the work in my previous post that axiomatizes neutron numbers and nucleon numbers for isotopes that appear in ChEBI as children of atom terms, then materializes isotope (same atomic number), isotone (same neutron number), and isobar (same nucleon number) relationships between them.","tags":["ChEBI","Chemistry","Ontology","Biocuration"],"title":"Axiomatizing Nuclides in ChEBI","updated_at":1790321407,"url":"https://cthoyt.com/2026/09/24/chebi-nuclides.html","version":"v1"}},{"document":{"authors":[{"contributor_roles":[],"family":"Singson","given":"Lea"}],"blog":{"authors":[{"name":"Redaktion iRights.info"}],"community_id":"7d3b25fd-a4a8-4155-8e76-99d6be06706a","created":1694736000,"current_feed_url":null,"description":"Urheberrecht und kreatives Schaffen in der digitalen Welt","doi":"https://doi.org/10.59350/irights","favicon":"https://rogue-scholar.org/api/communities/7d3b25fd-a4a8-4155-8e76-99d6be06706a/logo","feed_format":"application/atom+xml","feed_url":"https://irights.info/feed/atom","filter":null,"generator":"Other","home_page_url":"https://irights.info/","issn":null,"language":"deu","license":"https://creativecommons.org/licenses/by/4.0/legalcode","prefix":"10.59350","relative_url":null,"secure":true,"slug":"irights","status":"active","subfield":"3308","title":"iRights.info","updated":1790255863,"use_api":false},"blog_name":"iRights.info","blog_slug":"irights","content_html":"Wie lizenziert man OERs, wenn diese aus so genanntem \"gemischtem Material\" mit KI-Anteil bestehen? Und wann haben solche Inhalte urheberrechtliche Relevanz? Mehr dazu hier:
\n\n
K\u00fcnstliche Intelligenz unterst\u00fctzt Schaffende auch bei der Erstellung von OERs in variablem Umfang. H\u00e4ufig entstehen dabei so genannte \"gemischte Materialien\". Damit gemeint sind Materialien, die entweder aus einer Zusammenstellung von KI-generierten und pers\u00f6nlich erstellten Elementen bestehen oder aus einem Inhalt, f\u00fcr dessen Erstellung KI und Mensch zusammenwirken. Je nachdem, wie das gemischte Material beschaffen ist, gibt es dabei in Bezug auf die Lizenzierbarkeit und die Kennzeichnung des KI-Dienstes verschiedene Aspekte zu beachten.
\nBei gemischten Materialien ist zwischen Inhalten mit trennbaren Elementen und Inhalten mit einem Hauptelement mit zwei Erstellungsmethoden zu unterscheiden:
\nVerfasst eine Autorin f\u00fcr einen Online-Artikel beispielsweise einen Text und f\u00fcgt diesem ein KI-generiertes Titelbild hinzu, handelt es sich bei der Kombination aus Text und Bild um ein gemischtes Material, wobei das Bild und der Text dabei zwei voneinander trennbare Elemente sind.
\nL\u00e4sst die Autorin den Text selbst teilweise mit KI erstellen und verfasst ihn teilweise selbst, liegt mit dem Text ein Hauptelement mit zwei Erstellungsmethoden vor.
\nDa ein urheberrechtlicher Schutz \u2013 und damit auch eine Lizenzierung mit CC BY \u2013 eine pers\u00f6nliche geistige Sch\u00f6pfung voraussetzt, sind KI-generierte Materialien mangels menschlicher Sch\u00f6pfung nicht schutz- und lizenzierf\u00e4hig. KI-Output ist damit von sich aus gemeinfrei bzw. \"open\".
\nPrompt versus pers\u00f6nliche geistige Sch\u00f6pfung
\nKI-Outputs werden durch das Eingeben eines Befehls, eines so genannten Prompts, erzeugt. Eine pers\u00f6nliche geistige Sch\u00f6pfung setzt voraus, dass eine Person ein Werk durch eigene kreative, individuelle Entscheidungen formt. Da ein Prompt als Steuerung eines technischen Systems zu verstehen und rein anweisend ist, erf\u00fcllt er nicht die Voraussetzung einer pers\u00f6nlichen geistigen Sch\u00f6pfung.
\nIn der Praxis wird der Output nach dem Prompt h\u00e4ufig noch verfeinert. In so einem Fall kann es urheberrechtlichen Schutzf\u00e4higkeit des Prompts kommen, wenn der kreative Beitrag der Erstellerin st\u00e4rker hervortritt, als die KI-generierten Inhalte. Mehr dazu hier.
\nHier gilt Unterschiedliches, je nachdem, ob es sich um Inhalte mit trennbaren oder untrennbaren Elementen handelt.
\n1. Inhalte mit trennbaren Elementen
\nDa die KI-generierten Inhalte naturgem\u00e4\u00df gemeinfrei sind, sollten diese mit einem Public Domain Mark versehen werden. Die selbst erstellten, urheberrechtlich gesch\u00fctzten Inhalte k\u00f6nnen lizenziert werden. Damit der Inhalt als OER genutzt werden kann, empfiehlt sich die Lizenzierung mit der CC BY 4.0-Lizenz. Soll das gemischte Material einheitlich lizenziert werden, empfiehlt sich die CC0-Lizenz. Da diese Lizenz die lizenzierten Inhalte in die Gemeinfreiheit entl\u00e4sst, eignet sie sich auch zur Kennzeichnung von vornherein gemeinfreien Inhalten. Genaueres dazu hier.
\n2. Inhalte mit einem Hauptelement
\nBei Inhalten, die aus einem Hauptelement bestehen, durch die Mischung aus KI-Generierung und pers\u00f6nlichem Schaffen entstanden sind und bei denen der Schwerpunkt der Erstellung im pers\u00f6nlichen Schaffen liegt, kann der Inhalt insgesamt mit einer Lizenz wie der CC BY 4.0-Lizenz versehen werden. Liegt der Schwerpunkt in der KI-Generierung, ist der Inhalt insgesamt als gemeinfrei zu kennzeichnen. In beiden F\u00e4llen kann auch hier eine CC0 Lizenz verwendet werden.
\nIm Kontext der KI-Verordnung hat die EU-Kommission j\u00fcngst einen Verhaltenskodex f\u00fcr die Kennzeichnung von KI-Inhalten ver\u00f6ffentlicht. In diesem Leitfaden finden sich auch Vorschl\u00e4ge f\u00fcr KI-Kennzeichnungs-Symbole, die hier n\u00e4her dargestellt werden. Auch wer individuelle OER-Materialien erstellt, kann hieraus Orientierungshilfen f\u00fcr die KI-Kennzeichnung ableiten. Generell empfiehlt es sich bei der Erstellung von OER-Materialien mit KI den verwendeten KI-Dienst zu nennen. Dar\u00fcber hinaus sollten Erstellende darstellen, wof\u00fcr KI genau verwendet wurde und der Prompt sollte allgemein beschrieben werden. Bei Materialien mit trennbaren Anteilen bietet sich die Kennzeichnung so nah am KI-Inhalt wie m\u00f6glich an (beim Text-Bild-Beispiel also direkt unter dem Bild). Bei Materialien mit einem Hauptelement kann der Hinweis unter dem Inhalt erfolgen.
\nHinweis: Dieser Beitrag ist Teil einer Kooperation von\u00a0iRights.info, dem\u00a0Deutschen Bildungsserver\u00a0und\u00a0OERinfo. Der Text stammt von Lea Singson, steht unter der Lizenz CC BY 4.0\u00a0und wurde zun\u00e4chst bei\u00a0OERinfo\u00a0ver\u00f6ffentlicht.
\niRights.info\u00a0informiert und erkl\u00e4rt rund um das Thema \"Urheberrecht und Kreativit\u00e4t in der digitalen Welt\". Alle Texte erscheinen kostenlos und offen lizenziert.
\nWenn Sie m\u00f6gen, k\u00f6nnen Sie uns \u00fcber die\u00a0gemeinn\u00fctzige\u00a0Spendenplattform Betterplace\u00a0unterst\u00fctzen und daf\u00fcr eine Spendenbescheinigung erhalten. Betterplace akzeptiert PayPal, Bankeinzug, Kreditkarte, paydirekt oder \u00dcberweisung.
\nBesonders freuen wir uns \u00fcber einen regelm\u00e4\u00dfigen Beitrag, beispielsweise als monatlicher Dauerauftrag.\u00a0F\u00fcr Ihre Unterst\u00fctzung dankt Ihnen herzlich der\u00a0gemeinn\u00fctzige iRights e.V.!
\nDOI f\u00fcr diesen Text: https://doi.org/10.59350/p3anr-8y918\u00a0\u00b7 automatische DOI-Vergabe f\u00fcr Blogs \u00fcber The Rogue Scholar
\nThe post Die Mischung macht's: Kennzeichnung und Lizenzierung von Materialien mit KI-Anteil appeared first on iRights.info.
","doi":"https://doi.org/10.59350/p3anr-8y918","guid":"https://irights.info/?post_type=custom_artikel&p=32904","language":"de","license":"https://creativecommons.org/licenses/by/4.0/legalcode","published_at":1790208000,"rid":"3n4fc-x2226","summary":"Wie lizenziert man OERs, wenn diese aus so genanntem \"gemischtem Material\" mit KI-Anteil bestehen? Und wann haben solche Inhalte urheberrechtliche Relevanz? Mehr dazu hier: K\u00fcnstliche Intelligenz unterst\u00fctzt Schaffende auch bei der Erstellung von OERs in variablem Umfang.","tags":["Bildung + OER","Creative Commons + Lizenzen","Generative KI","Grundwissen","Urheberrecht"],"title":"Die Mischung macht's: Kennzeichnung und Lizenzierung von Materialien mit KI-Anteil","updated_at":1790321406,"url":"https://irights.info/artikel/gemischtes-material-ki/32904","version":"v1"}},{"document":{"authors":[{"affiliation":[{"id":"https://ror.org/04xfq0f34","name":"RWTH Aachen University"}],"contributor_roles":[],"family":"Hoyt","given":"Charles Tapley","url":"https://orcid.org/0000-0003-4423-4370"}],"blog":{"authors":null,"community_id":"da4ef2af-5fad-46b2-8195-d77db0141ad6","created":1716422400,"current_feed_url":null,"description":"Unraveling complex biology with biological knowledge graphs. Content licensed under CC BY 4.0.","doi":"https://doi.org/10.59350/cthoyt","favicon":"https://rogue-scholar.org/api/communities/da4ef2af-5fad-46b2-8195-d77db0141ad6/logo","feed_format":"application/atom+xml","feed_url":"https://cthoyt.com/feed.xml","filter":null,"generator":"Jekyll","home_page_url":"https://cthoyt.com/","issn":null,"language":"eng","license":"https://creativecommons.org/licenses/by/4.0/legalcode","prefix":"10.59350","relative_url":null,"secure":true,"slug":"cthoyt","status":"active","subfield":"1312","title":"Biopragmatics","updated":1790250300,"use_api":null},"blog_name":"Biopragmatics","blog_slug":"cthoyt","content_html":"A resolver is a web application that returns a redirect response for the uniform\nresource identifier (URI) expansion of a compact URI (CURIE). This post\ndemonstrates the resolver implemented as part of the\ncuries Python package, which is\nused by the Bioregistry and\nSemantic Farm.
I actually wrote the first version of this post in 2023 as I started\nexternalizing functionality from the bioregistry that could be made more\ngeneric. At the time, there were already several other resolvers (sometimes\ncalled meta-resolvers):
.htaccess rulesHowever, there are issues here with transparency, easy of configuration, and\nextensibility. I had already begun writing about the curies package as a\nfinal implementation of CURIE and URI conversion logic in a previous post on the curies package.
The following is an end-to-end example of using this function to create a small\nweb resolver application. This uses a flask.Blueprint which allows the\nresolver to be mounted on any pre-existing Flask application.
# flask_example.py\nfrom flask import Flask\nfrom curies import Converter, get_obo_converter\nfrom curies.resolver_service import get_flask_blueprint\n\n# Create a converter\nconverter: Converter = get_obo_converter()\n\n# Create a blueprint from the converter\nblueprint = get_flask_blueprint(converter)\n\n# Create the Flask app and register the blueprint\napp = Flask(__name__)\napp.register_blueprint(blueprint)\n\nif __name__ == \"__main__\":\n app.run()\nIf you don't need the flexibility of mounting on a pre-existing application, you\ncan use the curies.get_flask_app as a shortcut.
# flask_example.py\nfrom flask import Flask\nfrom curies import get_obo_converter, Converter\nfrom curies.resolver_service import get_flask_app\n\n# Create a converter\nconverter: Converter = get_obo_converter()\n\n# Create the Flask app and register the blueprint\napp: Flask = get_flask_app(converter)\n\nif __name__ == \"__main__\":\n app.run()\nIn the command line, either run your Python file directly, or via with\ngunicorn:
$ uvx gunicorn --bind 0.0.0.0:5000 flask_example:app\nTest a request in the Python REPL. Note that Flask's development server runs on\nport 5000 by default.
\n>>> import requests\n>>> requests.get(\"http://localhost:5000/GO:0032571\").url\n'http://amigo.geneontology.org/amigo/term/GO:0032571'\nThe same thing works for FastAPI applications, except with a fastapi.Router:
# fastapi_example.py\nfrom fastapi import FastAPI\nfrom curies.resolver_service import get_fastapi_router\nfrom curies import Converter, get_obo_converter\n\n# Create a converter\nconverter: Converter = get_obo_converter()\n\n# Create a router from the converter\nrouter = get_fastapi_router(converter)\n\n# Create the app and mount the router\napp = FastAPI()\napp.mount(router)\n\nif __name__ == \"__main__\":\n app.run()\nIf you don't need the flexibility of mounting on a pre-existing application, you\ncan use the curies.get_flask_app as a shortcut.
# fastapi_example.py\nfrom fastapi import FastAPI\nfrom curies import get_obo_converter, Converter\nfrom curies.resolver_service import get_fastapi_app\n\n# Create a converter\nconverter: Converter = get_obo_converter()\n\n# Create the Flask app and mount the router\napp: FastAPI = get_fastapi_app(converter)\n\nif __name__ == \"__main__\":\n import uvicorn\n\n uvicorn.run(app)\nIn the command line, either run your Python file directly, or via with\ngunicorn:
$ uvicorn --bind 0.0.0.0:5000 fastapi_example:app\nThere's a high-level CLI built in to the curies package that can be pointed at\na given local or remove prefix map, extended prefix map, or JSON-LD context to\nmake a resolver:
$ uvx \\\n --with click \\\n --with flask \\\n curies resolver\n --format prefix_map \\\n https://prefix.zazuko.com/api/v1/prefixes\nInstalled 15 packages in 11ms\n * Serving Flask app 'curies.resolver_service'\n * Debug mode: off\nWARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.\n * Running on all addresses (0.0.0.0)\n * Running on http://127.0.0.1:8764\n * Running on http://192.168.2.118:8764\nPress CTRL+C to quit\nFlags can be used to toggle the implementation (FastAPI or Flask) and the server\n(werkzeug, gunicorn, uvicorn). See --help for more information.
The inaugural European Small Mammal Conservation Conference (SMCC 2026) took place in Sofia, Bulgaria, from 21 to 25 September 2026, bringing together researchers, conservationists and practitioners from across Europe and beyond to address gaps in small mammal research and monitoring.
\n\n\nOrganised jointly by the Habitat Foundation, the Institute of Biodiversity and Ecosystem Research at the Bulgarian Academy of Sciences, the Dutch Mammal Society and Mammal Conservation Europe, with support from the Faculty of Biology at Sofia University, the conference formed part of the Life for Falcons project, funded by the EU LIFE Programme.
\n\n\n\nThis year’s conference was held jointly with the 33rd Hamster Working Group and the VIII European Ground Squirrel Meeting, making hamsters and sousliks the primary focus, alongside broader topics including renewable energy development, agricultural impacts, reintroductions, predator\u2013prey interactions and innovative methodologies in small mammal research.
\n\n\n\nWe were delighted to participate in SMCC 2026 with an exhibition booth, showcasing the breadth of publishing services we offer to the biodiversity and conservation community. It was a pleasure to present our portfolio of journals dedicated to advancing research across ecology, biodiversity and conservation.
\n\n\n\n\n\n\n\nWe were particularly proud to present the following journals:
\n\n\n\nMeeting delegates from across the small mammal research community was tremendously rewarding, and we thoroughly enjoyed discussing how our journals can support and amplify their work.
\n\n\n\nBeyond our academic offerings, we were particularly excited to showcase beautiful art prints illustrated by our in-house scientific illustrator, Denitsa Peneva. The collection featured stunning depictions of otters, olinguitos and hamsters.
\n\n\n\nThe scientific programme was exceptional, and we were privileged to attend many outstanding presentations that demonstrated the importance of innovative monitoring approaches and conservation action.
\n\n\n\nLessons from Citizen Science for Small Mammal Conservation Monitoring in Great Britain
\n\n\n\nWe were delighted to attend a talk by Matt Larsen-Daw, Chief Executive of the Mammal Society (UK), which presented a portfolio of citizen science programmes designed to address distribution knowledge and population monitoring across Great Britain. The programmes, united by the Mammal Mapper smartphone app, included the National Harvest Mouse Survey, the Searching for Shrews initiative, and the University Mammal Challenge.
\n\n\n\nThe presentation highlighted the value of standardised effort data, the differing trade-offs between structured and opportunistic recording, and the potential for these approaches to be applied across European contexts.
\n\n\n\nStrong Decline of Hamster Populations in Bulgaria
\n\n\n\nWe were equally impressed by Nedko Nedyalkov’s presentation documenting the significant decline in distribution and abundance of both the common hamster (Cricetus cricetus) and the Romanian hamster (Mesocricetus newtoni) across Bulgaria. The research revealed that population reductions, detected through owl pellet analysis and trapping methods, likely began in the 1950s with agricultural intensification and continue today.
\n\n\n\nGiven that both species are strictly protected under the EU Habitats Directive yet lack active conservation projects, the presentation substantiated the urgent need for targeted conservation measures. We are also pleased to note that Nedko serves as a subject editor for two of our open-access journals, ZooKeys and the Biodiversity Data Journal.
\n\n\n\nReintroduced Saker Falcons and Their Dependence on European Ground Squirrels
\n\n\n\nYana Andonova's presentation on the diet of Bulgaria’s reintroduced saker falcon population provided compelling evidence of the breeding birds' overwhelming dependence on the European ground squirrel (Spermophilus citellus) as a primary food source.
\n\n\n\nThrough food-remain analysis, visual observations and camera-trap monitoring, the research documented that ground squirrels comprised over 80 per cent of identified prey items, with small rodents accounting for 89 per cent overall! It is also worth mentioning that Andonova is an author in our open-access Biodiversity Data Journal.
\n\n\n\nAttending SMCC 2026 was a genuine pleasure and particularly meaningful given that the conference took place in Sofia, the city in which our company is based. Connecting with researchers and conservationists working at the forefront of small mammal conservation, and sharing our commitment to advancing biodiversity research through open-access publishing, reinforced our dedication to supporting this important field.
\n\n\n\nWe look very much forward to engaging with this community again at future events!
\n\n\n\nFollow us on Bluesky, Facebook, X, and LinkedIn for future conference updates.
\n\n","doi":"https://doi.org/10.59350/hmn14-8zj12","guid":"https://blog.pensoft.net/?p=20924","image":"https://blog.pensoft.net/wp-content/uploads/2026/09/SciComm-PR-2026-Instagram-2026-09-23T165239.066.png","language":"en","license":"https://creativecommons.org/licenses/by/4.0/legalcode","published_at":1790294400,"rid":"n5rb6-tqh12","summary":"Tweet The inaugural European Small Mammal Conservation Conference (SMCC 2026) took place in Sofia, Bulgaria, from 21 to 25 September 2026, bringing together researchers, conservationists and practitioners from across Europe and beyond to address gaps in small mammal research and monitoring.","tags":["Biodiversity Data Journal","Frontiers Of Biogeography","Individual-based Ecology","Nature Conservation","One Ecosystem"],"title":"Pensoft at the European Small Mammal Conservation Conference 2026","updated_at":1790337914,"url":"https://blog.pensoft.net/2026/09/25/pensoft-at-the-european-small-mammal-conservation-conference-2026/","version":"v1"},{"authors":[{"contributor_roles":[],"family":"Franziska Altemeier","given":"Nina D\u00fcvel"}],"blog":{"authors":null,"community_id":"db0d8909-9e37-46d0-b16c-0551f575e86b","created":1749772800,"current_feed_url":null,"description":"Das Blog der TIB \u2013 Leibniz-Informationszentrum Technik und Naturwissenschaften und Universit\u00e4tsbibliothek","doi":"https://doi.org/10.65527/tib","favicon":"https://rogue-scholar.org/api/communities/db0d8909-9e37-46d0-b16c-0551f575e86b/logo","feed_format":"application/atom+xml","feed_url":"https://blog.tib.eu/feed/atom/","filter":null,"generator":"WordPress","home_page_url":"https://blog.tib.eu/","issn":null,"language":"deu","license":"https://creativecommons.org/licenses/by/4.0/legalcode","prefix":"10.65527","relative_url":null,"secure":true,"slug":"tib","status":"active","subfield":"1802","title":"TIB-Blog","updated":1790331374,"use_api":true},"blog_name":"TIB-Blog","blog_slug":"tib","content_html":"Am 21. und 22. September 2026 fand an der Bibliotheca Hertziana \u2013 Max-Planck-Institut f\u00fcr Kunstgeschichte in Rom das Kick-off-Meeting des DFG/AHRC-gef\u00f6rderten Forschungsprojekts \"SERIOUS 3D in Art and Architectural History\" statt.
\nWissenschaftlerinnen und Wissenschaftler aus den Bereichen Kunst- und Architekturgeschichte (AAH), 3D Engineering (ENG) und Data Science in Cultural Heritage (DSC) diskutierten \u00fcber Forschungsziele, technische Anforderungen, methodische Herausforderungen und anstehende Arbeiten des gemeinsamen Projekts.
\nDas interdisziplin\u00e4re Projekt bringt Expertise aus der Bibliotheca Hertziana, der Hochschule Mainz, der TIB \u2013 Leibniz-Informationszentrum Technik und Naturwissenschaften in Hannover sowie den Universit\u00e4ten Cambridge und Exeter zusammen.
\nIm Mittelpunkt steht die Frage, wie historische R\u00e4ume mithilfe digitaler Technologien rekonstruiert, interpretiert und vermittelt werden k\u00f6nnen.
\nEin zentrales Thema des Kick-off-Meetings war die praktische Umsetzung der Verbindung kunsthistorischer Forschungsfragen mit digitalen 3D-Modellen als Teil strukturierter Forschungsdaten.
\nHistorische Rekonstruktionen beruhen auf unterschiedlichen Quellen, wissenschaftlichen Interpretationen und mitunter unvollst\u00e4ndigen Informationen; nicht alle Informationen lassen sich ohne Weiteres in ein digitales Geb\u00e4udemodell \u00fcbertragen,
\nDas Projekt untersucht deshalb auch, wie sich solche Unsicherheiten und die zugrunde liegenden Entscheidungen nachvollziehbar dokumentieren lassen.
\nDie Gruppe Data Science in Cultural Heritage (DSC), bestehend aus dem Open Science Lab der TIB und dem DH Lab der Bibliotheca Hertziana, befasst sich unter anderem damit, wie sich diese Informationen in einer gemeinsamen technischen Infrastruktur zusammenf\u00fchren lassen.
\nEin Baustein ist das im Open Science Lab entwickelte 3D-Viewer- und Annotationswerkzeug Semantic Kompakkt f\u00fcr interoperable und nachnutzbare Forschungsdaten, das mit Wikibase4Research ein Backend f\u00fcr die semantischen Informationen beinhaltet.
\nIm Projekt Herrenh\u00e4user des Ostseeraums wird Semantic Kompakkt bereits f\u00fcr einen vergleichbaren architekturhistorischen Anwendungsfall eingesetzt und entsprechend der Bedarfe einer architekturhistorischen wissenschaftlichen Community weiterentwickelt, unter anderem die Visualisierung von Punktwolken und den historischen oder \u00f6rtlichen Zusammenh\u00e4ngen.
\nBereits eine Woche vor dem Kick-off hatte das TIB-Team seine Arbeiten zur Integration des in Serious 3D genutzten Building Information Modeling (BIM) in Semantic Kompakkt auf der Konferenz FAIR 3D Heritage in Mainz vorgestellt. Der Beitrag \"Towards (H)BIM Integration in Semantic Kompakkt: Evaluation of Web Libraries for a Modular Import Pipeline\" lieferte konkrete Ans\u00e4tze f\u00fcr die anschlie\u00dfende Arbeit in Rom. Weitere Informationen finden sich im Konferenzprogramm der FAIR 3D Heritage.
\nDie Diskussionen machten deutlich, dass die Anforderungen der beteiligten Disziplinen bereits bei der kunsthistorischen Recherche und der Erstellung der ersten digitalen Geb\u00e4udemodelle ber\u00fccksichtigt werden m\u00fcssen. Dazu geh\u00f6rt insbesondere die Frage, welche Informationen sp\u00e4ter f\u00fcr die semantische Modellierung, wissenschaftliche Annotation und Visualisierung ben\u00f6tigt werden.
\nAls n\u00e4chster Schritt sollen exemplarische 3D-Modelle mit unterschiedlicher Informationstiefe seitens der ENG-Partner bereitgestellt werden. An ihnen will das DSC-Team den gesamten Workflow vom Datenimport bis zur interaktiven Darstellung erproben.
\nDie Modelle sollen historische Raumsituationen nicht nur veranschaulichen, sondern auch als Arbeitsgrundlage f\u00fcr kunsthistorische Fragestellungen der AAH-Beteiligten dienen. Daf\u00fcr m\u00fcssen Quellen und unterschiedliche Rekonstruktionshypothesen mit den modellierten Objekten verkn\u00fcpft werden k\u00f6nnen.
\nThematisiert wurde au\u00dferdem, wie sich historische R\u00e4ume durch webbasiertes Storytelling interaktiv erkunden und zugleich mit Quellen, Forschungsfragen und Erl\u00e4uterungen verbinden lassen.
\nIn der abschlie\u00dfenden Diskussion wurde nochmals betont, dass SERIOUS 3D als gemeinsamer Forschungsprozess, und nicht nur als Zusammenarbeit voneinander getrennter Arbeitsgruppen verstanden werden soll.
\nDie unterschiedlichen fachlichen Perspektiven sollen bereits bei der Entwicklung der Forschungsfragen, der Auswahl historischer Objekte und der Erarbeitung digitaler Methoden zusammengef\u00fchrt werden.
\nIm Anschluss an das Kick-off-Meeting reist das Projektteam vom 23. bis 25. September 2026 zur Feldforschung nach Florenz. Dort werden Teile des Palazzo Medici, das zentrale Forschungsobjekt von SERIOUS 3D, mithilfe von 3D-Laserscanning und Photogrammetrie digital erfasst.
\nDie gewonnenen Daten bilden die Grundlage f\u00fcr die weitere Entwicklung des historischen Geb\u00e4udemodells und die Erprobung der in Rom diskutierten technischen Workflows.
","doi":"https://doi.org/10.65527/ehvpv-0zn69","guid":"https://blog.tib.eu/?p=33673","image":"https://blog.tib.eu/wp-content/uploads/2026/09/SERIOUS-3D-in-Art-and-Architectural-History_2_quer.jpg","language":"de","license":"https://creativecommons.org/licenses/by/4.0/legalcode","published_at":1790294400,"rid":"4b751-nmd91","summary":"Am 21. und 22. September 2026 fand an der Bibliotheca Hertziana \u2013 Max-Planck-Institut f\u00fcr Kunstgeschichte in Rom das Kick-off-Meeting des DFG/AHRC-gef\u00f6rderten Forschungsprojekts \"SERIOUS 3D in Art and Architectural History\" statt.","tags":["OPENNESS","FORSCHUNG & PROJEKTE","Lizenz:CC-BY-4.0-INT","Open Science Lab","Open Science"],"title":"SERIOUS 3D: Kunst- und Architekturgeschichte im digitalen Forschungsraum","updated_at":1790331830,"url":"https://blog.tib.eu/2026/09/25/serious-3d-kunst-und-architekturgeschichte-im-digitalen-forschungsraum/","version":"v1"},{"authors":[{"contributor_roles":[],"family":"Eden","given":"Terence"}],"blog":{"authors":null,"community_id":"61ce553a-bafd-4aba-a952-d3bab5e85bcc","created":1788652800,"current_feed_url":null,"description":"Regular nonsense about tech and its effects \ud83d\ude43","doi":"https://doi.org/10.59350/shkspr","favicon":"https://rogue-scholar.org/api/communities/61ce553a-bafd-4aba-a952-d3bab5e85bcc/logo","feed_format":"application/atom+xml","feed_url":"https://shkspr.mobi/blog/feed/DOI","filter":"category:-1982","generator":"WordPress","home_page_url":"https://shkspr.mobi/blog","issn":"2753-1570","language":"eng","license":"https://creativecommons.org/licenses/by/4.0/legalcode","prefix":"10.59350","relative_url":null,"secure":true,"slug":"shkspr","status":"active","subfield":"1712","title":"Terence Eden's Blog","updated":1790328333,"use_api":true},"blog_name":"Terence Eden's Blog","blog_slug":"shkspr","content_html":"One of the great things about modern HTML is that it tries to standardise stuff that developers are already doing. If there are a myriad ways of, for example, loading video onto a page - then browsers and other interested parties should work out how to make a standard <video> element.
An interesting new proposal has been brought forth by Microsoft. There are a dozen ways to show a preview of an <img> element before the src= attribute has loaded. So why not standardise on previewsrc=? There's an excellent explainer on Patrick Brosset's blog.
I instinctively like the idea - if only to simplify source code and reduce JS usage. But I do have some concerns which I've shared with the team.
\n\nThis is the thing I always bang on about when I'm discussing standards. Additions to HTML should primarily benefit end users, not developers.
\n\nDo end users want this? Is there a bunch of research that shows normal people are confused that they don't see a preview image? Do they recoil in fear and distress while waiting for a full resolution picture to appear?
\n\nWhen people see a blurry or blocky image, do they understand that they need to wait for the full thing - or do they assume their computer is broken?
\n\nMicrosoft has a bazillion dollars - it can afford to spend a few thousand on interviewing some real users and mapping out what they're likely to want from this.
\n\nI begrudgingly admit that developers need love too.
\n\n\n\nWhat are the pain points of the current implementations? Is it hard to dynamically generate multiple images? Is the syntax hard to use? Do blurs slow down the page?
\n\nAgain, MS needs to pony up some cash to talk to developers. At the very least run a survey of all existing websites in the BING! database and see what they use.
\n\nWhen an image doesn't load, or loads slowly, a user will normally be shown some alt text - like this:
\n\n\n\nIs that more or less useful than this?
\n\n\n\nAccessibility isn't just for people with visual impairments! This is an issue I've raised with them.
\n\nI've written before about the usability of HTML elements. Some of the newer ones like <picture> have very poorly named attributes in my opinion.
One alternative for previewsrc is poster. That would match with the poster attribute on the <video> element. They both show a preview image before the main content is loaded.
Given their functionality is identical, I think it makes sense for them to have the same name. You wouldn't expect to see <video horizontal=\"1920\" vertical=\"1080\"> would you? No. That's why they use the same width and height attributes as images.
There are several interesting objections and discussions on the GitHub repo. I'm delighted that this is being talked about in the open, rather than just being presented as a fait accompli (remember the toast proposal?).
\n\nAs I said, I genuinely think that there's a useful idea in here. But after writing all of this, I think it would be better and simpler for developers to use progressive images rather than overload HTML with a new attribute.
\n\nIf website owners can't be bothered to save progressive images, I don't see why they'd bother to create a separate preview image.
\n\nKeeping preview images in sync with their full images is also likely to be a problem.
\n\nIf you think I'm wrong, read the explainer and then chat with Microsoft.
","doi":"https://doi.org/10.59350/twr9x-eh003","guid":"https://shkspr.mobi/blog/?p=75856","image":"https://shkspr.mobi/blog/wp-content/uploads/2018/01/HTML5_Badge_512.png","language":"en","license":"https://creativecommons.org/licenses/by/4.0/legalcode","published_at":1790208000,"rid":"bke8v-4h802","summary":"One of the great things about modern HTML is that it tries to standardise stuff that developers are already doing. If there are a myriad ways of, for example, loading video onto a page - then browsers and other interested parties should work out how to make a standard element. An interesting new proposal has been brought forth by Microsoft.","tags":["/etc/","HTML","Standards"],"title":"Some thoughts on HTML's proposed previewsrc attribute","updated_at":1790328376,"url":"https://shkspr.mobi/blog/2026/09/some-thoughts-on-htmls-proposed-previewsrc-attribute/","version":"v1"},{"authors":[{"affiliation":[{"id":"https://ror.org/02feahw73","name":"Centre National de la Recherche Scientifique"}],"contributor_roles":[],"family":"Hinsen","given":"Konrad","url":"https://orcid.org/0000-0003-0330-9428"}],"blog":{"authors":null,"community_id":"2488dc7f-4f82-4051-8490-22d2cd8d472d","created":1719792000,"current_feed_url":null,"description":null,"doi":"https://doi.org/10.59350/khinsen","favicon":"https://rogue-scholar.org/api/communities/2488dc7f-4f82-4051-8490-22d2cd8d472d/logo","feed_format":"application/atom+xml","feed_url":"https://blog.khinsen.net/feeds/all.atom.xml","filter":null,"generator":"Other","home_page_url":"https://blog.khinsen.net/","issn":null,"language":"eng","license":"https://creativecommons.org/licenses/by/4.0/legalcode","prefix":"10.59350","relative_url":null,"secure":true,"slug":"khinsen","status":"active","subfield":"1802","title":"Konrad Hinsen's blog","updated":1790294400,"use_api":null},"blog_name":"Konrad Hinsen's blog","blog_slug":"khinsen","content_html":"Knowledge refinement is the ever ongoing process in science (and beyond it) that shepherds knowledge from lab notebooks into journal articles and then on to review articles, monographs, reference handbooks, university textbooks, and finally professional domain expertise and school education for a wider public. It has been going on for a few centuries, but we hardly talk about it. In fact, I made up the term because I couldn't find an established one. Computational knowledge has not yet found its place in the knowledge refinement process. Why not? And what can we do to make it happen?
\n\nFirst of all, what is the role of knowledge refinement?
\nOne answer is that knowledge becomes more reliable in the refinement process. Any single experiment, no matter how carefully done, can turn out to be wrong for lots of reasons. In contrast, the synthesis of hundreds of independent related experiments will remain trustworthy even if one flaky input experiment has to be withdrawn.
\nAnother role of knowledge refinement is making knowledge more accessible. When we learn from others, rather than from our own experience, we start with a highly refined view of a domain, and dive into the details only later and when we see a need for it. Schools teach only refined knowledge, which thus shapes general culture.
\nFinally, with refinement, knowledge also becomes more long-lived. A useful picture here is pace layers: each refinement step pushes knowledge down into a more slowly evolving layer.
\nEach knowledge refinement step has several interrelated aspects:
\nSummarization. A large number of works from the preceding step are cooked down into a common essence that emerges from them.
Curation. Domain experts select what they see as most relevant, discarding what they consider technical details, or only of historical importance.
Integration. Each step draws on broader domain coverage than the preceding one. The relation to already established knowledge is made clearer.
Simplification and clarification. Each step is written for a wider and less specialized audience than the preceding one. Jargon is replaced by more widely understood vocabulary. New concepts are introduced and the explanation is structured around them.
All these processes require reformulation. The output of a refinement step is not simply an annotated collection of quotes from its inputs. You can't edit a journal article into a chapter for a university textbook.
\nIn the digital era, it has become widely accepted that software and electronic datasets are representations of scientific knowledge. See for example pages 9 to 11 of the UNESCO Recommendation on Open Science, which discuss \"open scientific knowledge\". For now, however, this is mostly wishful thinking. While code and data certainly are scientific information, it is difficult to consider them to be knowledge as long as they don't participate in the knowledge refinement process.
\nLet me illustrate this with analogies from pre-digital science. The predecessors of today's digital datasets are tables of observations recorded in lab notebooks. The predecessors of today's scientific software are mathematical equations. Consider the foundational research on electromagnetism that was done in the 19th century. Examples of original sources are the lab notebooks of Michael Faraday, or on the theoretical side James Clerk Maxwell's paper \"A Dynamical Theory of the Electromagneticm Field\" (already a refined version of his personal notes, which are probably lost). Today's textbooks in physics or electrical engineering mention both Faraday and Maxwell in historical overviews, but they don't ask you to consult their original work, nor do they cite passages from it in their pedagogical presentation. Instead, they show highly refined versions of Maxwell's theory in modern vector notation, which was largely created for this purpose. The textbooks also summarize the kind of experiments done by Faraday and many others, with pictures and diagrams of modern rather than historical instruments and experimental setups. Instead of real data, they show plots of idealized synthetic data for illustration.
\nWhereas nobody would seriously consider publishing a lab notebook as a journal article after just some light editing, many researchers seem to believe that computational notebooks, such as the popular Jupyter notebooks, could replace journal articles. However, the history and practice of Jupyter shows that it is by design a tool for interactive computational exploration. A Jupyter notebook is an annotated chronological record of a single computation. There is no way to summarize multiple computations. There is no way to focus on the essential aspects of a computation while relegating implementation details to an appendix. There is no way to explain, in more than words, algorithms from a library that is used in the notebook. Moreover, the order of presentation is constrained by the flow of the computation. In a typical Jupyter notebook, one of the very first lines says import matplotlib, a technical detail that in a journal article should be relegated to a reference list, because it is irrelevant to the scientific message.
If you look at today's published Jupyter notebooks, most of them are complements to journal articles. The play the role of an appendix, a repository for technical details. Notebooks that are independent publications do exist, for example in the Journal of Digital History, but the computations they contain, basic data analysis and visualization, are simple and not the main topic of the paper. Moreover, the Journal of Digital History has developed its own extensions to Jupyter that add support for hiding technical details from view while reading the article.
\nWhile I focused on Jupyter because of its popularity, other notebook technologies such as Quarto or Emacs' Babel extension to org-mode are not fundamentally different. As long as the executable content is a single computation that runs from top to bottom, the above criticisms remain valid.
\nVarious ideas for improving the publishing technology for code are being explored. One of them is removing the linear execution constraint, e.g. by using the dataflow paradigm. A few notebook systems have adopted this approach, most notably Observable. The most interesting system I have seen so far in this space is Lopecode, which adds a hypertext structure to Observable's dataflow model for computation. My own experiment on supporting the publication of refined digital knowledge is HyperDoc, which focuses on (1) integrating code and its execution into hypermedia networks and (2) building bridges to existing hypermedia systems. It has the advantage of being applicable to existing code in any programming language (though this requires significant implementation work that hasn't been done yet), and thus avoids a complete break with the past six decades of computational research.
\nMuch more remains to be done, however, before computational knowledge can become an integral part of the refinement process. Computational knowledge is most of all formalized knowledge, meaning knowledge expressed in terms of a formal system that can be processed mechanically, by a computer. Refinement techniques for formalized knowledge are constrained by the formal system they depend on. Program source code lives in a formal system defined by a programming language. It is processed mechanically by a compiler or an interpreter. The focus of a programming language is, not surprisingly, the construction of executable programs. There is a well-established refinement process for source code: scripts become library modules, which are complemented by tests and documentation and then published to become off-the-shelf ingredients for constructing more complex programs. Like knowledge refinement, code refinement makes code more reliable, more accessible, and long-lived, but only from the \"code as a tool\" perspective. It tends to reduce rather than augment its value as a knowledge repository. Software engineering priorities such as optimization and reducing redundancy tend to make the code less readable for researchers who are not professional software developers, and impenetrable to anyone who is just starting to explore a new domain of knowledge.
\nThis is why knowledge refinement in computational science remains limited to non-formal language. Textbooks remain printed books (or their digital twins, PDF files), merely referring to and writing about machine-readable artifacts such as code. The textbooks discuss concepts, including algorithms and data structures, but don't provide examples that readers could run and then build on in their own explorations. On the code side, there are often highly refined implementations for use as off-the-shelf tools, but their correspondence to what the textbooks say is unclear and not verifiable by the reader.
\nThere has been work on improving the explanation side, for example Bret Victor's explorable explanations that integrate interactive exploration tools into formerly passive textbook material. However, the strict divide between explanation and code for use in practice remains.
\nThis state of the art is tolerable for low-complexity computational knowledge, e.g. in linear algebra or signal processing. A textbook on Fourier transforms and good FFT library are good enough for learning these methods. But we need something better for complex models and methods.
\nConsider computational models of complex systems such as force fields for biomolecules, or climate models. On the machine side, they are implemented as software modules for use in simulation, using standard programming languages. On the human side, there are papers describing the principles behind their design, but lacking many details because these details would be overwhelming to a human reader. So if you really want to know how such models work, your only choice is wading through enormous amounts of source code, taking notes carefully of the findings that are relevant to your question. And if you ever want to compare two such complex models... good luck exploring two large software packages in parallel. Unfortunately, that's something you can't avoid doing during knowledge refinement. For example when you write a review paper on protein force fields, or on climate models.
\nWhen models become too complex to be represented in traditional scientific notations (equations, diagrams, etc.), they need to be represented in digital scientific notations. They need to be represented in formal systems that are made for documentation and exploration, rather than for plugging into a simulator. And they require tools that treat them as data, not code.
\nAn idea I have been pursuing for a while is the use of specification languages as digital scientific notations. See my project Leibniz for the details. Specification languages are more general than programming languages in the same way that mathematical equations are more general than mathematical functions (see here for a discussion). In particular, specification languages do not impose an executability condition on everything you write. This allows you to write incomplete function definitions or data structures. I am working on this idea and I remain optimistic that it will work out, but I won't declare victory before I have actually written that review of biomolecular force fields. Meanwhile, I'd be happy to see other work in this space, ideally pursuing very different ideas.
\nDigital scientific notations are a necessary first step for enabling the refinement of digital scientific knowledge, but the real works starts once we have them. We must then develop the tools that let researchers explore and examine publications containing formalized knowledge. We must also find refinement strategies that actually work in practice. There remains a lot to be done!
","doi":"https://doi.org/10.59350/5vb7q-rnw59","guid":"https://blog.khinsen.net/posts/2026/09/25/knowledge-refinement.html","language":"en","license":"https://creativecommons.org/licenses/by/4.0/legalcode","published_at":1790294400,"rid":"kn021-31216","summary":"Knowledge refinement is the ever ongoing process in science (and beyond it) that shepherds knowledge from lab notebooks into journal articles and then on to review articles, monographs, reference handbooks, university textbooks, and finally professional domain expertise and school education for a wider public.","title":"Knowledge refinement in the digital era","updated_at":1790328281,"url":"https://blog.khinsen.net/posts/2026/09/25/knowledge-refinement.html","version":"v1"},{"authors":[{"contributor_roles":[],"name":"Team OA Brandenburg"}],"blog":{"authors":null,"community_id":"00dd7e11-a802-44c1-9584-5c56d1f8d417","created":1706832000,"current_feed_url":null,"description":"Vernetzungs- und Kompetenzstelle Open Access Brandenburg","doi":"https://doi.org/10.59350/oabrandenburg","favicon":"https://rogue-scholar.org/api/communities/00dd7e11-a802-44c1-9584-5c56d1f8d417/logo","feed_format":"application/atom+xml","feed_url":"https://open-access-brandenburg.de/feed/atom","filter":null,"generator":"WordPress","home_page_url":"https://open-access-brandenburg.de/","issn":null,"language":"deu","license":"https://creativecommons.org/licenses/by/4.0/legalcode","prefix":"10.59350","relative_url":null,"secure":true,"slug":"oabrandenburg","status":"active","subfield":"1802","title":"Open Access Brandenburg","updated":1790261676,"use_api":false},"blog_name":"Open Access Brandenburg","blog_slug":"oabrandenburg","content_html":"F\u00fcr die Erfolgsbewertung der Open-Access-Transformation schauen wir als Vernetzungs- und Kompetenzstelle Open Access Brandenburg erwartungsgem\u00e4\u00df mit erheblichem Interesse darauf, was an den Hochschulen des Landes an Wissenschaft nach dem Open-Access-Modell erscheint. Zugleich \u00fcberlegen wir, wie wir diesen Entwicklungen st\u00e4rker sichtbar machen. Denn tats\u00e4chlich geschieht im Land Brandenburg erstaunlich viel und Open Access an vielen Stellen erstaunlich selbstverst\u00e4ndlich.\n\nEin Ansatz, denn wir aktuell etwas ausprobieren m\u00f6chten, sind kleine Textbohrungen in das Datenmaterial. Heute haben wir daf\u00fcr exemplarisch mit OpenAlex einen Blick darauf geworfen, welches die \u2013 bislang \u2013 meistzitierten Open-Access-Publikation der Forschung mit Beteiligung von an der Europa Universit\u00e4t Viadrina affiliierten Forschenden aus dem Jahr 2025 sind. \"Bislang\" bezieht sich auf die Tatsache, dass gerade beim F\u00e4cherspektrum der Viadrina l\u00e4ngere Zeitzyklen f\u00fcr Zitationen zu ber\u00fccksichtigen sind und je thematischer Entwicklung weitere Zitationen zu erwarten sind. Eine wissenschaftliche Arbeit braucht erfahrungsgem\u00e4\u00df eine Weile, bis sie in ihrer Zielcommunity sichtbar rezipiert und von dieser f\u00fcr neue Forschung verarbeitet wird. Diese Studie konstatiert beispielsweise generell eine durchschnittliche Zitationsverz\u00f6gerung von sieben bis acht Jahren. Und f\u00fcr die Geisteswissenschaften wurde gar eine \"Ruhezeit\" von f\u00fcnf Jahren ermittelt. Zugleich wollen wir nicht allzu weit zur\u00fcckgehen, weil uns auch interessiert, welche Forschungsthemen sich aktuell in der Aufmerksamkeit aktuell. Das bedeutet aber keinesfalls, dass wir uns nicht bei Gelegenheit auch einmal einen l\u00e4ngeren Zeitraum anschauen. Und ganz sicher beleuchten wir auch unsere anderen Einrichtungen im Land Brandenburg.\u00a0\nDie nachfolgende Rangliste erfolgt auf Angaben von OpenAlex. Die Zahl der Zitationen entspricht dem Stichtag 23.09.2026. Es wurden ausschlie\u00dflich Open-Access-Publikationen ber\u00fccksichtigt.\nZitierhinweis:
\nVernetzungs- und Kompetenzstelle Open Access Brandenburg (2026): \"Brandenburger OA-Top 10: Forschung aus der Europa Universit\u00e4t Viadrina Frankfurt (Oder), 2025.\" DOI: 10.59350/mp0vb-23e71
\nZitierhinweis:
\nKaden, Ben (2026): \"OA-Takeaways: Wie l\u00e4sst sich ein teilhabeorientiertes Open Access besser gestalten?.\" DOI: 10.59350/8kxzb-3k358
\nThis post describes how I extended the work in my previous\npost that axiomatizes\nneutron numbers and nucleon numbers for isotopes that appear in ChEBI as\nchildren of atom terms, then materializes isotope (same atomic number), isotone\n(same neutron number), and isobar (same nucleon number) relationships between\nthem.
\nWhile the previous post was directly motivated by needs for the upcoming basis\nset ontology for NFDI4Chem, extending the axiomizations from partially qualified\natoms (with just atomic number) to fully qualified atoms (with both atomic and\nneutron number) was an obvious next step once I was already familiar with the\nChEBI atom hierarchy.
\nThe code and data presented in this post were added in\ncthoyt/chebi-atomic-numbers-ontology@2\nand\ncthoyt/chebi-atomic-numbers-ontology#3.
\nWhile ChEBI has full coverage through element 117 in the atoms branch, it only\nhas partial coverage of isotopes. I used the following script to produce an\ninitial ROBOT template:
\nimport pandas as pd\nimport pyobo\n\nelements_df = pd.read_csv(\"elements.tsv\", sep=\"\\t\", skiprows=2, header=None)\nrows = []\nfor curie, _, label, number in elements_df.values:\n for child in pyobo.get_descendants(curie) or []:\n full_name = pyobo.get_name(child, strict=True)\n name = full_name.removesuffix(\"atom\").strip()\n _, _, total = name.partition(\"-\")\n if total:\n total = int(total)\n rows.append((child.curie, \"class\", name, total, total - number))\n else:\n print(f\"failed on {child.curie} - {full_name}\")\n\nisotopes_df = pd.DataFrame(rows)\nisotopes_df.to_csv(\"isotopes.tsv\", sep=\"\\t\", index=False)\nExcept the three isotopes of hydrogen, which each have their own labels, all\nisotopes' labels have the following form:
| curie | \ntype | \nlabel | \nnucleon number | \nneutron number | \n
|---|---|---|---|---|
| ID | \nTYPE | \n\u00a0 | \nSC 'ChEMROF:nucleon_number' value % | \nSC 'ChEMROF:neutron_number' value % | \n
| CHEBI:29236 | \nclass | \nprotium atom | \n1 | \n0 | \n
| CHEBI:29237 | \nclass | \ndeuterium atom | \n2 | \n1 | \n
| CHEBI:29238 | \nclass | \ntritium atom | \n3 | \n2 | \n
| CHEBI:30218 | \nclass | \nhelium-3 | \n3 | \n1 | \n
| CHEBI:37004 | \nclass | \nhelium-8 | \n8 | \n6 | \n
| CHEBI:30219 | \nclass | \nhelium-4 | \n4 | \n2 | \n
| CHEBI:37003 | \nclass | \nhelium-6 | \n6 | \n4 | \n
This template works the same way I described in the previous post, now using two columns for data value\nconstraints instead of just a single column. Note, the links are added here for\nconvenience, and don't/shouldn't actually appear in ROBOT templates.
\nInterestingly, a related\ndiscussion\nwill be taking place at the\nOntologies4Chem Workshop 2026.\nI would like to add the missing isotopes to ChEBI, but this will probably take a\nwhile!
\nI had high hopes that formalizing the atomic number, nucleon number, and neutron\nnumber would allow for me to encode inference rules to cover what it means for\ntwo fully qualified atoms to be isotopes, isobars, or isotones of each other,\nfor example, using\nSemantic Web Rule Language (SWRL). However,\nI had a pretty typical experience that the OWL and semantic web technologies\ndon't directly support this (IMO) rather obvious use case.
\nInstead, I opted to write several SPARQL queries that can be used with\nrobot query to manipulate OWL as\nRDF and add in new object property constraints directly with a command like:
$ robot query \\\n --update src/isobar-construct.ru \\\n --update src/isotone-construct.ru \\\n --update src/isotope-construct.ru\nSee the full incorporation into the build in the repository's\njustfile.
\nIsotopes are atoms of the same element\nwith different number of neutrons. They can be produced, e.g., through the\nprocess of neutron capture. For\nexample, thallium-199 (CHEBI:37805),\nthallium-201 (CHEBI:37804),\nthallium-203 (CHEBI:37802), and\nthallium-205 (CHEBI:37803) are isotopes of\nthallium.
\nThe following SPARQL materializes isotope relationships between atoms using the\nChEMROF:isotope_of relationship.
\nINSERT {\n ?x rdfs:subClassOf [\n owl:onProperty ChEMROF:isotope_of;\n owl:someValuesFrom ?y\n ] .\n}\nWHERE {\n ?atom rdfs:subClassOf [\n owl:onProperty ChEMROF:atomic_number;\n owl:hasValue ?atomic_number\n ] ;\n ?x rdfs:subClassOf ?atom .\n ?y rdfs:subClassOf ?atom .\n FILTER(?x != ?y)\n}\nIsotones are atoms of different\nelements with the same number of neutrons. They can be produced, e.g., through\nthe process of proton capture.\nFor example, nitrogen-17 (CHEBI:36937)\noxygen-18 (CHEBI:33815), and\nfluorine-19 (CHEBI:36940) each have 10\nneutrons.
\nThe following SPARQL materializes isotone relationships between atoms using the\nChEMROF:isotone_of relationship.
\nINSERT {\n ?x rdfs:subClassOf [\n owl:onProperty ChEMROF:isotone_of;\n owl:someValuesFrom ?y\n ] .\n}\nWHERE {\n ?x rdfs:subClassOf [\n owl:onProperty ChEMROF:neutron_number;\n owl:hasValue ?value\n ] .\n ?y rdfs:subClassOf [\n owl:onProperty ChEMROF:neutron_number;\n owl:hasValue ?value\n ] .\n FILTER(?x != ?y)\n}\nIsobars are atoms of\ndifferent elements with the same number of nucleons. They can be produced, e.g.,\nthrough the process of beta decay.\nFor example, nitrogen-15 (CHEBI:36934) and\noxygen-15 (CHEBI:36932) are isobars with\nthe same nucleon number of 15.
\nThe following SPARQL materializes isobar relationships between atoms using the\nChEMROF:nucleon_number\nrelationship.
\nINSERT {\n ?x rdfs:subClassOf [\n owl:onProperty ChEMROF:isobar_of;\n owl:someValuesFrom ?y\n ] .\n}\nWHERE {\n ?x rdfs:subClassOf [\n owl:onProperty ChEMROF:nucleon_number;\n owl:hasValue ?value\n ] .\n ?y rdfs:subClassOf [\n owl:onProperty ChEMROF:nucleon_number;\n owl:hasValue ?value\n ] .\n FILTER(?x != ?y)\n}\nWhile I exhausted the current ChEMROF predicates, there still remain a few that\nI found while reading up on Wikipedia:
\nIsodiaphers are atoms\nwith equal neutron excess (i.e., neutron number minus atomic number). They can\nbe produced, e.g., through the process of\nalpha decay. For example,\ncarbon-13 (CHEBI:36928),\nnitrogen-15 (CHEBI:36934), and\noxygen-17 (CHEBI:33819) are isodiaphers\nwith a neutron excess of 1. I made a\npull request to ChEMROF to add this\nrelationship - after some discussion, I might also include an additional SPARQL\nquery.
\nMirror nuclei are atoms whose\nneutron numbers and atomic numbers are swapped. They can be produced, e.g.,\nthrough the process of\npositron emission. For\nexample, tritium (CHEBI:29238) and\nhelium-3 (CHEBI:30218) are mirror nuclei.
","doi":"https://doi.org/10.59350/8sztc-csq48","guid":"https://cthoyt.com/2026/09/24/chebi-nuclides","language":"en","license":"https://creativecommons.org/licenses/by/4.0/legalcode","published_at":1790208000,"rid":"ts8h5-vpr83","summary":"This post describes how I extended the work in my previous post that axiomatizes neutron numbers and nucleon numbers for isotopes that appear in ChEBI as children of atom terms, then materializes isotope (same atomic number), isotone (same neutron number), and isobar (same nucleon number) relationships between them.","tags":["ChEBI","Chemistry","Ontology","Biocuration"],"title":"Axiomatizing Nuclides in ChEBI","updated_at":1790321407,"url":"https://cthoyt.com/2026/09/24/chebi-nuclides.html","version":"v1"},{"authors":[{"contributor_roles":[],"family":"Singson","given":"Lea"}],"blog":{"authors":[{"name":"Redaktion iRights.info"}],"community_id":"7d3b25fd-a4a8-4155-8e76-99d6be06706a","created":1694736000,"current_feed_url":null,"description":"Urheberrecht und kreatives Schaffen in der digitalen Welt","doi":"https://doi.org/10.59350/irights","favicon":"https://rogue-scholar.org/api/communities/7d3b25fd-a4a8-4155-8e76-99d6be06706a/logo","feed_format":"application/atom+xml","feed_url":"https://irights.info/feed/atom","filter":null,"generator":"Other","home_page_url":"https://irights.info/","issn":null,"language":"deu","license":"https://creativecommons.org/licenses/by/4.0/legalcode","prefix":"10.59350","relative_url":null,"secure":true,"slug":"irights","status":"active","subfield":"3308","title":"iRights.info","updated":1790255863,"use_api":false},"blog_name":"iRights.info","blog_slug":"irights","content_html":"Wie lizenziert man OERs, wenn diese aus so genanntem \"gemischtem Material\" mit KI-Anteil bestehen? Und wann haben solche Inhalte urheberrechtliche Relevanz? Mehr dazu hier:
\n\n
K\u00fcnstliche Intelligenz unterst\u00fctzt Schaffende auch bei der Erstellung von OERs in variablem Umfang. H\u00e4ufig entstehen dabei so genannte \"gemischte Materialien\". Damit gemeint sind Materialien, die entweder aus einer Zusammenstellung von KI-generierten und pers\u00f6nlich erstellten Elementen bestehen oder aus einem Inhalt, f\u00fcr dessen Erstellung KI und Mensch zusammenwirken. Je nachdem, wie das gemischte Material beschaffen ist, gibt es dabei in Bezug auf die Lizenzierbarkeit und die Kennzeichnung des KI-Dienstes verschiedene Aspekte zu beachten.
\nBei gemischten Materialien ist zwischen Inhalten mit trennbaren Elementen und Inhalten mit einem Hauptelement mit zwei Erstellungsmethoden zu unterscheiden:
\nVerfasst eine Autorin f\u00fcr einen Online-Artikel beispielsweise einen Text und f\u00fcgt diesem ein KI-generiertes Titelbild hinzu, handelt es sich bei der Kombination aus Text und Bild um ein gemischtes Material, wobei das Bild und der Text dabei zwei voneinander trennbare Elemente sind.
\nL\u00e4sst die Autorin den Text selbst teilweise mit KI erstellen und verfasst ihn teilweise selbst, liegt mit dem Text ein Hauptelement mit zwei Erstellungsmethoden vor.
\nDa ein urheberrechtlicher Schutz \u2013 und damit auch eine Lizenzierung mit CC BY \u2013 eine pers\u00f6nliche geistige Sch\u00f6pfung voraussetzt, sind KI-generierte Materialien mangels menschlicher Sch\u00f6pfung nicht schutz- und lizenzierf\u00e4hig. KI-Output ist damit von sich aus gemeinfrei bzw. \"open\".
\nPrompt versus pers\u00f6nliche geistige Sch\u00f6pfung
\nKI-Outputs werden durch das Eingeben eines Befehls, eines so genannten Prompts, erzeugt. Eine pers\u00f6nliche geistige Sch\u00f6pfung setzt voraus, dass eine Person ein Werk durch eigene kreative, individuelle Entscheidungen formt. Da ein Prompt als Steuerung eines technischen Systems zu verstehen und rein anweisend ist, erf\u00fcllt er nicht die Voraussetzung einer pers\u00f6nlichen geistigen Sch\u00f6pfung.
\nIn der Praxis wird der Output nach dem Prompt h\u00e4ufig noch verfeinert. In so einem Fall kann es urheberrechtlichen Schutzf\u00e4higkeit des Prompts kommen, wenn der kreative Beitrag der Erstellerin st\u00e4rker hervortritt, als die KI-generierten Inhalte. Mehr dazu hier.
\nHier gilt Unterschiedliches, je nachdem, ob es sich um Inhalte mit trennbaren oder untrennbaren Elementen handelt.
\n1. Inhalte mit trennbaren Elementen
\nDa die KI-generierten Inhalte naturgem\u00e4\u00df gemeinfrei sind, sollten diese mit einem Public Domain Mark versehen werden. Die selbst erstellten, urheberrechtlich gesch\u00fctzten Inhalte k\u00f6nnen lizenziert werden. Damit der Inhalt als OER genutzt werden kann, empfiehlt sich die Lizenzierung mit der CC BY 4.0-Lizenz. Soll das gemischte Material einheitlich lizenziert werden, empfiehlt sich die CC0-Lizenz. Da diese Lizenz die lizenzierten Inhalte in die Gemeinfreiheit entl\u00e4sst, eignet sie sich auch zur Kennzeichnung von vornherein gemeinfreien Inhalten. Genaueres dazu hier.
\n2. Inhalte mit einem Hauptelement
\nBei Inhalten, die aus einem Hauptelement bestehen, durch die Mischung aus KI-Generierung und pers\u00f6nlichem Schaffen entstanden sind und bei denen der Schwerpunkt der Erstellung im pers\u00f6nlichen Schaffen liegt, kann der Inhalt insgesamt mit einer Lizenz wie der CC BY 4.0-Lizenz versehen werden. Liegt der Schwerpunkt in der KI-Generierung, ist der Inhalt insgesamt als gemeinfrei zu kennzeichnen. In beiden F\u00e4llen kann auch hier eine CC0 Lizenz verwendet werden.
\nIm Kontext der KI-Verordnung hat die EU-Kommission j\u00fcngst einen Verhaltenskodex f\u00fcr die Kennzeichnung von KI-Inhalten ver\u00f6ffentlicht. In diesem Leitfaden finden sich auch Vorschl\u00e4ge f\u00fcr KI-Kennzeichnungs-Symbole, die hier n\u00e4her dargestellt werden. Auch wer individuelle OER-Materialien erstellt, kann hieraus Orientierungshilfen f\u00fcr die KI-Kennzeichnung ableiten. Generell empfiehlt es sich bei der Erstellung von OER-Materialien mit KI den verwendeten KI-Dienst zu nennen. Dar\u00fcber hinaus sollten Erstellende darstellen, wof\u00fcr KI genau verwendet wurde und der Prompt sollte allgemein beschrieben werden. Bei Materialien mit trennbaren Anteilen bietet sich die Kennzeichnung so nah am KI-Inhalt wie m\u00f6glich an (beim Text-Bild-Beispiel also direkt unter dem Bild). Bei Materialien mit einem Hauptelement kann der Hinweis unter dem Inhalt erfolgen.
\nHinweis: Dieser Beitrag ist Teil einer Kooperation von\u00a0iRights.info, dem\u00a0Deutschen Bildungsserver\u00a0und\u00a0OERinfo. Der Text stammt von Lea Singson, steht unter der Lizenz CC BY 4.0\u00a0und wurde zun\u00e4chst bei\u00a0OERinfo\u00a0ver\u00f6ffentlicht.
\niRights.info\u00a0informiert und erkl\u00e4rt rund um das Thema \"Urheberrecht und Kreativit\u00e4t in der digitalen Welt\". Alle Texte erscheinen kostenlos und offen lizenziert.
\nWenn Sie m\u00f6gen, k\u00f6nnen Sie uns \u00fcber die\u00a0gemeinn\u00fctzige\u00a0Spendenplattform Betterplace\u00a0unterst\u00fctzen und daf\u00fcr eine Spendenbescheinigung erhalten. Betterplace akzeptiert PayPal, Bankeinzug, Kreditkarte, paydirekt oder \u00dcberweisung.
\nBesonders freuen wir uns \u00fcber einen regelm\u00e4\u00dfigen Beitrag, beispielsweise als monatlicher Dauerauftrag.\u00a0F\u00fcr Ihre Unterst\u00fctzung dankt Ihnen herzlich der\u00a0gemeinn\u00fctzige iRights e.V.!
\nDOI f\u00fcr diesen Text: https://doi.org/10.59350/p3anr-8y918\u00a0\u00b7 automatische DOI-Vergabe f\u00fcr Blogs \u00fcber The Rogue Scholar
\nThe post Die Mischung macht's: Kennzeichnung und Lizenzierung von Materialien mit KI-Anteil appeared first on iRights.info.
","doi":"https://doi.org/10.59350/p3anr-8y918","guid":"https://irights.info/?post_type=custom_artikel&p=32904","language":"de","license":"https://creativecommons.org/licenses/by/4.0/legalcode","published_at":1790208000,"rid":"3n4fc-x2226","summary":"Wie lizenziert man OERs, wenn diese aus so genanntem \"gemischtem Material\" mit KI-Anteil bestehen? Und wann haben solche Inhalte urheberrechtliche Relevanz? Mehr dazu hier: K\u00fcnstliche Intelligenz unterst\u00fctzt Schaffende auch bei der Erstellung von OERs in variablem Umfang.","tags":["Bildung + OER","Creative Commons + Lizenzen","Generative KI","Grundwissen","Urheberrecht"],"title":"Die Mischung macht's: Kennzeichnung und Lizenzierung von Materialien mit KI-Anteil","updated_at":1790321406,"url":"https://irights.info/artikel/gemischtes-material-ki/32904","version":"v1"},{"authors":[{"affiliation":[{"id":"https://ror.org/04xfq0f34","name":"RWTH Aachen University"}],"contributor_roles":[],"family":"Hoyt","given":"Charles Tapley","url":"https://orcid.org/0000-0003-4423-4370"}],"blog":{"authors":null,"community_id":"da4ef2af-5fad-46b2-8195-d77db0141ad6","created":1716422400,"current_feed_url":null,"description":"Unraveling complex biology with biological knowledge graphs. Content licensed under CC BY 4.0.","doi":"https://doi.org/10.59350/cthoyt","favicon":"https://rogue-scholar.org/api/communities/da4ef2af-5fad-46b2-8195-d77db0141ad6/logo","feed_format":"application/atom+xml","feed_url":"https://cthoyt.com/feed.xml","filter":null,"generator":"Jekyll","home_page_url":"https://cthoyt.com/","issn":null,"language":"eng","license":"https://creativecommons.org/licenses/by/4.0/legalcode","prefix":"10.59350","relative_url":null,"secure":true,"slug":"cthoyt","status":"active","subfield":"1312","title":"Biopragmatics","updated":1790250300,"use_api":null},"blog_name":"Biopragmatics","blog_slug":"cthoyt","content_html":"A resolver is a web application that returns a redirect response for the uniform\nresource identifier (URI) expansion of a compact URI (CURIE). This post\ndemonstrates the resolver implemented as part of the\ncuries Python package, which is\nused by the Bioregistry and\nSemantic Farm.
I actually wrote the first version of this post in 2023 as I started\nexternalizing functionality from the bioregistry that could be made more\ngeneric. At the time, there were already several other resolvers (sometimes\ncalled meta-resolvers):
.htaccess rulesHowever, there are issues here with transparency, easy of configuration, and\nextensibility. I had already begun writing about the curies package as a\nfinal implementation of CURIE and URI conversion logic in a previous post on the curies package.
The following is an end-to-end example of using this function to create a small\nweb resolver application. This uses a flask.Blueprint which allows the\nresolver to be mounted on any pre-existing Flask application.
# flask_example.py\nfrom flask import Flask\nfrom curies import Converter, get_obo_converter\nfrom curies.resolver_service import get_flask_blueprint\n\n# Create a converter\nconverter: Converter = get_obo_converter()\n\n# Create a blueprint from the converter\nblueprint = get_flask_blueprint(converter)\n\n# Create the Flask app and register the blueprint\napp = Flask(__name__)\napp.register_blueprint(blueprint)\n\nif __name__ == \"__main__\":\n app.run()\nIf you don't need the flexibility of mounting on a pre-existing application, you\ncan use the curies.get_flask_app as a shortcut.
# flask_example.py\nfrom flask import Flask\nfrom curies import get_obo_converter, Converter\nfrom curies.resolver_service import get_flask_app\n\n# Create a converter\nconverter: Converter = get_obo_converter()\n\n# Create the Flask app and register the blueprint\napp: Flask = get_flask_app(converter)\n\nif __name__ == \"__main__\":\n app.run()\nIn the command line, either run your Python file directly, or via with\ngunicorn:
$ uvx gunicorn --bind 0.0.0.0:5000 flask_example:app\nTest a request in the Python REPL. Note that Flask's development server runs on\nport 5000 by default.
\n>>> import requests\n>>> requests.get(\"http://localhost:5000/GO:0032571\").url\n'http://amigo.geneontology.org/amigo/term/GO:0032571'\nThe same thing works for FastAPI applications, except with a fastapi.Router:
# fastapi_example.py\nfrom fastapi import FastAPI\nfrom curies.resolver_service import get_fastapi_router\nfrom curies import Converter, get_obo_converter\n\n# Create a converter\nconverter: Converter = get_obo_converter()\n\n# Create a router from the converter\nrouter = get_fastapi_router(converter)\n\n# Create the app and mount the router\napp = FastAPI()\napp.mount(router)\n\nif __name__ == \"__main__\":\n app.run()\nIf you don't need the flexibility of mounting on a pre-existing application, you\ncan use the curies.get_flask_app as a shortcut.
# fastapi_example.py\nfrom fastapi import FastAPI\nfrom curies import get_obo_converter, Converter\nfrom curies.resolver_service import get_fastapi_app\n\n# Create a converter\nconverter: Converter = get_obo_converter()\n\n# Create the Flask app and mount the router\napp: FastAPI = get_fastapi_app(converter)\n\nif __name__ == \"__main__\":\n import uvicorn\n\n uvicorn.run(app)\nIn the command line, either run your Python file directly, or via with\ngunicorn:
$ uvicorn --bind 0.0.0.0:5000 fastapi_example:app\nThere's a high-level CLI built in to the curies package that can be pointed at\na given local or remove prefix map, extended prefix map, or JSON-LD context to\nmake a resolver:
$ uvx \\\n --with click \\\n --with flask \\\n curies resolver\n --format prefix_map \\\n https://prefix.zazuko.com/api/v1/prefixes\nInstalled 15 packages in 11ms\n * Serving Flask app 'curies.resolver_service'\n * Debug mode: off\nWARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.\n * Running on all addresses (0.0.0.0)\n * Running on http://127.0.0.1:8764\n * Running on http://192.168.2.118:8764\nPress CTRL+C to quit\nFlags can be used to toggle the implementation (FastAPI or Flask) and the server\n(werkzeug, gunicorn, uvicorn). See --help for more information.