Sections and content of the components specification

[espinr]

For those that are not following the discussions, this work doesn't want to replace the Web Component mechanisms. Instead, it aims to collect and inform about the common features of the different MiniApp implementations.

I've drafted a first proposal with the outline of the document ant the sections that can have the document (#5), but it's just an early suggestion.

1. MiniApp Pages and Components (intro to explain relation, custom components, the difference with Custom Components, etc.)
2. Markup and templating (can we find a common pattern?)
3. MiniApp Interface (properties and methods)
4. Component Declaration and Reuse
5. Component Events (Binding, Listeners, Types)
6. Scripting Resources (ECMAScript support)
7. Stylesheets (CSS profile, non-standard properties)
8. Component Lifecycle (if it differs from the MiniApp Lifecycle spec)
9. MiniApp Elements (or vendors' built-in components)

Feel free to comment here on the overall structure of the document, also the parts we should (or should not) include, and what is the content for each section.

[EisenbergEffect]

As long as this is about collecting information, I think this is fine. There's already active work on a number of these areas happening in the Web Components CG. This information could be used as input into those standards. I want to be very clear that we don't want two component models or two template languages, or anything of that sort though.