Re: Optional features considered harmful

>lightweight and easy to adopt?  At the same time, James is correct that it 
>is unreasonable and wrong to expect render-mostly network browsers to use 
>the SGML transclude-and-parse semantics.  Is there an option-free way to
>reconcile our goals?

Assuming that we do not have asynchronous nodes, can't the 
transclude-parse model be replaced by parser-transclude-parse? 
Validation would complicate it somewhat, but not overly much.