See minutes online for a more detailed record of the discussions.
(This is issue #222.)
EPUB3 had hints for special things like MathML; the question is whether it is necessary to have these in WP? The consensus (and the experience of implementers) is that these were not reliable, and it may not be necessary to translate them to WP. However, the WG will set up a list somewhere of those properties for roundripping purposes.
(This is issue #223.)
EPUB3 has features like page lists, landmarks, list of tables, etc. What to do about these in WP? Beyond roundtripping, some of these may be very important; e.g., page lists may be considered to be as important as Table of Contents for accessibility purposes.
The discussion was a bit bifurcated on the exact nature of WP and the reason of roundtripping. There was no final decision on the call, the discussion continues on the issue thread.
(This is issue #205.)
At the moment there is no clear definition on what the “boundaries” of a WP are, although there are infoset items for resources and reading order. The question is what should happen to additional resources like CSS or other that are referred to from resources. The exact goals must be established for offlining, caching, packaging, etc, where this issue is particularly relevant.
There was no final decision on the call, the discussion continues on the issue thread.