W3C home > Mailing lists > Public > public-digipub-ig@w3.org > December 2015

Re: "Scholarly HTML" and science.ai

From: Ivan Herman <ivan@w3.org>
Date: Mon, 14 Dec 2015 17:31:28 +0100
Cc: Charles LaPierre <charlesl@benetech.org>, W3C Digital Publishing IG <public-digipub-ig@w3.org>
Message-Id: <5429C908-54D3-4FFC-A4A2-A1D0DC41D27B@w3.org>
To: Dave Cramer <Dave.Cramer@hbgusa.com>

> On 14 Dec 2015, at 17:01, Cramer, Dave <Dave.Cramer@hbgusa.com> wrote:
> On Dec 14, 2015, at 10:50 AM, Ivan Herman <ivan@w3.org <mailto:ivan@w3.org>> wrote:
>>> On 14 Dec 2015, at 16:40, Charles LaPierre <charlesl@benetech.org <mailto:charlesl@benetech.org>> wrote:
>>> Has anyone read about this before?  Looks interesting just trying to see how this fits in with our PWP and archiving.
>>>> http://scholarly.vernacular.io <http://scholarly.vernacular.io/> and https://science.ai <https://science.ai/>
>> Robin Berjon (one of the co-authors of that paper) has started a W3C Community Group on scholarly HTML:
>> https://www.w3.org/community/scholarlyhtml/ <https://www.w3.org/community/scholarlyhtml/>
>> it is still in its early days, but it may be very interesting on long term.
>> Not sure yet how it will fit into PWP. In some sense, it may be orthogonal to PWP in the sense that what it tries to do is to define an HTML profile for scholarly publishing, to be used for particular use cases. These profiles, obviously, would fit PWP, too, but I do not believe it would create new requirements for it.
> I think of the idea of a "vernacular" itself [1] is quite applicable. Our mission is to use HTML for publications. In order to make such publications more readable, more accessible, and more meaningful, we are likely to use HTML in specific ways. A good example is requiring a nav file. This idea of a vernacular has certainly helped me clarify my thinking on EPUB Zero as defined in the Readme [2]

I must admit I did not know the vernacular itself, only the scholarly HTML stuff.

Whether vernacular is necessary for PWP as a whole: I am not sure, that is to be seen. I fully agree that for specific areas (like scholarly HTML) defining a vernacular is probably a good idea (that is where the CG is going). And there may be similar issues for defining, say, legal publications. But all those are, or I believe should be, independent from the general approach on PWP which should try to be as non-restrictive as possible…

But practice will tell. In any case, it *is* an interesting document, that is for sure!



> Dave
> [1] http://vernacular.io <http://vernacular.io/>
> [2] https://github.com/dauwhe/epub-zero/blob/gh-pages/readme.md <https://github.com/dauwhe/epub-zero/blob/gh-pages/readme.md>
> This may contain confidential material. If you are not an intended recipient, please notify the sender, delete immediately, and understand that no disclosure or reliance on the information herein is permitted. Hachette Book Group may monitor email to and from our network.

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 Monday, 14 December 2015 16:31:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:36:20 UTC