Well, a report developer wants to give users reports that mean something, and sometimes having an analytical view like Exhibit is great. The faceted view is newer, but along the lines of Pivot Tables in Excel, or Crystal Analysis, or Essbase or other OLAP tools, and yes, I would expect users to understand, at least vaguely, that that data has to be staged most often from a "raw" view. That's the report developer's job, to make sense of the raw data, and then to stage that for users.
I dunno about some of this, getting a little thick into what exactly your community is comprised of. I think that RDF in general can provide tools for end users (A sparql XML result with a stylesheet applied, a basic static report), as well as whatever else. Personally I wish I had more tools available for very large dataset visualization, heh... It all depends on what you have going on. > when you sort by some category, maybe you would have interesting results that > arent in > the local cache but are on the remote store - at this point, you > might as well throw away > exhibit's database class completely, and replace it with something that is > designed from > conception to work with multiple endpoints/providers SPARQL does that... it can handle multiple FROMs which could be SPARQL endpoints, or flat RDF data available via HTTP.... I don't think exhibits focus is merging multiple datasets from multiple repositories, but you can certainly do that probably digging into the code, but I've always thought that SPARQL, or even your RDF database itself, should be able to do that. Thomas On 3/17/07, carmen <[EMAIL PROTECTED]> wrote: > On Sat Mar 17, 2007 at 03:47:12PM -0500, Thomas Winningham wrote: > > Keith, > > > > I've often thought that an Exhibit of an ad-hoc query or a specific RDF > > context is an insanely powerful and under used idea. > > the main problem is the dichotomy of 2 layers of querying. the initial > SPARQL/Versa/graph-pattern layer in the store. then the secondary layer in > the clientside/view-coupled store. > > when you sort by some category, maybe you would have interesting results that > arent in the local cache but are on the remote store - at this point, you > might as well throw away exhibit's database class completely, and replace it > with something that is designed from conception to work with multiple > endpoints/providers > > > Its amazing to think of a query as setting the stage for further ad-hoc > > faceted analysis. This is almost the 2-part SPARQL query techniques to get > > to any view you want of RDF data as described by Danny Ayers in some of his > > blog posts. > > whats this? do you really think users want to think about their queries as > needing 2 parts? > _______________________________________________ > General mailing list > [email protected] > http://simile.mit.edu/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
