W3C home > Mailing lists > Public > public-digipub-ig@w3.org > July 2016

Re: Some comments on use cases - #1

From: Mike Perlman <perlmanm@me.com>
Date: Thu, 14 Jul 2016 08:20:30 +0200
Cc: "Siegman, Tzviya - Hoboken" <tsiegman@wiley.com>, Leonard Rosenthol <lrosenth@adobe.com>, "DPUB mailing list (public-digipub-ig@w3.org)" <public-digipub-ig@w3.org>
Message-id: <49469300-1063-4015-A8B0-4DAD2F6051AD@me.com>
To: Charles LaPierre <charlesl@benetech.org>
FYI, I reported on GitHub that in the Use Cases document the link for “Latest Published Version” is a 404.
Also, I just noticed that under “Abstract” the link to the main spec is to the 26 November 2015 document and not the 9 July 2016 draft. 

It would be very helpful if the links at the top to versions was clearer and also if each release had a tag in GitHub.


Regarding this discussion on use cases, I think it would be very helpful to produce a user-flow diagram that compliments the Manifest labyrinth. Right now it is not clear what is meant by the difference between online and offline access of a PWP. While it is aspirational that the process should be seamless, how would that work? 

For example, what happens if Shoshana’s iPad crashes on the train? Will she be able to reboot and continue working? How will she do this if there is no internet access? Does Shoshana enter http://www.url.xx or file:///localurl?

And what happens the next morning on the train, if Shoshana updates IOS overnight and all the caches are wiped in the process? Will she lose offline access to her entire library of PWPs?

> On 13 Jul 2016, at 09:47, Charles LaPierre <charlesl@benetech.org> wrote:
>> On Jul 13, 2016, at 12:34 PM, Siegman, Tzviya - Hoboken <tsiegman@wiley.com <mailto:tsiegman@wiley.com>> wrote:
>> 2.1.5 There should be a very smooth transition between offline and online states of the same publication
>> As far as I can tell – this is identical to 2.1.4, just worded differently.  Is there any reason we need both or can we remove this section entirely?
>> TS: The distinction we made is that in 2.1.4 the PWP should be available both online and offline. In 2.1.5, the use case is about the user experience, meaning the burden should not be on the user. Do we need to clarify the distinction?
> I agree with Tzviya here.  We really need to make it clear that yes even though a PWP must be able to be used both online and offline we need the process in terms of the user experience to be seamless and as easy as possible to switch between both states.  You don’t want to have to tell the user, well install this plugin on this specific browser in order to take your publication offline. 
> Thanks
> Charles LaPierre
> Technical Lead, DIAGRAM and Born Accessible
> E-mail: charlesl@benetech.org <mailto:charlesl@benetech.org>
> Twitter: @CLaPierreA11Y
> Skype: charles_lapierre
> Phone: 650-600-3301

Received on Thursday, 14 July 2016 06:21:04 UTC

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