Re: Turtle and JSON-LD Matter

Was there not a principle, stated or unstated, in RDF or linked data
specification, that there would be different representations of triples,
*and* that they would *be* equal?

seth

the #toothlessfoodie <https://plus.google.com/s/%23toothlessfoodie>
Facebook: facebook.com/russell.seth
Blog: fastblogit.com/seth/
Talking products: www.speaktomecatalog.com


On Wed, Jul 16, 2014 at 7:19 AM, 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.
>
> 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
>
>
>