I never had the chance to actually use JSON-LD in a project, so I will have to 
toy around with it first, but considering that lots of people are familiar to 
the JSON syntax I think that definitely makes sense!
Added to the list of output formats to support in the Jenkins plug-in.

Thanks Andy! 
Bruno


      From: Andy Seaborne <[email protected]>
 To: [email protected] 
 Sent: Monday, April 27, 2015 1:55 AM
 Subject: Re: Implementing CSV on the Web | Gregg Kellogg
   
Bruno,

Maybe JSON-LD would be a good choice for output - can be handled as JSON 
syntax or used as RDF.

    Andy



On 22/04/15 23:48, Bruno P. Kinoshita wrote:
> Thanks for sharing Andy!
> I'm collecting posts like this to work on enhancing the existing Metadata 
> plugin for Jenkins [1].
> My goal is to use Jena within Jenkins, to store metadata and transform 
> Jenkins into a SPARQL Endpoint. Also letting users retrieve metadata from 
> Jenkins builds using format as RDF, JSON, XML, etc. I hadn't thought about 
> CSV to RDF yet.
> Bruno
>
> [1] https://wiki.jenkins-ci.org/display/JENKINS/Metadata+plugin
>
>        From: Andy Seaborne <[email protected]>
>  To: [email protected]
>  Sent: Thursday, April 23, 2015 5:05 AM
>  Subject: Implementing CSV on the Web | Gregg Kellogg
>
> FYI
>
> Gregg Kellogg has written up his experience in implementing the W3C "CSV
> on the web" (inc conversion to RDF) working group design.  His
> implementation is in Ruby but the experience is valid for any language.
>
> http://greggkellogg.net/2015/04/implementing-csv-on-the-web/
>
>      Andy
>
>
>
>



   

Reply via email to