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

RE: Contd: Nice Data Cleansing Tool Demo

From: Georgi Kobilarov <georgi.kobilarov@gmx.de>
Date: Mon, 29 Mar 2010 21:13:27 +0200
To: "'Kingsley Idehen'" <kidehen@openlinksw.com>, <public-lod@w3.org>
Message-ID: <000101cacf73$f187fbd0$d497f370$@gmx.de>

> >>> So by the time you can
> >>> use Pivot on SW/linked data, you will already have solved all the
> >>> interesting and challenging problems.
> >>>
> >> This part is what I call an innovation slot since we have hooked it
> >> into
> >>
> > our
> >
> >> DBMS hosted faceted engine and successfully used it over very large
> >> sets.
> >
> > Kingsley, I'm wondering: How did you do that? I tried it myself, and
> > it doesn't work.
> Did I indicate that my demo instance was public? How did you come to
> overlook that?

I wasn't referring to a demo of yours, but to the general task of using
Pivot as a frontend to a faceted browsing backend engine. 

> > Pivot can't make use of server-side faceted browsing engines.
> >
> Why do you speculate? You are incorrect and Virtuoso *doing* what you
> claim is impossible will be emphatic proof, nice and simple.
> Pivot consumes data from HTTP accessible collections (which may be static
> dynamic [1]). A dynamic collection is comprised of CXML resources
> XML) .

I don't speculate. Which parts of my "does not work" and "can't use" did
sound like a speculation?  

> > You need to send *all* the data to the Pivot client, and it computes
> > the facets and performs any filtering operation client-side.
> You make a collection from a huge corpus of data (what I demonstrate) then
> you "Save As" (which I demonstrate as the generation point re. CXML
> resource) and then Pivot consumes. All the data is Virtuoso hosted.
> There are two things you are overlooking:
> 1. The dynamic collection is produced at the conclusion of Virtuoso based
> faceted navigation (the interactions basically describes the Facet
> membership to Virtuoso) 2. Pivot works with static and dynamic collections
> *I specifically state, this is about using both products together to solve
> major problem. #1 Faceted Browsing UX #2 Faceting over a huge data
> corpus.*
> Virtuoso is an HTTP server, it can serve a myriad of representations of
data to
> user agents (it has its own DBMS hosted XSLT Processor and XML Schema
> Validator with XQuery/XPath to boot, all very old stuff).

Yes, you make a collection and "save as" that to CXML, exactly! That is not
"using Pivot as a frontend to Virtuoso". Sure, you can construct a small
dataset from a huge dataset using SPARQL, or your Virtuoso facet engine or
whatever. And then export that resulting dataset to Pivot collection XML and
load that CXML into Pivot. But that is very different to using Pivot as a
frontend to a huge data set. 

> BTW -- how do you think Peter Haase got his variant working? I am sure he
> will shed identical light on the matter for you.

Yes, Peter, please do. From what I saw in the Fluidops demo, it works
exactly as I wrote above: A sparql-query constructs a small dataset from the
sparql endpoint, converts that via a proxy to CXML and loads it into Pivot. 

I don't say Pivot doesn't make a nice demo, or a useful tool to explore a
small dataset via faceted filtering. But it's not a frontend that can be put
on top of a faceted browsing engine like


Georgi Kobilarov
Uberblic Labs Berlin
Received on Monday, 29 March 2010 19:14:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:20:58 UTC