Re: Identifying a book on the Web today from Hadrien Gardeur on 2017-08-04 (public-publ-wg@w3.org from August 2017)

From: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
Date: Fri, 4 Aug 2017 11:37:29 +0200
To: Ivan Herman <ivan@w3.org>
Cc: MURATA Makoto <eb2m-mrt@asahi-net.or.jp>, Baldur Bjarnason <baldur@rebus.foundation>, Benjamin Young <byoung@bigbluehat.com>, David Wood <david.wood@ephox.com>, W3C Publishing Working Group <public-publ-wg@w3.org>
Message-ID: <CA+KS-139PPedF=+gR9D3NLxydfK+YRAjQ0y+mKwUKwwpDNzMpw@mail.gmail.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.

Hadrien

Received on Friday, 4 August 2017 10:00:34 UTC