The lib I mentionned  probably can run server-side. In that case, you also need 
a JsonT stylesheet to "tree-ize" the js object graph and serve it as a Json 
structure.
Node.js can do these kind of tricks. Patching Fuseki with some Rhino code 
sounds possible too.


Le 19 juil. 2013 à 19:44, Neubert Joachim <[email protected]> a écrit :

> Hi Oliver,
> 
> Thank you for your offer. This could indeed be helpful on the frontend side. 
> It however does not solve my problem as a provider of Fuseki-based web 
> services (http://zbw.eu/beta/econ-ws), where I try to make it as easy as 
> possible for the unknown web programmer on the other side of the API.
> 
> Cheers, Joachim
> 
> -----Ursprüngliche Nachricht-----
> Von: Olivier Rossel [mailto:[email protected]] 
> Gesendet: Freitag, 19. Juli 2013 17:56
> An: [email protected]
> Betreff: Re: JSON-LD as a Fuseki output format
> 
> I developed a js library so a web client can parse a (n3) CONSTRUCT result, 
> and create the corresponding javascript graph of resources.
> Not a big deal. But the base for nice client-side tricks :) Interested in the 
> code?
> 
> 
> On Fri, Jul 19, 2013 at 1:51 PM, Neubert Joachim <[email protected]> wrote:
> 
>> For some use cases, the tabular SPARQL select query output formats are 
>> not optimal. That's true when the results are in fact tree-shaped, 
>> such as multiple skos concepts with their relations and their respective 
>> labels.
>> Therefore, it would be highly useful if I could offer the output of a 
>> SPARQL construct query in a format which a web developer without any 
>> knowledge of RDF can immediately cope with.
>> 
>> From Andy's mail on this list (
>> http://mail-archives.apache.org/mod_mbox/jena-users/201306.mbox/%3C51C
>> [email protected]%3E) I understand that there are issues re. 
>> the scalability of json-ld and its suitability for updates. However, I 
>> imagine that for a large number of use cases these issues would not 
>> matter, and an integration of jena-jsonld into Fuseki (perhaps with a 
>> warning hint in the documentation) could be tremendously helpful for 
>> people using Fuseki just out of the box.
>> 
>> What do you think?
>> 
>> Cheers, Joachim
>> 
>> 

Reply via email to