Thanks for your suggestion!

MiniApp Packaging is currently using zip. My understanding is that EPUB cannot meet some needs, so it is not used.

Related:

• Mention EPUB 3 WG in the Coordination section of the charter miniapp#84
• https://github.com/w3c/miniapp-packaging/blob/main/docs/explainer.md#4-comparison-with-other-packaging-technologies
• https://github.com/WICG/resource-bundles/blob/de2c4f16d1d0239a7669747c572f40a4b633e1ec/faq.md#q-should-w3c-miniapp-packaging-use-this-bundle-format-instead-of-zip

Thanks @xfq. Yeah, the Publishing Community Group (PCG) was actually started from almost end of last year which was after the discussion here related to Epub. Epub 3 is a very well defined and widely used zip based format which mostly focusing on offline reading (or publishing). As you pointed out in w3c/miniapp#84 it might be possible to use OCF as existing wheel to actually help spreading mini app to widely usage.

Because there are already many of published applications started to support epub3 (since 2012) one of the benefit of adopting epub3 is existing reading application might be able to support MiniApp without large amount of work. Hence this could help spreading MiniApp.

So if member in this Interesting Group would be open to discuss I think we can try to discover more on the possibility as well as challenges. How do you think.

But yeah, I opened this as issue also because I think it might be worthful to mention potentially use epub3 as one of package format. I think I joined Interesting Group as well so if needed I am open to discuss in your group meeting if not too late for me.

Here's the transcript of the CG meeting discussing this issue this Thursday: https://www.w3.org/2021/04/22-miniapp-minutes.html#t02

I'm intrigued by offline reading support? I think this would be worthwhile to investigate. MiniApps that could fully function in offline mode could open up new opportunities.

Yup, it's a spec mostly focusing on offline reading/application