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

Re: [dpub-loc] meeting 20160302

From: Leonard Rosenthol <lrosenth@adobe.com>
Date: Wed, 2 Mar 2016 21:05:05 +0000
To: Ivan Herman <ivan@w3.org>
CC: Ben De Meester <ben.demeester@ugent.be>, W3C Digital Publishing IG <public-digipub-ig@w3.org>
Message-ID: <55C0F4E3-4708-4D8F-9780-DA005D8C03B8@adobe.com>
Maybe just put the word “AND” somewhere there…

Otherwise, seems like we are indeed on the same page – thanks for doing the work on the picture.

From: Ivan Herman <ivan@w3.org<mailto:ivan@w3.org>>
Date: Wednesday, March 2, 2016 at 7:07 AM
To: Leonard Rosenthol <lrosenth@adobe.com<mailto:lrosenth@adobe.com>>
Cc: Ben De Meester <ben.demeester@ugent.be<mailto:ben.demeester@ugent.be>>, W3C Digital Publishing IG <public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>>
Subject: Re: [dpub-loc] meeting 20160302


On 2 Mar 2016, at 12:34, Leonard Rosenthol <lrosenth@adobe.com<mailto:lrosenth@adobe.com>> wrote:

Ivan – a couple of comments on the picture.

First and foremost – in what cases would you expect to get back from the HTTP request a “Link Header” but NOT a result type of HTML, Manifest or Package?

I do not expect that. I am not sure how to express on the diagram, but the idea is that the PWP Processor looks at the return data (and makes a switch according to the media type) AND also looks at the LINK response header. Any idea what the usual way of properly expressing it on the diagram?

The previous diagram had this, because it included two serial steps, but it is simply difficult to get it visually right...

Its not clear how/when that happens.  And is it in addition or instead – that’s also not clear from the Mextra?

Addition. There are two sources for M, the PWP client processor has to be prepared to check both. Whether they will be delivered or not (ie, whether there will be a <link> element or whether there will be a LINK header) is a server setup issue, but the PWP client processor should not rely on a particular setup.


Minor thing – The PF1 under package is all caps instead of Pf1.

Thanks, took care of this.

Ivan


Otherwise, looks good!

From: Ivan Herman <ivan@w3.org<mailto:ivan@w3.org>>
Date: Wednesday, March 2, 2016 at 6:24 AM
To: Ben De Meester <ben.demeester@ugent.be<mailto:ben.demeester@ugent.be>>
Cc: W3C Digital Publishing IG <public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>>
Subject: Re: [dpub-loc] meeting 20160302
Resent-From: <public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>>
Resent-Date: Wed, 2 Mar 2016 11:24:45 +0000


On 2 Mar 2016, at 09:26, Ben De Meester <ben.demeester@ugent.be<mailto:ben.demeester@ugent.be>> wrote:

Hi all, sorry for the late notice,

The next locators TF meeting will be on 2 March (so today) at 1500 UTC [1]

Agenda:

* Going over http://w3c.github.io/dpub-pwp-loc/drafts/PWPClient.png


I have actually made a (hopefully) improved version:

http://w3c.github.io/dpub-pwp-loc/drafts/PWPClient2.png


http://w3c.github.io/dpub-pwp-loc/drafts/PWPClient2.<http://w3c.github.io/dpub-pwp-loc/drafts/PWPClient.png>svg

The major change (apart from making it horizontal, better if we want to use it in presentations, for example) is a separation between a manifest file and the metadata therein. We agreed that the manifest file is more general, and the metadata (namely the part we are discussing here) is only part of it and more conceptual. The linkage, HTTP, etc, result in the manifest file, and not in the metadata; extracting the metadata is an extra logical step. This is now, hopefully, better reflected in the diagram

Ivan

* (closely related) reaching consensus over https://github.com/w3c/dpub-pwp-loc/blob/gh-pages/drafts/ivans-musings.md, to get to a first draft of a locators spec going

Kind regards, and hear you later!
Ben

[1] http://www.timeanddate.com/worldclock/fixedtime.html?msg=DPUB+Locators&iso=20160210T15


IRC: #dpub-loc

Topic: DPUB IG Locator Task Force
Date: Every Wednesday, from Wednesday, January 13, 2016, to Wednesday, December 21, 2016
Time: 10:00 am, Eastern Standard Time (New York, GMT-05:00)
Meeting Number: 640 269 372
Meeting Password: Please obtain your meeting password from your host.
-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://mit.webex.com/mit/j.php?MTID=mec073df570c69d4340ca47564e81b37a

2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: Please obtain your meeting password from your host.
4. Click "Join".

To view in other time zones or languages, please click the link:
https://mit.webex.com/mit/j.php?MTID=maa411ca7bcf238f6c25818c4ef58f654


-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code.
US Toll Number: +1-617-324-0000<tel:%2B1-617-324-0000>

Access code:640 269 372
Mobile Auto Dial:+1-617-324-0000<tel:%2B1-617-324-0000>,,,640269372#




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







----
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 Wednesday, 2 March 2016 21:05:39 UTC

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