Add concept of notIsolated directives by simply distinguishing between directives that have new scopes, and directives whose new scopes are to be isolated. And personally, I might add that I believe the former (directives having new scopes, or a directive whose definition declares notIsolated to be true) to be the ideal default behavior, which would result in several side-benefits: (1) improve the readability of the Angular source (by not having to distinguish between a newIsolateScopeDirective var and a nearly useless newScopeDirective var) and (2) alleviating the conceptual burden of beginners to Angular who would really like to define a directive that has attributes that directly correspond to its (new) scope without being completely set apart from its prototypal parentage (or isolated), and finally (3) allow transcluded directives to transclude into any number of other transcluded directives, any number of which may or may not have attributes automatically attributed to their respective new scopes.