W3C home > Mailing lists > Public > public-lod@w3.org > April 2011

Re: 15 Ways to Think About Data Quality (Just for a Start)

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Tue, 12 Apr 2011 17:55:48 -0400
Message-ID: <4DA4CA64.1000002@openlinksw.com>
To: glenn mcdonald <glenn@furia.com>
CC: "public-lod@w3.org" <public-lod@w3.org>
On 4/12/11 5:30 PM, glenn mcdonald wrote:
>>     http://linkeddata.uriburner.com/ode/?uri=http%3A%2F%2Fdbpedia.org%2Fresource%2FMichael_Jackson
>     The link above doesn't correspond to any link I've sent to you
>     owl:sameAs inference context. Basically, that's ODE one of many
>     browsers we offer. Its forte isn't showcasing owl:sameAs expansion.
>     Here are the links I sent earlier:
>     1.
>     http://lod.openlinksw.com/describe/?uri=http%3A%2F%2Fdbpedia.org%2Fresource%2FMichael_Jackson--
>     basic description of 'Micheal Jackson' from DBpedia
> As I said already, go to this link and then click "OpenLink Data 
> Explorer" at the bottom, hoping, as the message promises, to "Explore 
> alternative Linked Data Views & Meshups". Is there another link 
> somewhere to get to the SPARQL query behind the page? I don't see one.


-- URI Debugger output showing you what in <link/> and/or what you can 
extract via "Link:" response headers

As for the sole ODE option, that's kinda confusing as it isn't a 
coherent segue in the grand scheme of things for the human user per se. 
What I mean by that is this: we should also include the following links 
in the footer:

1. iSPARQL link that places you in the QBE or Advanced Mode tabs of our 
SPARQL Query Builder -- in this case you would see the DESCRIBE Query 
rather than having to processes the encoded URLs in <head/> <link/> or 
"Link:" response headers

2. PivotViewer links that places you either in the PivotViewer 
description page of the SPARQL query editor

3. Raw /sparql endpoint page that like #1 alleviates tedium of decoding 
the encoded SPARQL protocol URLs.

Then via 1-3 you end up with more human friendly routes to SPARQL behind 
the page.

>>     I wasn't even talking about Needle, but that day came long ago.
>>     All Needle nodes have IDs that resolve to representations via URLs.
>     Okay, what where you talking about? Specificity helps everyone,
>     this is a public forum etc..
> In Needle's Pazz & Jop music-poll dataset, the (relative) ID for 
> Michael Jackson is 76337.
> Here's a URI for the Michael Jackson node in Needle's Pazz & Jop dataset:
> https://pub.needlebase.com/actions/visualizer/V2Visualizer.do?domain=Pazz-Jop&thread=%4076337 
> <https://pub.needlebase.com/actions/visualizer/V2Visualizer.do?domain=Pazz-Jop&thread=%4076337>
> Here's a URL for seeing that node in Needle's UI:
> https://pub.needlebase.com/actions/visualizer/V2Visualizer.do?domain=Pazz-Jop&thread=%4076337&typeId=9149585060559937608&render=List 
> <https://pub.needlebase.com/actions/visualizer/V2Visualizer.do?domain=Pazz-Jop&thread=%4076337&typeId=9149585060559937608&render=List>
> Here's a URL for getting that data in JSON:
> https://pub.needlebase.com/actions/api/V2Visualizer.do?domain=Pazz-Jop&render=Jsv&thread=%4076337&typeId=9149585060559937608&render=List&showAllDetails=false&defaultCol=false&showRejectedGroups=false&selectedColumns=ColuwCRkEpwkbzaLG6%2CColaNkcDjUUlijFYSv%2CColZ2NJlXSlrQKvP7W%2CColQcBNiWkLbAqCXcY%2CColeZBKuJQ41hg96q0%2CColMqmX4mWy1jw4dkP%2CCol3kQ0iFiMTlmghrr%2CCol6UVm8wlhDfgfNlY&startPage=1&showCheckboxes=false&rerun=false 
> <https://pub.needlebase.com/actions/api/V2Visualizer.do?domain=Pazz-Jop&render=Jsv&thread=%4076337&typeId=9149585060559937608&render=List&showAllDetails=false&defaultCol=false&showRejectedGroups=false&selectedColumns=ColuwCRkEpwkbzaLG6%2CColaNkcDjUUlijFYSv%2CColZ2NJlXSlrQKvP7W%2CColQcBNiWkLbAqCXcY%2CColeZBKuJQ41hg96q0%2CColMqmX4mWy1jw4dkP%2CCol3kQ0iFiMTlmghrr%2CCol6UVm8wlhDfgfNlY&startPage=1&showCheckboxes=false&rerun=false>
> I make no claims about the prettiness of these.

Not worried about the prettiness etc..

Are 'Michael Jackson' Object ID and Object Representation Access Address 
distinct?   I already know that an HTTP GET against the Representation 
Address will return an EAV graph, once you loosen authentication 
requirements re. JSON representation :-)

BTW - can I assume this is the actual URL that you intended above re. 
access to JSON based graph representation: 



Kingsley Idehen	
President&  CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen
Received on Tuesday, 12 April 2011 21:56:14 UTC

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