Hi Andy,

Thanks a lot, this are  exactly the pointers I had whished for! 

I will give this a try.

Thank you for your quick and helpful answer,
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

> -----Original Message-----
> From: Andy Seaborne [mailto:[email protected]]
> Sent: zaterdag 4 maart 2017 20:00
> To: [email protected]
> Subject: Re: Fuseki / ARQ DESCRIBE query to include ?s ?p <incoming resource>
> 
> Minor clarification:
> 
> Fuseki's default behaviour is the calculate the blank node closure based
> on the "subject (<incoming resource> ?p ?o)".
> 
> 
> There's a registry DescribeHandlerRegistry and a context key for setting
> it (ARQConstants.registryDescribeHandlers).
> 
> The registry keeps a list of DescribeHandlerFactory and calls each one
> on the list.
> 
> Adding to that list or setting per query is doable but it's Java - in
> Fuseki from just configuring, it's not doable.
> 
> Adding a context setting to set the DescribeHandle policy by name would
> achieve that.
> 
>       Andy
> 
> e.g.
> https://gist.github.com/shellac/1313924
> 
> On 03/03/17 10:13, Beetz, J. 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+%3
> Fo&page=2#query:describe%20query%20%3Fs%20%3Fp%20%3Fo+page:2+mid:5thzze4xhqhak3
> 4g+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
> >

Reply via email to