WikiPathways RDF IRIs are now dereferenceable #222
marvinm2
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
WikiPathways RDF IRIs are now dereferenceable
The WikiPathways RDF IRI resolver is live at rdf.wikipathways.org/about. Every
http://rdf.wikipathways.org/IRI — pathways, interactions, complexes — now resolves via standard HTTP with content negotiation.What does this mean?
Until now, WikiPathways RDF IRIs (like
http://rdf.wikipathways.org/Pathway/WP4846_r140186) existed in the triplestore but returned nothing when you tried to dereference them in a browser or withcurl. That breaks a core Linked Data principle: IRIs should be dereferenceable.The resolver fixes this by acting as a transparent SPARQL proxy. When you request an IRI, it issues a
DESCRIBE <IRI>query against the WikiPathways Virtuoso endpoint and returns the result in whatever format you ask for.How to use it
In a browser
Just visit any WikiPathways RDF IRI and you'll get a syntax-highlighted HTML view with clickable links:
From the command line
Via Accept header:
Via file extension (overrides Accept header):
Supported formats
text/htmltext/turtle.ttlapplication/ld+json.jsonldapplication/rdf+xml.rdfapplication/n-triples.ntBrowsers and clients sending
*/*get HTML by default.Operational details
The service caches responses in memory (5 min TTL) and supports HTTP caching via
ETag,If-None-Match(304), andCache-Controlheaders. CORS is open (Access-Control-Allow-Origin: *). Prometheus metrics are at/metrics, health check at/_health. Rate limit is 60 requests/minute per IP, configurable.Links
The resolver is a single-file Flask app deployed with Gunicorn in Docker. MIT licensed. If you hit a bug or have questions, open an issue in the GitHub repo!
Beta Was this translation helpful? Give feedback.
All reactions