Re: Turtle and JSON-LD Matter

Shouldn’t we all strive to support at least TTL, JSON-LD and RDF/XML?

TTL because we have to read/write RDF every day.

JSON-LD because we need (more) killer apps

RDF/XML because it’s too ugly to die

-lee-


On 17 Jul 2014, at 12:34 am, Melvin Carvalho <melvincarvalho@gmail.com> wrote:

> 
> 
> 
> On 16 July 2014 16:19, Kingsley Idehen <kidehen@openlinksw.com> wrote:
> All,
> 
> Is there any reason why Turtle and JSON-LD cannot be on equal footing in regards to the WebID spec?
> 
> There's no reason why WebID-Profile documents MUST be comprised of RDF content in Turtle Notation.
> 
> Its crystal clear that we have two critical developer communities that coalesce around Turtle and JSON-LD  i.e., Semantic Web and Web Developers, respectively. Thus, its in the best interest of adoption for the WebID spec to treat Turtle and JSON-LD as different RDF notations for creating RDF document content e.g., WebID-Profile documents.
> 
> Not an issue for me to add JSON LD to my WebID, if needed.  It only took me 30 minutes to add turtle support :)
> 
> Would be interesting to see what others think.
>  
> 
> WebID-TLS implementers should be encouraged to support WebID-Profile documents comprised of Turtle or JSON-LD content. This is really important, at this point in time.
> 
> -- 
> Regards,
> 
> Kingsley Idehen 
> Founder & CEO
> OpenLink Software
> Company Web: http://www.openlinksw.com
> Personal Weblog 1: http://kidehen.blogspot.com
> Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen
> Twitter Profile: https://twitter.com/kidehen
> Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
> LinkedIn Profile: http://www.linkedin.com/in/kidehen
> Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this
> 
> 
>