Re: json-ld.org playground updated

Sorry, not fully engaged here, and my mind is definitely mid-pacific. If {"@literal": "foo"} is banned, then how does one express a plain literal when the context has a default @language? Is it not possible to express a plain literal when the context has @language? I always presumed that this is how it would be done.

Gregg

On Jan 19, 2012, at 5:16 AM, Manu Sporny wrote:

> On 01/18/12 15:05, Manu Sporny wrote:
>> On 01/18/12 12:10, Alexandre Passant wrote:
>>> It seems that @value is not rendered properly, e.g.
>> 
>> Fixed:
>> 
>> https://github.com/json-ld/json-ld.org/commit/8b930458dac3e69ddef5bba6b716a6cd76dcaa9e
> 
> After some discussion with Dave Longley, both of us feel that we should
> kill this feature. It overly complicates the number of ways that you can
> express a plain literal.
> 
> There is an argument that this should be valid: { "@value": "foo" }
> 
> However, it does two things:
> 
> 1. It complicates what developers have to deal with, now you can't just
> check to see if the value is a string for a plain literal... you have to
> check if it is a string, and if it isn't, you have to check to see if it
> is an object containing an "@value" key and only that key.
> 
> 2. It complicates the expansion algorithm, instead of { "name": "foo" },
> expanded form ends up being {"name": { "@value": "foo"}}
> 
> 3. The two items above thus complicate implementations.
> 
> While it's perfectly logical to interpret { "@value": "foo" } as a plain
> literal, I don't think we should because it doesn't buy us anything
> other than more complexity. We should keep it simple... plain literals
> are expressed as strings in JSON-LD - always.
> 
> -- manu
> 
> -- 
> Manu Sporny (skype: msporny, twitter: manusporny)
> President/CEO - Digital Bazaar, Inc.
> blog: Web Payments - PaySwarm vs. OpenTransact Shootout
> http://manu.sporny.org/2011/web-payments-comparison/
>

Received on Friday, 20 January 2012 11:35:20 UTC