Could you please answer my question below:

"What I rather would suggest is that the core team defines the complete datamodel according to the roadmap first . In this way developers can step in and enhance the store with their own components around a solid datamodel. This will avoid mismatching datamodels and avoid spending many resources in engineering back to a DNN store. I would like to know if somebody has a data model of the entire store and/or its scripts to script in into a database to allow developers to continue their own store products."

I want to help, but I cannot step in if their is no solid architecture. If I start building an own store, I would also make a solid architecture first. Starting with functionalities (your roadmap), but also with a data model which will support all these functions. I am looking for the datamodel right now. If I keep close to this datamodel I would be able to add functionality and/or do help in fixing bugs. I will even become a benefactor if that will help. But this open source project is rather slow if you do not allow people to step in or guide them to where the project is going to.

So I am not sure if I am a sheep or a wolf with my plans. You decide on that. I need a store running end of september; and it will cost me a lot more if I have to rebuild my store if I want to keep close to the DNN store module later on (what I am opposed to so). Also a Dutch expression is "reinventing the wheel". So I would rather not do that.