Re: [dpub-loc] New version of the PWP Client processor diagrams

First, simple change.  On the package being returned, it shouldn’t be M1 since it then goes to M2 and it’s not clear what the difference is.  Just make that M2, since it’s no different than the manifest directly case.

Apparently, however, I missed a conversation about how the manifest might come “inline” some returned HTML.   Can someone explain the use cases for this and when this would be used (or even useful)?

Next, what’s the difference between M1,1 and M3 – I would assume that they are identical, yes?  If so, let’s call them the same thing – otherwise someone (like I am doing) will assume they are different things.  And if I am correct that M1,1 from the link in head – what would happen if you ALSO have a link HTTP header?   Do you really get two copies of M3??   That gets confusing in the diagram.

Bottom line – I wonder if this is getting too complex??

Leonard

From: Ivan Herman <ivan@w3.org<mailto:ivan@w3.org>>
Date: Thursday, March 3, 2016 at 7:32 AM
To: W3C Digital Publishing IG <public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>>
Subject: [dpub-loc] New version of the PWP Client processor diagrams
Resent-From: <public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>>
Resent-Date: Thu, 3 Mar 2016 12:32:30 +0000

Here they are:

https://w3c.github.io/dpub-pwp-loc/drafts/PWPClient3.svg
https://w3c.github.io/dpub-pwp-loc/drafts/PWPClient3.png


I think I have incorporated everything that we discussed yesterday.

Ivan

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