Re: For the discussion on the PWP

Actually that would be backwards, Hadrien ☺.

href is the URL as found inside content in the package – your “index” if you will.   And hrefsrc is the URL where the actual content lies.   So when referring to a resource that is referenced by an absolute URL, it would instead be:

{"href": "http://www.louvre.com/monalisa.jpg", "hrefsrc": "/images/monalisa.jpb", "type": "image/jpeg"},

Leonard

From: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
Date: Wednesday, November 23, 2016 at 9:15 PM
To: Leonard Rosenthol <lrosenth@adobe.com>
Cc: Ivan Herman <ivan@w3.org>, W3C Digital Publishing IG <public-digipub-ig@w3.org>, Ric Wright <rkwright@geofx.com>, Laurent Le Meur <laurent.lemeur@edrlab.org>
Subject: Re: For the discussion on the PWP

And for B – your use of hrefsrc is exactly the type of thing that I would envision as well.  HOWEVER, you are only looking at the easy case – the base HTML files.   Now try to do the same thing for an image referenced by c001.html – in that case, you need TWO hrefsrc – one for the canonical URL and one for the relative mapping inside the package. This also raises the really hard (from a security perspective) case of when c001.html (in this instance) uses an absolute URL to refer to something (eg. our Mona Lisa example at http://www.louvre.com/monalisa.jpg) - but now you need to make this fully self-contained AND not modify the HTML.

"href" would then point to the resource inside the package and "hrefsrc" to the canonical URI, it's exactly the same as the example for HTML.

Hadrien