Re: [dpub-loc] Use Cases

Sorry I missed the call, as I would have voted against using github in this manner.  But since things have already started there, so be it.

Leonard

From: Ben De Meester <ben.demeester@ugent.be<mailto:ben.demeester@ugent.be>>
Date: Thursday, February 4, 2016 at 1:08 PM
To: Leonard Rosenthol <lrosenth@adobe.com<mailto:lrosenth@adobe.com>>
Cc: "DPUB mailing list (public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>)" <public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>>
Subject: Re: [dpub-loc] Use Cases

Hi Leonard,

As agreed on the call, we will consolidate all use case discussion on the github repo (https://github.com/w3c/dpub-pwp-ucr). I will make new issues there per use case type, and add your comments and my answers :).

Thanks!
Kind regards,
Ben

Ben De Meester
Researcher Semantic Web
Ghent University - iMinds - Data Science Lab | Faculty of Engineering and Architecture | Department of Electronics and Information Systems
Sint-Pietersnieuwstraat 41, 9000 Ghent, Belgium
t: +32 9 331 49 59 | e: ben.demeester@ugent.be<mailto:ben.demeester@ugent.be> | URL:  http://users.ugent.be/~bjdmeest/


2016-02-03 16:55 GMT+01:00 Leonard Rosenthol <lrosenth@adobe.com<mailto:lrosenth@adobe.com>>:
I have to disagree with your creating a new flavor – cached.  Caching is a feature of an RS and NOT part of a file format, such as PWP.

However, if you simply replace all instances of cached with local or downloaded, then so far so good for annotating across states.

The concept of public and private annotations is out of scope and has nothing to do with PWP.

Leonard

From: Ben De Meester <ben.demeester@ugent.be<mailto:ben.demeester@ugent.be>>
Date: Wednesday, February 3, 2016 at 1:56 PM
To: "DPUB mailing list (public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>)" <public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>>
Subject: [dpub-loc] Use Cases
Resent-From: <public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>>
Resent-Date: Wednesday, February 3, 2016 at 1:57 PM

Hi all,

Below, you can find some use cases I thought of, where I think the locators should be resilient to.
Something to discuss at 3PM UTC :)

state-wise, I currently assume the following:
* a PWP can be unpacked or packed
* a PWP can be online (http), offline (cache), or downloaded (file). Other variations like accessing via FTP etc. are not excluded.

## Annotating across states

*1 Writer Annie has her book published on her own web space as a PWP [http/unpacked]. Reader Bob reads it online, and selects a nice quote to bookmark via its browser PWP bookmarking plugin: PWPMark-plugin.
*2 Writer Annie has her book published on her own web space as a PWP [http/unpacked]. Reader Bob caches the PWP [cache/unpacked], reads it offline, and selects a nice quote to bookmark using PWPMark-plugin.
  *2a When Bob re-opens the offline PWP, the booksmarks are shown via PWPMark-plugin
  *2b When Bob re-visits the original PWP, PWPMark-plugin can also show Bob's bookmarks in the online version.
*3 Writer Annie has her book published on her own web space as a PWP [http/packed]. Reader Bob opens it online using the PWP reading plugin PWPRead-plugin, and selects a nice quote to bookmark via PWPMark-plugin.
*4 Writer Annie has her book published on her own web space as a PWP [http/packed]. Reader Bob caches it using a plugin [cache/packed], and selects a nice quote to bookmark via PWPMark-plugin.
*5 Writer Annie has her book published on her own web space as a PWP, both packed [http/packed] as unpacked [http/unpacked]. Reader Bob reads [http/unpacked] online and selects a nice quote to bookmark via PWPMark-plugin. Then, Bob downloads [http/packed] to his local filesystem [file/packed] to open in his reading system of choice, namely, PWPRead-soft.
  *5a PWPRead-soft synchronizes with Bob's PWPMark profile, and can show Bob's bookmarks when he continues reading [file/packed]

## Private/Public annotations

*1 Bob is reading in PWPRead-soft, and makes private annotations. These annotations can be - via Bob's PWPMark profile - synced across devices.
*2 Bob makes a couple of his annotations public. Chris also has a PWPMark profile, and choses to show all public annotations whilst reading using PWPRead-plugin. Chris sees Bob's annotations whilst reading the same document.
  *2a this could be extended to more 'fine-grained' user access, e.g., two lawyers annotating the same contract as a PWP on their own computer. These annotations are shared only in specific groups, depending on what the PWPMark software allows.

Kind regards,
Ben
Ben De Meester
Researcher Semantic Web
Ghent University - iMinds - Data Science Lab | Faculty of Engineering and Architecture | Department of Electronics and Information Systems
Sint-Pietersnieuwstraat 41, 9000 Ghent, Belgium
t: +32 9 331 49 59<tel:%2B32%209%20331%2049%2059> | e: ben.demeester@ugent.be<mailto:ben.demeester@ugent.be> | URL:  http://users.ugent.be/~bjdmeest/