- From: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
- Date: Wed, 23 Nov 2016 13:40:53 +0100
- 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>
- Message-ID: <CA+KS-12K7pLpjPqRsaiJERjQbykgthkgX0cmbOyTqXeyBrTjew@mail.gmail.com>
It all depends on the semantics that you'd like to associate to both "href" and "hrefsrc", for the manifest inside a package, the opposite is much more natural for me. Also keep in mind that you're advocating keeping the content intact, something that I don't really consider realistic at this point (I've listed multiple reasons before). Also, for a publication which only exists initially in a packaged form, only having "hrefsrc" and no "href" would look really weird. 2016-11-23 13:30 GMT+01:00 Leonard Rosenthol <lrosenth@adobe.com>: > Actually that would be backwards, Hadrien J. > > > > 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 > -- Hadrien Gardeur Co-founder, Feedbooks http://www.feedbooks.com T: +33.6.63.28.59.69 E: hadrien.gardeur@feedbooks.com 54, rue de Paradis 75010 Paris, France
Received on Wednesday, 23 November 2016 12:41:47 UTC