No, Pubby [1] is designed to present a simple "Linked Data" representation of resources the data for which are recorded in some SPARQL-equipped service (e.g. Fuseki).
You set up Pubby aimed at your SPARQL endpoint, and then when people make requests for a particular resource from Pubby, it gives them the results of a DESCRIBE query on that resource. --- A. Soroka The University of Virginia Library [1] > On Mar 3, 2017, at 9:37 AM, Martynas Jusevičius <[email protected]> wrote: > > Isn't Fuseki already doing the same as Pubby? > > On Fri, Mar 3, 2017 at 11:13 AM, Beetz, J. <[email protected]> wrote: >> Dear community, >> >> I have set up a Pubby http://wifo5-03.informatik.uni-mannheim.de/pubby/ >> frontend to allow dereferencing/content-negotiation/browser-navigation of a >> vocabulary served by Fuseki 2.4.1 . >> As per the SPARQL standard, the default behavior of DESCRIBE queries that >> are sent by the frontend to Fuseki is left to the implementation. Fusekis >> default behavior is to send back the graph containing all triples where >> <incoming resource> is the subject (<incoming resource> ?p ?o). I would also >> like to include (?s ?p <incoming resource> and probably (?s <incoming >> resource> ?o). >> >> From the list archive I have seen that I can probably implement my own >> execDescribe() similar to this thread from some time ago: >> http://jena.markmail.org/message/5thzze4xhqhak34g?q=describe+query+%3Fs+%3Fp+%3Fo&page=2#query:describe%20query%20%3Fs%20%3Fp%20%3Fo+page:2+mid:5thzze4xhqhak34g+state:results >> >> I wonder whether there is another (easier) way through a configuration >> setting or similar which allows me to achieve this. >> >> Thank you very much in advance for your help >> >> Jakob >> >> _______________________________________________________________ >> Dr. Jakob Beetz - Assistant Professor >> Information Systems in the Built Environment (ISBE) Group >> Department of the Built Environment | Bouwkunde >> Eindhoven University of Technology, The Netherlands >> phone: +31 (0)40 247 2288 on-campus location: VRT 9.J06 >>
