W3C home > Mailing lists > Public > public-publ-wg@w3.org > August 2017

Re: On Spreadsheets, Birthday Cards, and the Nature of Publications

From: Leonard Rosenthol <lrosenth@adobe.com>
Date: Mon, 14 Aug 2017 13:59:42 +0000
To: Dave Cramer <dauwhe@gmail.com>, W3C Publishing Working Group <public-publ-wg@w3.org>
Message-ID: <2AB97533-F2D1-4F9E-9836-54E7E1FFEA5F@adobe.com>
Great questions, Dave!

And I would tend to agree with you that the primary benefit for many of these ad-hoc publications is the ability to package them up.  There isn’t anything necessarily special (yet?) in our work on WP itself that is directly beneficial – beyond the use of the OWP.

But since our “design” is that PWP is a WP that is packaged – it then becomes important that we don’t say/do anything in a WP that would preclude the packaging of such things.   That’s why shoulds are better than musts for many things, as it leaves the opening for not doing them in cases where it isn’t necessary (or even logical).


From: Dave Cramer <dauwhe@gmail.com>
Date: Monday, August 14, 2017 at 9:27 AM
To: W3C Publishing Working Group <public-publ-wg@w3.org>
Subject: On Spreadsheets, Birthday Cards, and the Nature of Publications
Resent-From: <public-publ-wg@w3.org>
Resent-Date: Monday, August 14, 2017 at 9:27 AM

As we've discussed various issues on GitHub, our esteemed colleague from Adobe has provided examples of potential web publications which seem, to my dinosaur dead-tree publisher eyes, to be rather far removed from what I think of as publications.

Leonard has often spoken of "ad-hoc publications," such as memos, reports, letters—the output of tools that are categorized with words like "office" and "document" and "productivity". And of course we can can make such documents using HTML/CSS/JS, and we should, ’cause HTML is cool and CSS is awe-

But how would a birthday card or a spreadsheet benefit from being a web publication? They are unlikely to consist of more than one primary resource, and the existing web platform seems entirely capable of providing a good user experience, except for one thing. Such "ad-hoc publications" would benefit from being packaged and portable.

But do we need to design web publications around these types of documents, when packaging is likely the only feature they require? Can we usefully separate the concept of packaging from other aspects of web publications?

Received on Monday, 14 August 2017 14:00:12 UTC

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