W3C home > Mailing lists > Public > public-lod@w3.org > March 2010

Figuring out what's behind a SPARQL endpoint

From: Hondros, Constantine <Constantine.Hondros@wolterskluwer.com>
Date: Tue, 23 Mar 2010 08:59:02 +0100
To: "public-lod@w3.org" <public-lod@w3.org>
Message-ID: <6C01B6D23EB50A4487054D57249A0B01097203D41A@EUSRVWK01005.eu.wkeurope.com>
What's the best way to get a grip on what's actually behind an endpoint?

I've been mulling over a proof-of-concept project to enrich published legal content - already highly annotated with RDF metadata - with RDF content from open government sources. But I'm kind of baffled by how best to assess the richness of an endpoint other than by running my own SPARQLs - eg. listing DISTINCT predicates, or CONSTRUCTing some of the typed resources.

These queries give me some indication of what's there ... but  what would be handy is some sort of visualisation or analysis tool that gives me statistics like the number of resources contained in the endpoint, the type and predicate vocabularies used, and the density of linking between resources.

Anything like this exist?

This email and any attachments may contain confidential or privileged information
and is intended for the addressee only. If you are not the intended recipient, please
immediately notify us by email or telephone and delete the original email and attachments
without using, disseminating or reproducing its contents to anyone other than the intended
recipient. Wolters Kluwer shall not be liable for the incorrect or incomplete transmission of
of this email or any attachments, nor for unauthorized use by its employees.

Wolters Kluwer nv has its registered address in Alphen aan den Rijn, The Netherlands, and is registered
with the Trade Registry of the Dutch Chamber of Commerce under number 33202517.
Received on Tuesday, 23 March 2010 07:59:38 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:16:03 UTC