I also found in https://json-ld.org/spec/latest/json-ld/#advanced-concepts <https://json-ld.org/spec/latest/json-ld/#advanced-concepts> another potential solution:
{
"@context": {
"@vocab": "http://schema.org/",
"databaseId": null
},
"@id": "http://example.org/places#BrewEats",
"@type": "Restaurant",
"name": "Brew Eats",
"databaseId": "23987520"
}
in
Cordialement,
Laurent Le Meur
EDRLab
> Le 4 juin 2018 à 16:44, Laurent Le Meur <laurent.lemeur@edrlab.org> a écrit :
>
> Is Google so weak? Can't believe it...
>
> L
>
>
>> Le 4 juin 2018 à 16:42, Hadrien Gardeur <hadrien.gardeur@feedbooks.com <mailto:hadrien.gardeur@feedbooks.com>> a écrit :
>>
>> This was an option that I pointed out as well during the meeting. Given the fact that we'll need terms from bib.schema.org <http://bib.schema.org/> as well (and probably other vocabularies as well), this feels like a good approach.
>>
>> The main issue with rolling our own context seems to be that Google wouldn't be able to properly parse and index these metadata.
>