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

Re: [Glossary] Definition of a portable document (and other things...)

From: Bill McCoy <bmccoy@idpf.org>
Date: Thu, 10 Sep 2015 11:07:29 -0700
Message-ID: <CADMjS0aT5jdA31KSCXCfqe+F6chemJc3RgtYxMv4eF+=QgExbg@mail.gmail.com>
To: Olaf Drümmer <olaf@druemmer.com>
Cc: Leonard Rosenthol <lrosenth@adobe.com>, Ivan Herman <ivan@w3.org>, W3C Digital Publishing IG <public-digipub-ig@w3.org>, Deborah Kaplan <dkaplan@safaribooksonline.com>, Liam Quin <liam@w3.org>, Ralph Swick <swick@w3.org>
Yes, and let me piggyback on this to try to make my point (to Ivan) more

I think that the ability to reliably *capture a snapshot and use it offline*
is a righteous *feature* for a Web Document to offer. And, the results of
that snapshot might be itself a (new instance of a) "Portable [Web]

But to me that does *not* make the original Web Document itself a "Portable
Web Document" because what is captured with the snapshot is not a true
representation of the original document.

Leonard's dashboard example is a perfect illustration. Take a dashboard
like http://status.aws.amazon.com/ .  I can't imagine calling that a
"Portable Web Document".

I think we are here confusing offline features of Web Documents with what
is a Portable [Web] Document. I don't believe they are at all the same
thing. And I am still convinced we can come up with a definition for the
latter that is neither anthropocentric nor fundamentally subjective.


On Thu, Sep 10, 2015 at 10:58 AM, Olaf Drümmer <olaf@druemmer.com> wrote:

> But we may want to keep in mind that being able to capture a snapshot
> (kind of a 'frozen state') could be a valid feature, as much as being able
> to update when (after having been offline) being online again. Not sure
> whether a 'deep freeze' switch would be a metadata item in the portable
> document (== do not update me), or whether the document would have to be
> written into a portable document such that it simply doesn't update it
> itself anymore.
> Olaf
> On 10 Sep 2015, at 18:16, Leonard Rosenthol <lrosenth@ADOBE.COM> wrote:
> One of the best examples/use cases that we have in this area is a
> “Dashboard”, as you might get to visualize any sort of data.
> You would like this dashboard to be portable – so that it can be used both
> online and offline.  But in the online case, the document should be able to
> get the latest set of data and then store that away for offline use (aka
> caching, but explicit instead of implicit).
> So yes – I think we are now getting into the “state” of the document.  It
> is portable but can be in different states.


Bill McCoy
Executive Director
International Digital Publishing Forum (IDPF)
email: bmccoy@idpf.org
mobile: +1 206 353 0233
Received on Thursday, 10 September 2015 18:07:58 UTC

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