Re: [dpub-loc] Draft update

Hi Ivan, all,

Thanks! I find it to be a very clear statement of the problem. Some
comments:

Line 19
> reflecting the unpacked state in terms of (file) structure the *Canonical
Locator* of the Mona Lisa image is `
http://book.org/published-books/1/mona_lisa.jpg`

_I assume you mean `http://book.org/published-books/1/*img/*mona_lisa.jpg`?_

_Also, I think we agreed that **L** doesn't have to be different than
**Lu**, maybe we should keep that documented here as well._

Line 32
> * **M** contains a reference to **L**, and **M** is also available in all
the different states of **P**.

_This would mean that all different states of **P** have references to
**Lp** and **Lu**, right? I would lessen the constraint:_

* **M** contains a reference to **L**, and ***L*** is also available in all
the different states of **P**.

_Given your possible answer on Q1, you can get to **M** via **L**, and thus
a connection can then be made between the different states of **P** via
**M**, so this change would not introduce conflicts_

Line 37
> Although our discussions should be technology dependent, it is clear that
this aspect of a PWP Processor, more exactly the implementation strategy
thereof, resembles that of Service Workers. Ie, if Service Workers are not
available, then the implementation of a PWP Processor may require to
implement some of the Service Worker features.

_I assume you mean technology *in*dependent? :)_

Line 51
> 2. As a consequence, **M** contains the list of states (and their
Locators) that are available on **S**. In other words, it “knows” **Lp**
and **Lu**, together with their media types.

_Given my remark above, I agree :)_

Line 60
>    * If the preferred state is the packed one, then **Lp** accessed,
unpacked, and the image is localized within the unpacked content (and that
usually means using the relative URL as some sort of a file system path
within that unpacked content)

_To be clear, this means the PWP on **Lp** is downloaded entirely and the
image is retrieved client-side, right? I agree that this is a viable
solution, with minimal server requirements. But if your server is smarter,
it can retrieve that image client-side and return that image directly. Do
we need to fix that functionality as either client-side or server-side?
Can't we just define functionalities and let implementers implement as they
see fit? Or is that just crazy talk? :)_

I fully agree on your possible solution to Q1, no comments there :)

Thanks, and 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 | URL:
http://users.ugent.be/~bjdmeest/

2016-02-11 18:28 GMT+01:00 Ivan Herman <ivan@w3.org>:

> Ben, everybody
>
>
> I have given some thoughts over the last discussion we had yesterday at
> the end of the call. I have spent some time to make a more detailed writeup
> over those questions; instead of sending around a very long mail, I have
> uploaded a separate document onto the repo:
>
> https://github.com/w3c/dpub-pwp-loc/blob/gh-pages/drafts/ivans-musings.md
>
> Comments/changes/issues please!
>
> To increase your appetite, here are the two questions I was musing about:
>
> • Q1: What is the answer of the server to a 'HTTP Get
> http://book.org/published-books/1' request?
> • Q2: How does a PWP Processor accesses the Mona Lisa image when '
> http://book.org/published-books/1/img/mona_lisa.jpg' is requested by the
> Reading System?
>
> Caveat: my regrets for the next call. I am double booked in February, and
> next time I must go to my other call:-(
>
> Cheers
>
> Ivan
>
>
> On 11 Feb 2016, at 13:50, Ben De Meester <ben.demeester@ugent.be> wrote:
>
> Hi all,
>
> I updated the markdown on the git repo (
> https://github.com/w3c/dpub-pwp-loc/blob/gh-pages/locators.md), trying to
> incorporate the discussion of the previous call.
>
> I also added 2 new sections: functionalities (i.e., what specific
> functionalities are needed to support PWPs, e.g., mapping from canonical to
> state locator, displaying a resource, etc.), and issues.
>
> Issue 1 is the issue as discussed last on the call, issue 2 is one Ivan
> mentioned in his last comment to the previous draft: what do you get when
> GETting the unpacked PWP?
>
> Comments are most welcome!
>
> Kind regards,
> Ben
>
>
>
> ----
> 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
>
>
>
>
>