"Daniel Mietchen" . . "RSA" . . "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCW+VopfbAsAusLtasUe5QnVQL4ovdEXZRd7/44ZfSOuSYBr9BOFBxBoxBpfdCij85m1UHz3Dvb9YLSfx8oSyhdGhBFO4m6zimJ1hpnHQe5jA1cvF6PRYznWgQAhwC4RaYhZJ4MkzVMxXmWTI+8hYRn4oC2+qsg7DJjiS+cttD3tQIDAQAB" . . "RSA" . . "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDnA5FgUmM9Mx3uUIhTFTGdA9fNVO+AexL03qaWYQ60KOCHjE/XaI+Z74fCyMzXkzsfl5eqTtfi72Gr4Ws6I+Q3dfkV/B4LFbw7N9xphn4qemizfEho8z1Asz/C9octC6X3o+MPpfOgM119YhZAGSMAVY2x+nSw9qVXAnSnBIAXOQIDAQAB" . . "RSA" . "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCTdrjHE05mWzJPiHs4goY9HN9AYf2BWYdsPbcKwtRZQP3t+ZrdRv/YX7kMvWDsdrRtAYMm/1xpfor45o2iASPOoQut/QT/kspp5X1UFjwCkAW0s4N2Jr7WInnc6S1YONO3KFhmrnf2U12Tz6vRoPoCxR/clP7FJPQqnYW3ywFqFwIDAQAB" . . "RSA" . . "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDnA5FgUmM9Mx3uUIhTFTGdA9fNVO+AexL03qaWYQ60KOCHjE/XaI+Z74fCyMzXkzsfl5eqTtfi72Gr4Ws6I+Q3dfkV/B4LFbw7N9xphn4qemizfEho8z1Asz/C9octC6X3o+MPpfOgM119YhZAGSMAVY2x+nSw9qVXAnSnBIAXOQIDAQAB" . "Daniel Mietchen" . . "RSA" . "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCTdrjHE05mWzJPiHs4goY9HN9AYf2BWYdsPbcKwtRZQP3t+ZrdRv/YX7kMvWDsdrRtAYMm/1xpfor45o2iASPOoQut/QT/kspp5X1UFjwCkAW0s4N2Jr7WInnc6S1YONO3KFhmrnf2U12Tz6vRoPoCxR/clP7FJPQqnYW3ywFqFwIDAQAB" . "Daniel Mietchen" . "Codeberg" . . . "Google Scholar" . "Mastodon" . . "Personal page at FIZ Karlsruhe" . . . "Wikidata user page" . . . "The ongoing saga with the Wikidata graph split stimulates thoughts about alternative setups for initiatives that depend on the full graph, e.g. WikiCite and Scholia." . . "2026-05-16"^^ . "WikiCite and Scholia as nanopublications" . . . "Some of the scenarios that the authors are considering: \"Examples include IoT sensor networks, activity feeds (cfr. ActivityPub), knowledge graph updates, benchmark stream distribution [7], Trustflows [2], Nanopublications [4], or returning multiple results when evaluating SPARQL CONSTRUCT queries.\" - several of these are well within my own research interests." . . "2026-05-16"^^ . "Interesting paper \"It's Time to Standardize RDF Messages\"" . . . . . . . . . . . . . . . . . . . . . . . . . . . . "Amplification of computational power by the multiplication of bacteria exploring microfluidic networks encoding mathematical problems" . . . "2026-08-17" . . "A fascinating combination of things I am interested in - letting bacteria grow and migrate in a microfluidic network structured such that counting bacteria on one end means getting a solution to a computationally hard mathematical problem." . "Modeling the Probability of Tsunami Fire Ignition Based on Data From the 2011 Tohoku and 2024 Noto Peninsula Earthquakes, With Recommendations to Reduce Emerging Fire Risk in Tsunami Vertical Evacuation Structures" . . . "2026-08-17" . . "Uses data from recent tsunamis in Japan to consider and model risks due to tsunami-related fires as well as protective measures in terms of building design and evacuation measures." . "Upper (1974)" . . . "2026-07-17" . . "It stimulates thoughts about what a basic unit of publishing might look like, and much of it resembles a nanopublication: There is an assertion (the blank page), along with provenance information (unsucessful treatment of writer's block, as per the title), and there is bibliographic metadata (Dennis Upper (1974) The unsuccessful self-treatment of a case of ‘writer's block’. Journal of Applied Behavior Analysis, 7:497.). The footnote and the review could in principle each be a separate nanopublication." . "Soejarto et al. 2026" . . . "2026-06-09" . . "A useful dive into taxonomic errors in the phytochemical literature." . "Clark et al. 2026" . . . "2026-06-09" . . "This paper presents seven principles of AI-readiness for (biomedical) datasets." . "Hoàng et al. 2026 - The Power of Agency: How Interactivity in Data Storytelling Influences Emotional Engagement and Perceived Trustworthiness in News Context" . . . "2026-05-18" . . "There are currently two issues with this: (1) the DOI has not been activated, so the article is only available via the DOI-containing publisher URL https://www.frontiersin.org/journals/computer-science/articles/10.3389/fcomp.2026.1843009 (2) only the abstract is available, accompanied by a note that states \"The final, formatted version of the article will be published soon.\"" . "Southan 2020 - Opening up connectivity between documents, structures and bioactivity" . . . "2026-01-23" . . "has a logical error: \"of the 62000 papers curated by ChEMBL in EPMC only 85000 are full-text and only 600 OA\"" . "A dataset comprising 141 magnetic resonance imaging scans of 98 extant sea urchin species" . . . . . "See my review report in the \"Supplementary data\" section." . . "It would be useful to have a mechanism for creating spaces for upcoming shindings of recurring events (e.g. NanoSessions or Office Hours) well ahead of the event, in a consistent and perhaps crowdsourced fashion." . . . . "System for creating recurring event spaces ahead of time" . . . "An independent replication (using independent data) of a figure on global-mean marine heatwave days over multiple years." . "Story: Longer and more frequent marine heatwaves — independently confirmed" . . "After the July 2026 update of the IUCN Red List, it \"now includes 175,909 species, of which 49,505 are threatened with extinction.\"" . "IUCN Redlist update July 2026" . . . . "What mechanisms exist for the long-term preservation of nanopublications?" . "This text will hopefully be replaced by a useful answer soon." . . . . "How do nanopublications relate to the Diamond Open Access system?" . "This text will hopefully be replaced by a useful answer soon." . . . . "How can I link to an individual question on this FAQ page?" . "This text will hopefully be replaced by a useful answer soon." . . . . . . . "This is one of the weekly office hours of the Knowledge Pixels incubators." . "2026-08-19T15:00:00.0+02:00"^^ . "2026-08-19T14:00:00.0+02:00"^^ . "Office Hour 19 August 2026" . . . . . "Daniel Mietchen" . . "RSA" . . "MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4xK1hdyblk7RVB/WxbUiDxe8ZUEv46YhdGLlJn9UqGCALb3lUBEcr4i4X8yzAdP59aqjepCuJ4Pmo4/ljmkRCVh3WEowMP4JcS5cIM69Dfp5ZsgDhmOLuUeB1JyarwSEXDOyXPO01V1Da3IfH3YXR2rDflrckEdlh1LQJ1+j9oQUYjfhPYPOOyvN4aBt87KrEri473INIjIfno7HO2i+Yy8N0Vn6n7FHvnUta4se8CtWihh3FA27MrGDXKPWtzoIFzyMX9ZBr13g6GbV4/N08KJrNGVBXl1ZMgxflxEwi7RbW+clHarn9xGYzBgaRo40XA8PE3QoOQi5wPWMYdYpqQIDAQAB" . "In the \"Use cases\" listing, the entries for \"Recently read papers\" and \"Query: Get thanks\" do not currently work. I suspect this is because of escaping related to HTML/ URL formatting." . . . . . . . "In the \"Use cases\" listing, the entries for \"Recently read papers\" and \"Query: Get thanks\" do not currently work. I suspect this is because of escaping related to HTML/ URL formatting." . . . . "A set of papers that have been declared to have been read, aggregated across multiple readers." . "Recently read papers" . . "Examples of nanopublications expressing gratitude." . "Query: Get thanks" . "Perhaps we should have a space dedicated to collecting papers, blog posts and other materials about nanopublications. Such a resource could assists in welcoming newcomers to the nanopublication system by giving them introductory (and ideally perhaps third-party) perspectives on it." . . . . . . "The paper reporting about the first observation of gravitational waves includes an acknowledgment section of over 300 words that lists dozens of organisations from around the globe." . . "The authors gratefully acknowledge the support of the United States National Science Foundation (NSF) for the construction and operation of the LIGO Laboratory and Advanced LIGO as well as the Science and Technology Facilities Council (STFC) of the United Kingdom, the Max-Planck Society (MPS), and the State of Niedersachsen, Germany, for support of the construction of Advanced LIGO and construction and operation of the GEO 600 detector. Additional support for Advanced LIGO was provided by the Australian Research Council. The authors gratefully acknowledge the Italian Istituto Nazionale di Fisica Nucleare (INFN), the French Centre National de la Recherche Scientifique (CNRS), and the Foundation for Fundamental Research on Matter supported by the Netherlands Organisation for Scientific Research, for the construction and operation of the Virgo detector, and for the creation and support of the EGO consortium. The authors also gratefully acknowledge research support from these agencies as well as by the Council of Scientific and Industrial Research of India, Department of Science and Technology, India, Science & Engineering Research Board (SERB), India, Ministry of Human Resource Development, India, the Spanish Ministerio de Economía y Competitividad, the Conselleria d’Economia i Competitivitat and Conselleria d’Educació, Cultura i Universitats of the Govern de les Illes Balears, the National Science Centre of Poland, the European Commission, the Royal Society, the Scottish Funding Council, the Scottish Universities Physics Alliance, the Hungarian Scientific Research Fund (OTKA), the Lyon Institute of Origins (LIO), the National Research Foundation of Korea, Industry Canada and the Province of Ontario through the Ministry of Economic Development and Innovation, the Natural Sciences and Engineering Research Council of Canada, Canadian Institute for Advanced Research, the Brazilian Ministry of Science, Technology, and Innovation, Russian Foundation for Basic Research, the Leverhulme Trust, the Research Corporation, Ministry of Science and Technology (MOST), Taiwan, and the Kavli Foundation. The authors gratefully acknowledge the support of the NSF, STFC, MPS, INFN, CNRS and the State of Niedersachsen, Germany, for provision of computational resources. This article has been assigned the document numbers LIGO-P150914 and VIR-0015A-16." . "ACKNOWLEDGMENTS" . "References (118)" . . . . "He was accompanied by one of his famous hats." . "Apparently, Napoleon was not alone in his coffin" . "Apparently, Napoleon was not alone in his coffin: \"Napoleon always had with him a set of twelve hats. Only four were taken to St Helena. The one presented here is one of those. On the Emperor’s death, one of them was placed in his coffin. Napoleon and his “little hat” rest together for eternity.\"" . . . . "Two species of snake have been documented in Jena, Thuringia, Germany." . "As of today, 14 observers have used iNaturalist to document 39 observations in Jena of what 57 users have identified as two species of snakes, the Grass Snake (Natrix natrix) and the Smooth Snake (Coronella austriaca)." . "As of today, 14 observers have used iNaturalist to document 39 observations in Jena of what 57 users have identified as two species of snakes, Grass Snake (Natrix natrix) and the Smooth Snake (Coronella austriaca)." . "The Q & A mechanics needs checking." . . . . "The GND record 103138900 mixes up two people: the priest and historian \"Johannes Kraus\" (Wikidata QID: Q140136465) who died around 1484 with the mathematician \"Johannes Karl Kraus\" (Wikidata QID: Q102405738) who co-authored the book \"Robust Algebraic Multilevel Methods and Algorithms\" that was published in 2009." . "The GND record 103138900 mixes up two people" . "In the current implementation of the \"Questions & answers\" display, it is irritating to have a \"Reply\" button next to the first-level reply. When I replied to such a first-level reply, my second-level reply got displayed as the (most recent) first-level reply. This should probably be disentangled a bit in terms of UI." . . . . "Are you sure?" . . . . . . . . . . . . "A website dedicated to sharing information about nanopublications." . "Nanopub.net" . . . . . . . . "Collaborative event taking place in Paris on 21-23 August 2026" . "2026-08-23T13:00:00.0+02:00"^^ . "2026-08-21T13:00:00.0+02:00"^^ . "GRADE Edit-a-thon" . . . . . . . . "Images obtained during the total lunar eclipse of September 16, 1997 suggest that there may have been an impact event. This requires independent verification." . "An impact during the total lunar eclipse of September 16, 1997?" . . "Crowdsourcing" . . . . . . "Quantum Computing for Biodiversity" . . "Documentation of the Nano Sessions, a series of events focused on nanopublications." . "Event documentation" . . "Data integration" . . . . "Interlinking" . . . . "Documentation" . . . . . . "Expressing gratitude" . . . . "Peer review" . . . . "Annotating existing resources" . . . . "Nanopublications FAQ" . . "Error reporting" . . . . "Sharing curation events" . . . . . "A common way of requesting information and responding to such requests." . "Asking and answering questions" . . . . "I'd like to review nanopub spaces for recent and upcoming events and to discuss options for improvements." . . "Streamlining of event spaces" . . . "Preparation of the tutorial as well as the nanopub space and any potential contributions to the proceedings." . . "Preparation of SEMANTiCS 2026" . . . "I'd like to continue exploring how someone can signal their availability as a peer reviewer, as discussed at last week's Office Hour." . . "Follow-up on Office Hour 5 August 2026" . . . . . . . . "We have a first nanopub using the \"I have reviewed X\" template." . . . . "We now have a first draft for \"I have reviewed X\"" . . . . "A simple starting point would be to adapt the \"I have read X\" nanopub template such that we get a new one that says \"I have reviewed Y\"." . . . . "- scientific expertise (topic/ methodology etc.)\r\n- review preferences (e.g. only open-access resources)\r\n- temporal aspects (e.g. recent reviewer load, current availability)\r\n\r\nThe third one is a bit privacy-sensitive, so we could perhaps start with the first two." . . "3 main components of a nanopub way to declare peer review preferences" . "Cross-disciplinary way to describe research fields" . . . . "I would like us to explore ways in which potential peer reviewers could express their preferences, availability etc. regarding peer review in a standardized and queriable fashion." . . "Declaring personal principles regarding availability as a peer reviewer" . . . . . . "Which stakeholders of the research ecosystem should host or mirror nanopublication servers?" . "This text will hopefully be replaced by a useful answer soon." . . "Let's review the space for the International Congress on Mathematical Software 2026." . . . "Review of ICSM space" . . "Maybe we should have a mechanism to have nanoalerts, e.g. notifications for new nanopublications meeting certain criteria." . . . . . . . . "It would be useful if Nanodash had more formal release mechanisms and in particular a staging setup separate from the production setup, so that new versions can be tested more thoroughly before being deployed." . . . "Nanodash should probably have a simple way to share screenshots, especially for bug reports." . . . . "In simple message displays, the default should be to not display nanopubs that have been overridden/ superseded/ retracted. This is not currently the case." . . . . "When a háček character is displayed in Nanodash, it usually points to the source of the underlying nanopub and optionally other templates for further actions. This recently changed, which causes trouble configuring new spaces properly." . . . . . "When a háček character is displayed in Nanodash, it usually points to the source of the underlying nanopub and optionally other templates for further actions. This recently changed, which causes trouble trouble configuring new spaces properly." . . . . . . . . . . . . . . . . . . . . "A place to report issues with the Nanodash software" . "Nanodash bug reports" . . . . "A scientific conference held in Waterloo (Ontario, Canada) on 20-23 July 2026." . "2026-07-23T18:00:00.0-04:00"^^ . "2026-07-20T09:00:00.0-04:00"^^ . "International Congress on Mathematical Software 2026" . . . . . . . . . . "A retraction notice explaining that the article it refers to was initially published in the wrong journal, due to a publisher error." . . "This article has now been published in the correct journal" . "Due to a technical issue, this article from ‘‘Phytochemistry’’ was inadvertently published in ‘‘Phytochemistry Letters’’." . "(Phytochemistry, 117, September 2015, Pages 476–481)." . . . . "This hint was both necessary and sufficient to fix the formatting issue, and the explanation helped me understand the underlying mechanics a bit better." . . . . "OK, thanks for the hint. I think that if the nanopub was created via the \"add\" button from the \"Highlighting\" table, then setting \"highlighting\" as a default makes sense. If we let users change that, then there should perhaps be some warning that the result will not pop up in the \"Highlightings\" table." . . . "All references cited in the section \"2.1 Large language models and expert agents\" are amongst the 11 ones that are mentioned in the retraction notice for being non-existent." . . "LLMs, including OpenAI's GPT series and similar frameworks, have revolutionized the understanding and simulation of human-like expertise and decision-making processes. [..] although LLMs offer unparalleled opportunities, ensuring transparency and ethical use remains essential for their integration into expert-driven methodologies." . "2. Literature review" . "2.2. Delphi survey and technology evaluation" . . . . . . . "The template used for preparing nanopublications via the \"add\" button in the \"Highlighting\" table above should be reviewed. The example nanopublication created this way (a) does not show up in the table and (b) does not display the submitted content for target and selector." . . . . . . . "All references cited in the section \"2.1 Large language models and expert agents\" are amongst the 11 ones that are mentioned in the retraction notice for being non-existent." . . "LLMs, including OpenAI's GPT series and similar frameworks, have revolutionized the understanding and simulation of human-like expertise and decision-making processes. [..] although LLMs offer unparalleled opportunities, ensuring transparency and ethical use remains essential for their integration into expert-driven methodologies." . "2. Literature review" . "2.2. Delphi survey and technology evaluation" . . . . "Follow-up on use case discussion from yesterday's NanoSession 33" . . "Use cases" . . . "Workflows for handling nanorequests and nanosuggestions." . . . "Nanorequests" . . . . "As just briefly mentioned, I would be interested in using nanopubs to document the use of AI, e.g. by building a plugin to some open LLMs that would allow to record my prompts and the resulting responses and then assist in generating suitable FAIA (FAIR AI Attribution) statements." . . . "As just briefly mentioned, I would be interested in using nanopubs to document the use of AI, e.g. by building a plugin to some open LLMs that would allow to record my prompts and the resulting responses." . . "An example of an error in Crossref metadata." . . . "The main use cases I would like to bring up can be expressed in terms of two main dimensions: (1) steps and progress along the research process, (2) components of typical research outcomes.\r\n\r\nPotential other dimensions would be (3) mechanisms to integrate nanopublications with Diamond Open-Access publishing workflows, e.g. via OJS (Open Journal Systems) plugins or (4) mechanisms to keep track of chains of arguments.\r\n\r\nAd 1: Here, I am thinking of ideas, proposals, code, software, curation events, literature reviews and other things,\r\nAd 2: This could be things like footnotes, data/ software availability statements, ethics statements, funding statements, figure/table captions, errors and such - essentially anything that can represent manuscript components in a way similar to how tagging standards like JATS do it.\r\nAd 3: OJS has a rich ecosystem of plugins already, to which nanopublication-related ones could be added.\r\nAd 4: There is the Nanoarguments project, which goes in this direction." . . . . . . "The main use cases I would like to bring up can be expressed in terms of two main dimensions: (1) steps and progress along the research process, (2) components of typical research outcomes.\r\n\r\nPotential other dimensions would be (3) mechanisms to integrate nanopublications with Diamond Open-Access publishing workflows, e.g. via OJS (Open Journal Systems) plugins (40 mechanisms to keep track of chains of arguments.\r\n\r\nAd 1: Here, I am thinking of ideas, proposals, code, software, curation events, literature reviews and other things,\r\nAd 2: This could be things like footnotes, data/ software availability statements, ethics statements, funding statements, figure/table captions, errors and such - essentially anything that can represent manuscript components in a way similar to how tagging standards like JATS do it.\r\nAd 3: OJS has a rich ecosystem of plugins already, to which nanopublication-related ones could be added.\r\nAd 4: There is the Nanoarguments project, which goes in this direction." . . . . . . "contradicts" . . "Such a nanopublication expresses a contradiction." . "Expressing a contradiction" . . "Contradiction" . . . . . "URI of the initial statement that is contradicted by another statement" . . "URI of the statement that contradicts the initial statement" . "is a" . "has the comment" . . "Express thanks by one or more thankers to one or more thanked for one or more thanksReason, optionally with a comment" . "Express multiple thanks" . "${thanker} thanks ${thanked}" . . . . . . . "plain-text comment" . . . . . . . . . . . . . . . . . . . . . "choose who receives the thank you" . . "choose who gives the thank you" . . "this" . . "enter the reason URI" . "thanks" . "is giving thanks to" . "is from" . "thanks for" . . "Thanks you for chairing Nano Session #28!" . . . . . "Thanks for recording this important bit of info." . . . . . "Thank you for this fantastic nanopub :)" . . . .