Hi, I have exactly the same idea, and the same problem... I have rdf stored in Sesame and I would like to use Exhibit to display this knowledge base in a user-friendly way.
I think the performance problem would be solved using SPARQL and converting dynamically the results to a json file, but I don't find any tool that does it at runtime. Do you know about such a tool? I see that Ivan Hermann (http://www.ivan-herman.net/Misc/PythonStuff/SPARQL/ Doc-SPARQL/SPARQL-module.html) had a similar approach using Python, but we are using Java. Any ideas? Cheers Tomás On Mar 29, 9:52 am, harshal <[email protected]> wrote: > Hi, > > Is it a good idea to consider Google Gears or similar for locally > storing the items ? > I think some scalability can be achieved with this approach. > > I would appreciate any comments on this. > > Thanks for your time. > > Regards > > ./harshal > > On Mar 29, 5:55 am, David Huynh <[email protected]> wrote: > > > Batla, > > > Yes, Exhibit isn't meant to scale that much... A few thousand items > > (records) are pushing it. I started a hybrid client/server version of > > Exhibit called Backstage, but haven't had much time to follow through. > > > David > > > Batla wrote: > > > HI David, > > > > Thanks for your response. > > > > I guess I'm thinking that I'm looking for something Exhibit may not > > > be...at least "out of the box". I ran into a problem with a large > > > volume of data with an exhibit I built (about 500k triples). I was > > > hoping that perhaps I could query something like a sesame server and > > > try to keep the json objects in manageable chunks. Pagination I'm > > > thinking. > > > > I may be making some pretty big assumptions here. I'm sure someone on > > > this list has already done something like this w/o any need for a > > > physical triple store - I'll check the historical posts again. But in > > > the meanwhile, if you can shed any light on this or point me to a > > > relevant thread, I would appreciate it. > > > > Thanks, > > > Batla > > > > On Mar 21, 9:35 pm, David Huynh <[email protected]> wrote: > > > >> Batla wrote: > > > >>> Hi all, > > > >>> Please forgive me if this post is a little naive. I am fairly > > >>> confident in my knowledge of RDF, but I am new to Exhibit and Sesame. > > >>> Up to now I have built a very simple exhibit and a very simple > > >>> implementation of MemoryStore in Sesame. > > > >>> Here's my question. Is there a "converter" than someone has written > > >>> that I could use to convert Statements from Sesame to Exhibit JSON? > > >>> Here's what I'm thinking. I like the sesame API's to the RDF Store - > > >>> querying, inserting, etc. and I love the faceted browse in Exhibit. I > > >>> would like to leverage both. Does that even make sense? > > > >>> Any pointers for this newbie would be helpful and appreciated. > > > >>> Thanks in advance! > > > >> Batla, > > > >> Babel > > >> http://service.simile-widgets.org/babel/ > > >> can convert from RDF/XML to Exhibit/JSON. It only processes resources > > >> that have rdf:type's. > > > >> You can even feed Exhibit an RDF/XML URL directly, and Exhibit will > > >> route it through Babel, e.g., > > >> > > >> http://people.csail.mit.edu/dfhuynh/projects/data-theft/data-theft.html > > > >> David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/simile-widgets?hl=en -~----------~----~----~----~------~----~------~--~---
