Heh, our mails crossed! Except that you do not have to use JSON-LD 1.1 for that,
https://www.w3.org/TR/2014/REC-json-ld-20140116/#default-vocabulary <https://www.w3.org/TR/2014/REC-json-ld-20140116/#default-vocabulary>
has the same example!
Ivan
> On 4 Jun 2018, at 17:02, Laurent Le Meur <laurent.lemeur@edrlab.org <mailto:laurent.lemeur@edrlab.org>> wrote:
>
> 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/ <http://schema.org/>",
> "databaseId": null
> },
> "@id": "http://example.org/places#BrewEats <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 <mailto: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.
>>
>
----
Ivan Herman, W3C
Publishing@W3C Technical Lead
Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
mobile: +31-641044153
ORCID ID: https://orcid.org/0000-0003-0782-2704 <https://orcid.org/0000-0003-0782-2704>