W3C home > Mailing lists > Public > public-rww@w3.org > July 2014

Re: Turtle and JSON-LD Matter

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Wed, 16 Jul 2014 13:12:28 -0400
Message-ID: <53C6B27C.5090204@openlinksw.com>
To: "public-webid@w3.org" <public-webid@w3.org>
CC: "public-rww@w3.org" <public-rww@w3.org>
On 7/16/14 11:34 AM, Andrei Sambra wrote:
> Good point, Kingsley.
>
> I'm in favor of adding JSON-LD, but not as a MUST.

MUST is a problem vector. It creates a problematic misconception.

> The reason why we decided to only mandate Turtle was to reduce the 
> number of serialization formats people must support.

Yes, and how many WebID-TLS implementations has that generated, since 
the inception of this effort?

> No one stops you from offering several other formats, as long as you 
> at least support Turtle.

I know, that, I support every known RDF notation. I am not the audience 
here. I am more concerned about others that are inadvertently put-off by 
the TURTLE notation specificity of WebID-Profile and WebID-TLS.


>
> Anyway, I'm definitely in favor of adding at least some JSON-LD 
> examples, next to Turtle. :)

At least that's better than the current state of affairs  :-)

Kingsley

>
> -- Andrei
>
>
> On Wed, Jul 16, 2014 at 5:42 PM, Lee Curtis <lee.curtis@me.com 
> <mailto:lee.curtis@me.com>> wrote:
>
>     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 <mailto:melvincarvalho@gmail.com>> wrote:
>
>>
>>
>>
>>     On 16 July 2014 16:19, Kingsley Idehen <kidehen@openlinksw.com
>>     <mailto: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
>>         <http://www.openlinksw.com/>
>>         Personal Weblog 1: http://kidehen.blogspot.com
>>         <http://kidehen.blogspot.com/>
>>         Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen
>>         <http://www.openlinksw.com/blog/%7Ekidehen>
>>         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
>>
>>
>>
>
>


-- 
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


Received on Wednesday, 16 July 2014 17:12:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:10:47 UTC