W3C home > Mailing lists > Public > public-linked-json@w3.org > November 2013

Map of identifiers of a type

From: Huynh T.D. <tdh@ecs.soton.ac.uk>
Date: Thu, 14 Nov 2013 10:26:51 +0000
To: "public-linked-json@w3.org" <public-linked-json@w3.org>
Message-ID: <480D40C41BB91343BC7581500181B0C91794CC9D@SRV00359.soton.ac.uk>
Hello,

I've just rediscovered JSON-LD yesterday (after about 2 years) and I've been very impressed with its progress.

Playing with my existing JSON, I found the following compact pattern that I have not been able to describe using the current specs.
{
  "Type1": {
    // A map of Type1 object IDs
    "id1": {
         // Properties of id1
         "name": "some value",
       },
       "id1": {
        // Properties of id2
       },
  },
  "Type2": {
    // another map of IDs here
  }
}

For example:
{
  "ConferencePaper": {
    "Huynh2013": {
         "title": "some value",
       },
    "Huynh2012": {
    },
  },
  "JournalPaper": {
  }
}
Essentially, there are two things that I want to describe using the pattern:

1.       "Huynh2013" and "Huynh2012" are identifiers of some objects, and

2.       they are of type ConferencePaper (i.e. rdf:type ConferencePaper).

Is it possible to describe the above pattern with the current spec?

I found the Data Indexing feature (http://json-ld.org/spec/latest/json-ld/#data-indexing) can help a bit with (1), but if I have to write "Huynh2013": { "@id": "Huynh2013", ... }, it is unnecessarily repetitive, I think.
I also found this email http://lists.w3.org/Archives/Public/public-linked-json/2013Nov/0003.html , which is related to (2), but the @reverse solution does not work in this case.

Many thanks,


Dong.
--
Dr T Dong Huynh
Research Fellow

Web and Internet Science Research Group         Tel: +44 (0) 23 8059 3270
School of Electronics and Computer Science      Fax: +44 (0) 23 8059 2783
University of Southampton                       Eml: tdh@ecs.soton.ac.uk<mailto:tdh@ecs.soton.ac.uk>
Southampton, SO17 1BJ, UK.
Received on Thursday, 14 November 2013 10:27:48 UTC

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