W3C home > Mailing lists > Public > public-schemaorg@w3.org > June 2015

Re: JSON-LD and multiple values

From: Dan Brickley <danbri@google.com>
Date: Tue, 9 Jun 2015 15:06:12 +0100
Message-ID: <CAK-qy=6ua=84BS3ZE9_PqGguCTbhYaxsftx+U2_eGMZW+t0zJw@mail.gmail.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Cc: John Walker <john.walker@semaku.com>, "mfhepp@gmail.com" <mfhepp@gmail.com>, Gregg Kellogg <gregg@greggkellogg.net>, Manu Sporny <msporny@digitalbazaar.com>, "schema.org Mailing List" <public-schemaorg@w3.org>
On 9 June 2015 at 14:36, Melvin Carvalho <melvincarvalho@gmail.com> wrote:
>
>
> On 9 June 2015 at 15:33, Dan Brickley <danbri@google.com> wrote:
>>
>> On 9 June 2015 at 14:20, Melvin Carvalho <melvincarvalho@gmail.com> wrote:
>> >
>> >
>> > On 9 June 2015 at 14:52, John Walker <john.walker@semaku.com> wrote:
>> >>
>> >> For the record I-JSON forbids duplicate names in an object:
>> >> https://tools.ietf.org/html/rfc7493#section-2.3
>> >
>> > So how do you do unordered lists.  Say a user has two nicknames or
>> > telephone
>> > numbers (strings).  This is a fundamental part of linked data, if it
>> > cant
>> > easily be done it's a *massive* interoperability issue.
>>
>> It's an array viewed from JSON, but a repeated property viewed from RDF.
>
>
> Got it, so you'd use @list in JSON LD for an ordered list, and a standard
> array for unordered.
>
> But is can I-JSON do the same thing?

Yup, https://www.tbray.org/ongoing/When/201x/2015/03/23/i-json
"I-JSON is just a note say­ing that if you con­struct a chunk of JSON
and avoid the in­terop fail­ures de­scribed in RFC 7159, you can call
it an “I-JSON Message”."

Dan
Received on Tuesday, 9 June 2015 14:06:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 9 June 2015 14:06:46 UTC