- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Mon, 28 Jul 2014 03:05:11 -0400
- To: <public-hydra@w3.org>
On Monday, July 28, 2014 2:11 AM, Dimitri van Hees wrote:
> I mean that with the context file I am able to convert homeLocation
> to http://schema.org/homeLocation, but "Tilburg" remains a literal instead
> of a http://schema.org/City. I am able to do that when adding @type to the
> response but not with the context file, right?
Yep, that's correct. Without introducing yet another keyword, a JSON-LD processor wouldn't know whether you meant it to be
{ "@value": "Tilburg", "@type": "schema:City" }
or
{ "@id": "Tilburg", "@type": "schema:City" }
In most cases, if you use a URL instead of a literal, you want to add more properties than just a type anyway.
Btw. HTML mails (in contrast to plain text mails) and top-posting are not very popular on mailing lists for various reasons :-P
--
Markus Lanthaler
@markuslanthaler
Received on Monday, 28 July 2014 07:05:43 UTC