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

Re: [dpub-loc] Draft update

From: Ivan Herman <ivan@w3.org>
Date: Thu, 11 Feb 2016 18:28:03 +0100
Cc: W3C Digital Publishing IG <public-digipub-ig@w3.org>
Message-Id: <B933D7CC-8F29-48EC-89A1-9F52D61AA911@w3.org>
To: Ben De Meester <ben.demeester@ugent.be>
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:


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



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

Received on Thursday, 11 February 2016 17:28:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 25 April 2017 10:44:40 UTC