Re: Identifying a book on the Web today

Dear Makoto, 

From my remote island, I will have three comments:
- The title of this thread (Identifying a book on the Web today) and the issue of URLs for resources embedded in a PWP are not related, which makes following threads (and searching in threads in the future) rather hard.
- we agreed to tackle issues with PWPs after WPs are clear. Your issue definitely seems to be related with PWPs.
- I still don't see why *all* discussions have moved from github to emails. The expected split btw generic and specific discussions, envisaged by Tzviya initially if I recall well, does not work in practice IMHO. 

Best,
Laurent



> Le 4 août 2017 à 12:05, MURATA Makoto <eb2m-mrt@asahi-net.or.jp> a écrit :
> 
> 
> 
> 2017-08-04 18:37 GMT+09:00 Hadrien Gardeur <hadrien.gardeur@feedbooks.com <mailto:hadrien.gardeur@feedbooks.com>>:
> For PWP the situation is a little bit more complex because the package may be 'elsewhere', ie, not on the Web but, if we regard (which I think is the case) a PWP some sort of a frozen version of a WP through some packaging, then the internal structure of a PWP would 100% reflect its 'exploded' WP ancestry. 
> 
> Bottom line: I do not see the problem. But that may only be me.
> 
> For a PWP that has a WP ancestry, this is fairly easy to handle and we can simply references all resources using their URL, no matter the context (packaged or not).
> For PWP with no prior WP ancestry, this might be more difficult, but I don't think that this is an issue that needs to be addressed now. 
> 
> I do not think so.  I think that this issue is extremely important for 
> the unification of EPUB and the Web.  To me, details of manifests 
> are much less important.
> 
> Regards,
> Makoto