> On 2 Dec 2015, at 16:51, Robin Berjon <robin@berjon.com> wrote: > > Signed PGP part > On 02/12/2015 10:34 , Ivan Herman wrote: > > There may be a middle way for this specific aspect, though. Using > > RDFa is based on a specific RDF vocabulary (schema.org + some > > things). It is perfectly possible to embed RDF into the HTML using > > JSON-LD and the script tag. Ie, the author can choose to use that > > instead of RDFa, and the result is identical. Schema.org (afaik) > > understands both approaches and many RDFa processors (e.g., > > Python's RDFLib) has parsers both for RDFa and the embedded > > JSON-LD. > > Yes, we've considered that option and in fact we use for some things: > http://scholarly.vernacular.io/#data-rich. One interesting application > of that is as a manifest for a larger research bundle. > > The problems are: > > • For the specific issue of encoding authorship (or for that matter > citations) the JSON-LD is not necessarily that much clearer than the > RDFa :) Especially with roles. > :-( > • In general I think it is a good guiding principle that things that > should be shown to humans should actually be in the HTML. This rules > out JSON-LD islands for authors and citations (but completely keeps it > in for other things). > Yep. I agree but… unfortunately the sad fact is that, sometimes, mixing the html syntax with RDFa gets pretty convoluted. In those cases JSON-LD might come in as a rescue… Ivan > -- > • Robin Berjon - http://berjon.com/ - @robinberjon > • http://science.ai/ — intelligent science publishing > • > ---- Ivan Herman, W3C Digital Publishing Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704
Received on Wednesday, 2 December 2015 15:55:42 UTC