Re: Example code

When developing a UI with a SQL database, if the developer is using an MVC pattern, they’re not sending SQL statements to the server and iterating over the result set. Instead, they’re making a request to the server such as “getPersonList” and the business logic on the server side is

Re: Splitting data into graphs vs datasets

Provenance. With named graphs, it's easier to track where data came from: who imported it, when etc. You can also have meta-graphs about other graphs. Also editing and updating data. You can load named graph contents (of smallish size) in an editor, make changes and then store a new version in

Splitting data into graphs vs datasets

Hi, I'm using Fuseki GSP, and so far have put all data into one default dataset and using graphs to split it. If I'm right there would be benefits using more than one dataset - better performance - each query is done inside a dataset so less data = faster query - protection of data - can't

Re: Example code

David, the actual UI rendering is done not by Java but by XSLT stylesheets that render RDF/XML: https://github.com/AtomGraph/Web-Client/blob/master/src/main/webapp/static/com/atomgraph/client/xsl/bootstrap/2.3.2/layout.xsl The stylesheet is invoked by the ModelXSLTWriter provider I mentioned

Re: Example code

On 19/3/18, 9:40 pm, "Martynas Jusevičius" wrote: David, >I gave you links but I take you haven't looked. The Web-Client project > specifically renders RDF as HTML. The crucial class is this: >

Re: Example code

On 19/3/18, 9:59 pm, "Laura Morales" wrote: >TBH I think you're writing to the wrong mailing list. You should write to the mailing list, and ask them to provide example code to use the UI with a Fuseki>backend instead of MySQL. The UI people would, quite