- From: Dimitri van Hees <info@dimitrivanhees.com>
- Date: Thu, 31 Jul 2014 12:06:51 +0000
- To: "public-hydra@w3.org" <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.
Ok, would this response make sense then? http://pastebin.com/utYVDXt1
> Btw. HTML mails (in contrast to plain text mails) and top-posting are not very popular on mailing lists for various reasons :-P
I'm sorry. Is this better?
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>
Received on Thursday, 31 July 2014 12:07:19 UTC