Re: A question on RWPM: why the 'metadata' tag?

>
> Could someone explain me how the title there will conflict with the
> <title> element of the document referencing the manifest? How the
> language there will conflict with the lang or xml:lang attributes of
> the document referencing the manifest? How the author there will
> conflict with the html meta elements in the document referencing the
> manifest?


They don't conflict. All metadata defined in the manifest are metadata
about the collection, while all the elements that you've listed apply to a
specific resource.



> And finally an oooold question: why do we have a list of
> resources at all?
>

In the case of Readium, we use the list of resources for two things right
now:

   - prefetching resources (using HTTP Link header + rel=prefetch)
   - offline access using a Service Worker (a script can easily fetch the
   manifest, extract the list of resources then cache them using CacheStorage)

In both RWPM and the WP infoset, the list of resources remains optional.


Example: the html document is in english, ltr with title "foo" while
> the manifest, referenced from there, says the title is "bar", the
> language is hebrew and the direction rtl. What happens?
>
> Note: when I mean "conflict" there, I mean "what will be the expected
> behaviour of a Web browser's rendering engine?".
>

IMO, nothing at all. The browser will entirely ignore collection level
metadata when rendering.