Allow to specify field of language code and string

[nichtich]

It looks like the following JSON format cannot be mapped to RDF with JSON-LD:

{
  "id": "http://example.org/istanbul"
  "names": [
    { "string": "İstanbul", "lang": "tr" },
    { "string": "Istanbul", "lang": "en" }
  ]
}

JSON-LD should be expanded to allow context like this

{
  "id": "@id",
  "names": { 
    "@id": "http://purl.org/dc/terms/title",
    "string": "@literal",
    "lang": "@language"
  }
}

to transform the example above to

<http://example.org/istanbul> <http://purl.org/dc/terms/title> "İstanbul"@tr .
<http://example.org/istanbul> <http://purl.org/dc/terms/title> "Istanbul"@en .

[dlongley]

A solution here (that works today):

{
  "@context": {
    "id": "@id",
    "names": {
      "@id": "http://purl.org/dc/terms/title",
      "@context": {
        "string": "@value",
        "lang": "@language"
      }
    }    
  },
  "id": "http://example.org/istanbul",
  "names": [
    { "string": "İstanbul", "lang": "tr" },
    { "string": "Istanbul", "lang": "en" }
  ]
}

<http://example.org/istanbul> <http://purl.org/dc/terms/title> "Istanbul"@en .
<http://example.org/istanbul> <http://purl.org/dc/terms/title> "İstanbul"@tr .

See: https://tinyurl.com/98rmjfvu

[nichtich]

Thanks a lot!

[TallTed]

It would be good to fix typo in title, from specifcy to specify.