Re: Newsletter & Call for Papers WebSci'18

Dear Peter,

Note that all of your items can be achieved with the current Web technology stack:

> - self-contained documents

You can embed all resources in an HTML document,
by inlining styles and scripts, and using data: URIs.

> - a document as a sequence of pages with non-varying line width and page height

You can obtain that with CSS.
Set a consistent line-height in points,
and specify the page dimensions.

> - non-varying fonts and glyphs, renderable at different resolutions

This is possible with system fonts and WOFF fonts.

> - non-varying embedded graphics, renderable at different resolutions

This is possible with SVG.

> - multiple popular ways to produce conformant documents

There exist many editors for HTML, CSS, SVG.

> - multiple popular ways to render at low cost

There exist many free browsers.

> (Yes, some of these are not true of PDF itself, but instead are true of the
> standard uses of PDF in scholarly publishing.)

Likewise, some of the things mentioned above are not universal HTML practices
(in particular the embedding of all resources), but are technologically possible.

>From the above, I conclude that the technological advantages alone should not be a burden.
Please let me know what other burdens you see.



Received on Sunday, 25 February 2018 20:23:52 UTC