W3C home > Mailing lists > Public > public-publ-wg@w3.org > June 2018

Re: Minimal WPUB for a scholarly paper (of sort)

From: Laurent Le Meur <laurent.lemeur@edrlab.org>
Date: Mon, 4 Jun 2018 16:38:56 +0200
Message-Id: <E8851C97-88B8-4DA5-9FDC-E72271811548@edrlab.org>
Cc: Ivan Herman <ivan@w3.org>, Hadrien Gardeur <hadrien.gardeur@feedbooks.com>, W3C Publishing Working Group <public-publ-wg@w3.org>
To: Benjamin Young <byoung@bigbluehat.com>
I just wonder why we wouldn't create our context and include the schema.org <http://schema.org/> vocab inside.  Isn't it the way JSON-LD is scalable ?

Cordialement, 

Laurent Le Meur
EDRLab


> Le 4 juin 2018 à 16:24, Benjamin Young <byoung@bigbluehat.com> a écrit :
> 
> Laurent is correct. Because Schema.org <http://schema.org/>'s context file [1] defines `"@vocab": "http://schema.org <http://schema.org/>/"` anything not currently defined within the context fill will still be mapped to that URL space.
> 
> Here's a JSON-LD playground example of the current wiki:
> https://tinyurl.com/y7fgat9t <https://tinyurl.com/y7fgat9t>
> 
> The quick and dirty solution is to use the same "greediness" of the `@vocab` to prevent that behavior until either we or Schema.org <http://schema.org/> define it.
> 
> To do that in JSON-LD, we'd change the example documents `@context` line to read:
> ```
>   "@context": ["https://schema.org <https://schema.org/>", {"@vocab": null}],
> ```
> 
> That will make any JSON-LD processor ignore anything it doesn't find in the schema.org <http://schema.org/> context file.
> 
> Hope that helps!
> Benjamin
> 
> [1] https://schema.org/docs/jsonldcontext.json <https://schema.org/docs/jsonldcontext.json>
> 
> --
> http://bigbluehat.com/ <http://bigbluehat.com/>
> http://linkedin.com/in/benjaminyoung <http://linkedin.com/in/benjaminyoung>
Received on Monday, 4 June 2018 14:39:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:52:27 UTC