W3C home > Mailing lists > Public > public-linked-json@w3.org > August 2014

Re: Migrating to @id and @type for legacy JSON specifications

From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
Date: Tue, 5 Aug 2014 14:46:43 +0100
Message-ID: <CAPRnXtnY4wBihs6EhzHxPje0nRu-WihJ7DbJCkTwCeYxJdv1Uw@mail.gmail.com>
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Cc: Linked JSON <public-linked-json@w3.org>
In deed, that does works now (but not last time I tried), as long as
you are OK to use the same alias within the whole resulting JSON.

e.g.:

{
  "@context": {
    "dc": "http://purl.org/dc/elements/1.1/",
    "ex": "http://example.org/vocab#",
    "xxx": "@id",
    "yyy": "@type"
  },
  "@type": "ex:Library",
  "ex:contains": {
    "@type": "ex:Book",
    "@context": {
      "id3": "@id"
    },
    "ex:contains": {
      "@type": "ex:Chapter"
    }
  }
}

In the JSON-LD playground Library Framing example, gives:

  "@graph": [
    {
      "xxx": "http://example.org/library",
      "yyy": "ex:Library",
      "ex:contains": {
        "xxx": "http://example.org/library/the-republic",
        "yyy": "ex:Book",



On 23 July 2014 08:16, Markus Lanthaler <markus.lanthaler@gmx.net> wrote:
> On 22 Jul 2014 at 03:05, Stian Soiland-Reyes wrote:
>> One problem I found is that, if data is coming from RDF and going out
>> as JSON-LD, it is hard to generate aliased terms for '@id' and '@type'
>> with JSON-LD Framing - but perhaps someone know a nice trick with one
>> of the libraries? (Search/replace does not count :) )
>
> What makes it difficult? Doesn't defining an alias in the frame's context do the job?
>
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>
>
>



-- 
Stian Soiland-Reyes, myGrid team
School of Computer Science
The University of Manchester
http://soiland-reyes.com/stian/work/ http://orcid.org/0000-0001-9842-9718
Received on Tuesday, 5 August 2014 13:47:33 UTC

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