#Tag
@cwebber @eyeinthesky @smallcircles @evan Apart from the fact that I would prefer turtle, I am very happy that AP ‘prescribes’ json-ld. This opens the door to many of my ideas. It makes possible what would be very complicated without #RDF. It's about time that the AP developers got to grips with it! https://rdf-pub.org/#rdf
@eyeinthesky @smallcircles @evan To be clear, I think json-ld has a lot of great ideas in it, and it's the extensibility and linked data compatibility (which was a strong group requirement) story we had at the time.
"JSON-LD is bad" doesn't really capture my views. "JSON-LD turned out to be too complicated for the majority of the ecosystem to work with, particularly when we gave the view that you could ignore it, except it creates a rift of interoperability between those who ignore it and those who don't and puts a burden on the latter who are doing their best to behave well" does match my views.
There are paths out of the situation, but I'm not confident in the discourse around them right now, and hesitant about how much I want to engage with it.
@cwebber @eyeinthesky @smallcircles @evan Apart from the fact that I would prefer turtle, I am very happy that AP ‘prescribes’ json-ld. This opens the door to many of my ideas. It makes possible what would be very complicated without #RDF. It's about time that the AP developers got to grips with it! https://rdf-pub.org/#rdf
I suspect that there is an error in the Turtle specification, in the section shown in the screen-shot.
(It relates to JSON-LD, which ActivityPub / ActivityStreams is built on.)
I suspect that "PN_CHARS_BASE" is an error.
Because other parts of other specifications seem to not make sense if it is.
I suspect that maybe it should have been "PN_PREFIX" instead.
WikiPathways RDF IRIs are now dereferenceable! Every http://rdf.wikipathways.org/ identifier now resolves via HTTP with content negotiation: HTML for browsers, Turtle/JSON-LD/RDF-XML/N-Triples for machines.
Try it: click any IRI on the about page, or curl one with an Accept header.
https://rdf.wikipathways.org/about
https://github.com/wikipathways/wikipathways-iri-resolver
#LinkedData #FAIR #WikiPathways #RDF #Bioinformatics #SemanticWeb
WikiPathways RDF IRIs are now dereferenceable! Every http://rdf.wikipathways.org/ identifier now resolves via HTTP with content negotiation: HTML for browsers, Turtle/JSON-LD/RDF-XML/N-Triples for machines.
Try it: click any IRI on the about page, or curl one with an Accept header.
https://rdf.wikipathways.org/about
https://github.com/wikipathways/wikipathways-iri-resolver
#LinkedData #FAIR #WikiPathways #RDF #Bioinformatics #SemanticWeb
Assuming that the conference "Perspectives on Scientific Error" 2026 (also known as PSE8)
https://perspectivesonscientificerror2026.wordpress.com/
has the #hashtag #PSE8, I am happy to report that it now also has a presence in the #nanopublications ecosystem at https://w3id.org/spaces/PSE8
In preperation for the nanopublications hackathon om 2026-02-13, we are going to use that space to experiment with the use of nanopublications for conference microblogging.
#openscience #FAIRdata #RDF #scientificerrors #reproducibility
Assuming that the conference "Perspectives on Scientific Error" 2026 (also known as PSE8)
https://perspectivesonscientificerror2026.wordpress.com/
has the #hashtag #PSE8, I am happy to report that it now also has a presence in the #nanopublications ecosystem at https://w3id.org/spaces/PSE8
In preperation for the nanopublications hackathon om 2026-02-13, we are going to use that space to experiment with the use of nanopublications for conference microblogging.
#openscience #FAIRdata #RDF #scientificerrors #reproducibility
RE: https://openbiblio.social/@awinkler/115982827467465444
from the linked GitHub issue: "Here is a demo of QLever handling one trillion triples on a single commodity PC: https://qlever.dev/one-trillion . That is more than fifty times larger than the current Wikidata" #sparql #rdf #opensource
Hi lazywell,
is there a standard CLI tool that can be used to extract all the descendants (rdf:subClass ? ) of a given term from a local OWL ontology file ?
I wrote a stupid java xml tool but I'd like a tool that understands the OWL spec (I don't)
#OpenScience and the #fediverse .. let's get that ball rolling 💪
@jfietkau @jonny and @bonfire opened a brainstorm and evaluation on how we can provide better support for the academic world and #science in general to the #ActivityPub-based fediverse.
Various different iniitiatives are underway, and there's great opportunity to bundle forces and align these efforts where possible. Set standards.
Interested? Join the discussion:
https://discuss.coding.social/t/my-current-goals-for-activitypub-and-academic-data/750
If you are at #39c3 and want to learn more about the current advances we made in the SDK of @nextgraph thanks to the contributions of @laurin ., he will be presenting his work on Tuesday the 30th at 10:30 in the CDC Triangle.
#localfirst #p2p #p4p #e2ee #crdts #decentralization #semanticweb #rdf #activitypub
If you are at #39c3 and want to learn more about the current advances we made in the SDK of @nextgraph thanks to the contributions of @laurin ., he will be presenting his work on Tuesday the 30th at 10:30 in the CDC Triangle.
#localfirst #p2p #p4p #e2ee #crdts #decentralization #semanticweb #rdf #activitypub
Yesterday I got some work done with Django AP Toolkit, finally solved one of the things that was bothering me in the mismatch between graph-oriented and object/relational-oriented programming: https://activitypub.mushroomlabs.com/topics/reference_context_architecture/#reference-based-relationships
And today I think I got closer to solve another part that was bugging me: most #ActivityPub sofrware does not deal with #RDF and instead relies on the JSON coming with a specific shape. THis means that even RDF-aware servers need to be able to select what data to put in a document. After iterating on some designs, I got something that seems acceptable by using "Projections": https://activitypub.mushroomlabs.com/topics/projections/
After a year since last time, I got back to playing with our digital-collections RDF exports and writing about it -- this time, aggregating some descriptions from id.loc and Wikidata. It was fun.
https://blogs.uoregon.edu/digitallibraryservices/2025/12/22/od2-rdf-02/
I believe we still have a fair bit of work and cleanup before we'd expose the data publicly. Maybe that's what I'll write about next year...
#rdf #sparql #python #lod
