W3C home > Mailing lists > Public > public-linked-json@w3.org > September 2017

Re: Relative URI Handling in JSON-LD

From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Wed, 27 Sep 2017 13:47:34 -0700
Cc: "public-linked-json@w3.org" <public-linked-json@w3.org>, "public-lod@w3.org" <public-lod@w3.org>
Message-Id: <B0B8C947-33D6-4BD2-AC2E-38B247CF9B00@greggkellogg.net>
To: Kingsley Idehen <kidehen@openlinksw.com>
JSON-LD will require expanded IRIs to be absolute (as does an N-Triples transformation of Turtle). The “base”: “” overrides to document location, and inhibits the creation of absolute IRIs. While you should be able to do this, the result won’t be valid expanded JSON-LD or RDF.

Gregg

On Sep 27, 2017, at 1:20 PM, Kingsley Idehen <kidehen@openlinksw.com> wrote:
> 
> All,
> 
> Can anyone shed light on the ability to use relative HTTP URIs to
> identify relations (keys in json parlance) via JSON-LD [1] ?
> 
> I have an RDF-Turtle example that I am struggling to replicate in JSON-LD.
> 
> Links:
> 
> [1] https://twitter.com/kidehen/status/913134180317515777 -- depicts the
> dilemma I've encountered
> 
> [2]
> http://kingsley.idehen.net/DAV/home/kidehen/Public/Linked%20Data%20Documents/Nanotations/basic-test2.txt
> -- sample
> 
> -- 
> Regards,
> 
> Kingsley Idehen          
> Founder & CEO 
> OpenLink Software   (Home Page: http://www.openlinksw.com)
> 
> Weblogs (Blogs):
> Legacy Blog: http://www.openlinksw.com/blog/~kidehen/
> Blogspot Blog: http://kidehen.blogspot.com
> Medium Blog: https://medium.com/@kidehen
> 
> Profile Pages:
> Pinterest: https://www.pinterest.com/kidehen/
> Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen
> Twitter: https://twitter.com/kidehen
> Google+: https://plus.google.com/+KingsleyIdehen/about
> LinkedIn: http://www.linkedin.com/in/kidehen
> 
> Web Identities (WebID):
> Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i
>        : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this
> 
> 
Received on Wednesday, 27 September 2017 20:48:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:50 UTC