rdfreader

Paste any IRI. We dereference it the way a linked data client should, parse whatever comes back, and render it as a page a person can actually read.

Prefilled with Drexel University, so Read works before you have typed anything. No account, nothing stored. Each request fetches and parses live at the edge.

Try these

• Archdiocese of Los Angelesturtle Textbook content negotiation: a 303 redirect for browsers, Turtle and JSON-LD for clients.
• All of schema.orgturtle 1,010 classes as a subsumption tree, six levels deep. The view an ontology editor opens with, on a URL.
• The GeoNames ontologyrdf/xml 6,847 triples. A whole gazetteer vocabulary, read as a class and property listing.
• GoodRelationsrdf/xml The e-commerce vocabulary that shaped how schema.org models products and offers.
• schema.org: Recipejson-ld Deeply inherited properties, flattened and labeled so the page reads top to bottom.
• The SIOC Core ontologyrdf/xml 669 triples in the classic serialization, the one most vocabularies were published in before Turtle.
• Victor Hugo, at the BnFjson-ld An ARK identifier from the Bibliotheque nationale de France, resolved to a person.
• The FOAF vocabularyjson-ld A classic ontology. Renders as a class and property listing rather than a resource page.
• schema.org: Personjson-ld The vocabulary behind most structured data on the open web, served as JSON-LD.
• Vatican Cityturtle 18,410 statements about one place. Labels get resolved so it reads as prose, not identifiers.
• GeoNames: Los Angelesrdf/xml Gazetteer data with neighboring features, the kind of graph the visualization was built for.
• Wikidata: Q42turtle Opaque identifiers, deep redirect chain. The chain is shown rather than hidden.
• Dublin Core termsturtle The oldest metadata vocabulary still in daily use, and a purl.org redirect on the way in.
• An ORCID recordturtle A person as a first-class identifier, the way scholarly infrastructure models one.