- From: Bill McCoy <bmccoy@idpf.org>
- Date: Tue, 8 Sep 2015 11:10:22 -0700
- To: Ivan Herman <ivan@w3.org>
- Cc: Leonard Rosenthol <lrosenth@adobe.com>, Olaf Drümmer <olaf@druemmer.com>, W3C Digital Publishing IG <public-digipub-ig@w3.org>, Deborah Kaplan <dkaplan@safaribooksonline.com>, Ralph Swick <swick@w3.org>, Bill Kasdorf <bkasdorf@apexcovantage.com>
- Message-ID: <CADMjS0abi+xLAp7=XYgkTsdU73uPQBnpxUVOBSJQr+0fUNk1wA@mail.gmail.com>
HI, to (belatedly) chime in on this: I am fine with the definitions proposed. I personally think it's a bit narrow to put (even as SHOULD) "adapt to the user's needs" in either the definition of Web Document or Portable Web Document, because there are many examples (comics for one) where adaptation may not be practical, and adaptability is to me only one of many useful properties. But it is a very very important property, one which we have always strived to enable with EPUB, so I can definitely live with it. I would also personally also prefer to define two more general terms, "Portable Document" (without relation to Web) and "Web Document" or "Web Content" (without relation to portability), and then define "Portable Web Document" as simply the intersection of these two concepts. That to me would be a more accurate depiction of the ecosystem, and would make it simple to diagram it, with PDF lying within the bubble of "Portable Document" but clearly well outside the intersection with "Web Document" and EPUB today (as most commonly used) perhaps lying just at the boundary of "Web Document" but definitely not yet fully realizing everything in the Venn diagram of the intersection. But this may just be my own way of looking at it, and I certainly have no objections if this (after all Web-centric) group prefers Ivan's decomposition (assuming we are all in agreement that Web != browser, i.e. that native apps consuming Web-based resources are fully in scope). I am just a bit nervous then that we wouldn't have explicitly defined what is e.g. PDF in our nomenclature which could lead to confusion later. --Bill On Tue, Sep 8, 2015 at 6:43 AM, Ivan Herman <ivan@w3.org> wrote: > > On 08 Sep 2015, at 15:31 , Leonard Rosenthol <lrosenth@adobe.com> wrote: > > While I agree with Olaf’s position, I don’t think the “good” terms would > serve us well. > > Instead, I’d like to build on Ivan’s point in the use of SHOULD and make > two small changes to the Portable (Web) Document definition: > > A **Portable (Web) Document** is a Web Document that should provide a > graceful degradation when presented to the user even offline. A Portable > Web Document should also be able to adapt to the user's needs. > > > I can live with that. > > Anybody else? Or should we declare victory? (There are some other terms to > define:-) > > Ivan > > > How’s that?? > > Leonard > > From: Ivan Herman > Date: Tuesday, September 8, 2015 at 12:22 AM > To: Olaf Drümmer > Cc: W3C Digital Publishing IG, Leonard Rosenthol, Deborah Kaplan, Ralph > Swick, Bill Kasdorf, Bill McCoy > Subject: Re: [Glossary] Definition of a portable document (and other > things...) > > > On 07 Sep 2015, at 21:39 , Olaf Drümmer <olaf@druemmer.com> wrote: > > Would this discussion become easier if based on a starting point like: > > On 7 Sep 2015, at 16:48, Ivan Herman <ivan@w3.org> wrote: > > [[[ > A **Web Document** is a uniquely identifiable and curated set of > interrelated Web resources. A Web Document should be constructed of > resources whose formats enable (individually or in conjunction with other > resources in the same Web Document) a graceful adaptation to the users' > needs. > > A **Portable (Web) Document** is a Web Document that has enough > information to ensure a graceful degradation when presented to the user > even offline. A Portable Web Document should also include enough > information for a graceful adaptation to the user's needs. > ]]] > > > we distinguished between > **Web Document** and **good Web Document** > and also between > **Portable (Web) Document** and **good Portable (Web) Document** > > Requirements like "graceful adaptation to the users' needs" are all fine, > but some web documents might just not adapt gracefully and still would have > to be called a web documents… > > > I am a bit afraid of overcomplicating things by introducing too many > terms. This is why it says "should" and not a "must": this is a pragmatic > choice... > > Ivan > > > > > Just my 2 cents… > > > Olaf > > > > ---- > 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 > > > > > > > ---- > 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 > > > > > -- Bill McCoy Executive Director International Digital Publishing Forum (IDPF) email: bmccoy@idpf.org mobile: +1 206 353 0233
Received on Tuesday, 8 September 2015 18:10:50 UTC