Into a recent talk at en.source Scriptorium, it has been told that nsPage can be viewed merely as a proofreading tool, the ns0 transclusion/text being the real core of source content.

I have a different opinion, since I see nsPage code as the real core of source content, ns0 being merely a derived content, that could be obtained with complete automation with a set of data wrapped into a Lua/Scribunto set of structural data (wrapping any needed data for header template and for pages tag), so that any ns0 page/subpage could be obtained with a template {{Derive|index base page name}}.

Giving to nsPage such a core content role, it will be much simpler to wrap into it TEI data, and any POV related to different styles of chapter/sections structure/naming could be avoided; html rendering will be unchanged, so saving IMHO conversion in ePub.

What do you think about?

Alex brollo