Terminology: Inline, Embedded & External.

W3C,

Please ignore this feedback if I'm unfairly adopting CSS parlance here
but isn't the term "inline" more commonly reserved for those cases in
which the construct under discussion is enclosed between the start and
end tag of the element, and specifically, to define some property of
that element? rather than being used, colloquially in my opinion, to
refer to "embedded" content, which I think in this case more aptly
conveys the crux of the concern and removes any ambiguity that might
arise.

http://www.w3.org/html/wg/drafts/html/master/introduction.html#introduc
tion

Errors that waste authoring time
       Some constructs are disallowed because historically they have
       been the cause of a lot of wasted authoring time, and by
       encouraging authors to avoid making them, authors can save time
       in future efforts.

       For example, a [1]script element's [2]src attribute causes the
       element's contents to be ignored. However, this isn't obvious,
       especially if the element's contents appear to be executable
       script — which can lead to authors spending a lot of time trying
       to debug the inline script without realizing that it is not
       executing. To reduce this problem, this specification makes it
       non-conforming to have executable script in a [3]script element
       when the [4]src attribute is present. This means that authors
       who are validating their documents are less likely to waste time
       with this kind of mistake.


Regards,

References

1. http://www.w3.org/html/wg/drafts/html/master/scripting-1.html#the-script-element
2. http://www.w3.org/html/wg/drafts/html/master/scripting-1.html#attr-script-src
3. http://www.w3.org/html/wg/drafts/html/master/scripting-1.html#the-script-element
4. http://www.w3.org/html/wg/drafts/html/master/scripting-1.html#attr-script-src


-- 
http://www.fastmail.fm - The professional email service