new blog post: "FAIR blog-to-blog citations" https://doi.org/10.59350/er1mn-m5q69
"Linkrot is real and digital preservation problematic. One reason why I have started migrating my blog to a more robust platform. That first step gave me version control. This […]
[Original post on social.edu.nl]
"Linkrot is real and digital preservation problematic. One reason why I have started migrating my blog to a more robust platform. That first step gave me version control. This […]
[Original post on social.edu.nl]
December 30, 2024 at 9:27 PM
new blog post: "FAIR blog-to-blog citations" https://doi.org/10.59350/er1mn-m5q69
"Linkrot is real and digital preservation problematic. One reason why I have started migrating my blog to a more robust platform. That first step gave me version control. This […]
[Original post on social.edu.nl]
"Linkrot is real and digital preservation problematic. One reason why I have started migrating my blog to a more robust platform. That first step gave me version control. This […]
[Original post on social.edu.nl]
January 25, 2025 at 5:34 PM
very interesting use of @nanopub at #wikicite2025 with a template where people can claim (authenticated with @ORCID_Org!) they are participant. And that can then be used in @wikidata s reference (links in the alt texts)
August 31, 2025 at 4:18 PM
very interesting use of @nanopub at #wikicite2025 with a template where people can claim (authenticated with @ORCID_Org!) they are participant. And that can then be used in @wikidata s reference (links in the alt texts)
@tkuhn, meanwhile, any idea why nanodash says these two new nanopubs and the template are "retracted"?
December 29, 2024 at 1:05 PM
@tkuhn, meanwhile, any idea why nanodash says these two new nanopubs and the template are "retracted"?
Say hi to our first customer! 🎉 We are partnering with Knowledge Pixels to help them scale the #Nanopublication network with NeverBlink’s streaming KG tech Jelly. 💪
We went down from dozens of minutes to retrieve 60k nanopubs to less than 4 seconds. ⌚
We went down from dozens of minutes to retrieve 60k nanopubs to less than 4 seconds. ⌚
April 23, 2025 at 2:40 PM
Say hi to our first customer! 🎉 We are partnering with Knowledge Pixels to help them scale the #Nanopublication network with NeverBlink’s streaming KG tech Jelly. 💪
We went down from dozens of minutes to retrieve 60k nanopubs to less than 4 seconds. ⌚
We went down from dozens of minutes to retrieve 60k nanopubs to less than 4 seconds. ⌚
🚀 Speeding up RDF communications! Piotr Sowiński, Tobias Kuhn & Karolina Bogacka tackle inter-service bottlenecks in the Nanopublication network with Jelly at #SEMANTiCS2025.
#RDF #Nanopublications #SemanticWeb #KnowledgeGraphs
#RDF #Nanopublications #SemanticWeb #KnowledgeGraphs
September 5, 2025 at 9:29 PM
🚀 Speeding up RDF communications! Piotr Sowiński, Tobias Kuhn & Karolina Bogacka tackle inter-service bottlenecks in the Nanopublication network with Jelly at #SEMANTiCS2025.
#RDF #Nanopublications #SemanticWeb #KnowledgeGraphs
#RDF #Nanopublications #SemanticWeb #KnowledgeGraphs
Is anyone working on implementing decentralized knowledge graphs with #atproto? This would be amazing for research synthesis and sensemaking.
eg extending the Post class to something like a “SemanticPost” with a payload of RDF triplets (based on the nanopublication spec nanopub.net) @atproto.com
eg extending the Post class to something like a “SemanticPost” with a payload of RDF triplets (based on the nanopublication spec nanopub.net) @atproto.com
November 27, 2024 at 9:32 PM
Is anyone working on implementing decentralized knowledge graphs with #atproto? This would be amazing for research synthesis and sensemaking.
eg extending the Post class to something like a “SemanticPost” with a payload of RDF triplets (based on the nanopublication spec nanopub.net) @atproto.com
eg extending the Post class to something like a “SemanticPost” with a payload of RDF triplets (based on the nanopublication spec nanopub.net) @atproto.com
Oh! Here at the #isc25 I noticed, I got my first #nanopub PR merged: https://github.com/Nanopublication/nanopub-py/pull/193 🥳
#ReproducibleResearch
#ReproducibleResearch
fix: introducing return values for publish() by cmeesters · Pull Request #193 · Nanopublication/nanopub-py
motivation: Whilst the publish() method logs URI and server for a terminal user to read, programmatically there is no way to get hold of these values. Hence, they ought to be returned, too. Otherwi...
github.com
June 12, 2025 at 1:47 PM
Oh! Here at the #isc25 I noticed, I got my first #nanopub PR merged: https://github.com/Nanopublication/nanopub-py/pull/193 🥳
#ReproducibleResearch
#ReproducibleResearch
Test 1: article to software release
https://w3id.org/np/RAzmTPPM7v5Ilgvo-3aFRRZgdD3ImaUB434NtGlfI0G90
https://doi.org/10.1021/acs.jcim.2c00268 is an article that uses a specific version of Bacting, version 0.0.31, which is archived on Zenodo with the DOI https://doi.org/10.5281/zenodo.5839734
https://w3id.org/np/RAzmTPPM7v5Ilgvo-3aFRRZgdD3ImaUB434NtGlfI0G90
https://doi.org/10.1021/acs.jcim.2c00268 is an article that uses a specific version of Bacting, version 0.0.31, which is archived on Zenodo with the DOI https://doi.org/10.5281/zenodo.5839734
December 29, 2024 at 12:54 PM
Test 1: article to software release
https://w3id.org/np/RAzmTPPM7v5Ilgvo-3aFRRZgdD3ImaUB434NtGlfI0G90
https://doi.org/10.1021/acs.jcim.2c00268 is an article that uses a specific version of Bacting, version 0.0.31, which is archived on Zenodo with the DOI https://doi.org/10.5281/zenodo.5839734
https://w3id.org/np/RAzmTPPM7v5Ilgvo-3aFRRZgdD3ImaUB434NtGlfI0G90
https://doi.org/10.1021/acs.jcim.2c00268 is an article that uses a specific version of Bacting, version 0.0.31, which is archived on Zenodo with the DOI https://doi.org/10.5281/zenodo.5839734
and with that, we also gained 3 new nanopublication, with the oldest discussed articles now in 1977 and 1978. More here: https://scholia.toolforge.org/cito/
June 22, 2025 at 10:19 AM
and with that, we also gained 3 new nanopublication, with the oldest discussed articles now in 1977 and 1978. More here: https://scholia.toolforge.org/cito/
Iolanta, my α console #linked-data browser, can (well, is trying to) visualize #nanopublication docs. Installing on Python 3.10+ & Ubuntu:
pip install iolanta
Running:
iolanta purl.org/np/RAYskLSM5...
…and click the orange block.
pip install iolanta
Running:
iolanta purl.org/np/RAYskLSM5...
…and click the orange block.
January 4, 2025 at 12:58 PM
Iolanta, my α console #linked-data browser, can (well, is trying to) visualize #nanopublication docs. Installing on Python 3.10+ & Ubuntu:
pip install iolanta
Running:
iolanta purl.org/np/RAYskLSM5...
…and click the orange block.
pip install iolanta
Running:
iolanta purl.org/np/RAYskLSM5...
…and click the orange block.
@rupdecat 1. citation -> yes, I understand. in the future I can imagine other things to be cited too
2. what I fixed for the creator was that it just had a literal (string) as value. That cannot be linked to the creator of the nanopublication, as String matching doesn't generally work. so, you […]
2. what I fixed for the creator was that it just had a literal (string) as value. That cannot be linked to the creator of the nanopublication, as String matching doesn't generally work. so, you […]
Original post on mastodon.social
mastodon.social
August 30, 2025 at 3:16 PM
@rupdecat 1. citation -> yes, I understand. in the future I can imagine other things to be cited too
2. what I fixed for the creator was that it just had a literal (string) as value. That cannot be linked to the creator of the nanopublication, as String matching doesn't generally work. so, you […]
2. what I fixed for the creator was that it just had a literal (string) as value. That cannot be linked to the creator of the nanopublication, as String matching doesn't generally work. so, you […]