Re: [Glossary] Portable Digital Document's states

So… it seems that we do have two dimensions for 'states. Because Ascii art can go very bad with different clients, I created images as attachments. The first attached image shows is the offline/online vs. packed/unpacked situation with some typical usage scenarios.

However, offline/online may be an elusive notion. I would think (although I am not sure) that it may be more precise to differentiate along access methods: in practice, if we are in a Web setting, the difference may be whether the content is accessed via an HTTP(S) protocol, through Web protocols, or whether the content is accessed through a file system. So I created a second image doing that.  Note the difference between the two: if I have an unpacked set of files in a folder, the same content can be accessed via the file system or via a server running on my machine with the same content served through HTTP. Although, in both cases, the content is accessed offline, the access method is different.

Whichever four states we choose (and their definitions should be properly pinned down) the real question for this Interest Group is which of these states are of real interest (sic!) for the group and for the digital publishing community at large. And, in fact, I believe all four are. Indeed,

- the packed/unpacked dimension is (obviously) of interest for the details and requirements on packaging; ie, it influences the details on an architectural view for some sort of a unified approach for readers' core (our service worker based scenario)

- the offline/online or, alternatively, file or protocol access dimension raises questions on identifiers. Do we use generic identifiers overall, regardless of locations, how should the references within a Portable Web Document be organized to ensure a unified identification scheme. (I cc-d BillK explicitly, because I know these questions are of a real interest to him:-)

If we agree with these two dimensions, we can go forward and define them more thoroughly

Ivan

> On 18 Sep 2015, at 18:21 , Leonard Rosenthol <lrosenth@adobe.com> wrote:
> 
> Yes, I believe that caching is more an implementation issue than a format or design issue.
> 
> From: Ivan Herman
> Date: Friday, September 18, 2015 at 9:07 AM
> To: Leonard Rosenthol
> Cc: "Brady com>", W3C Digital Publishing IG, Ralph Swick
> Subject: Re: [Glossary] Portable Digital Document's states
> 
> 
>> On 18 Sep 2015, at 14:35 , Leonard Rosenthol <lrosenth@adobe.com <mailto:lrosenth@adobe.com>> wrote:
>> 
>> [Sorry for coming in late]
>> 
>> I agree with Brady – there is a huge difference between package/unpackaged and online/offline.  The original terms made more sense to me as they focused on whether the content was usable without standard web protocols (aka offline) or not.
> 
> Indeed. As I say below, we seem to have two different dimension for 'states' and not one dimension only. I can be unpacked and offline, and packed and online. So the question is whether defining two types of states (offline/online and packed/unpacked) is enough. Ie, whether treating cached separately on any dimension is necessary or not (my feeling is that it is not, it is more of an implementation issue).
> 
> Ivan
> 
> 


----
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