W3C home > Mailing lists > Public > www-html@w3.org > November 2003

Re: <link> vs. <script> for external scripts

From: Lachlan Hunt <lhunt07@postoffice.csu.edu.au>
Date: Wed, 19 Nov 2003 22:47:13 +1100
Message-ID: <3FBB5841.1090107@postoffice.csu.edu.au>
To: W3C HTML List <www-html@w3.org>

> While looking at the script and noscript elements, I noticed some 
> other problems with them.  The current draft (2003-05-06) states that:
>
> "When this module is used, the script and noscript elements are added 
> to the Block and Inline content sets of the Block and Inline Text 
> Modules..."
>  Also, the content model for noscript is: (Heading | List | Block)+
>
> Since <noscript> is added to the Inline content model, then it makes 
> the following valid:
> <span>some text <script 
> language="text/javascript">document.write("something");<noscript><h>Heading</h></noscript> 
> more text</span>
>  Is there a way to specify that when script and noscript are used 
> within Inline elements, the content model is only (Inline)+, but when 
> used within Block elements, the content model is (Heading | List | 
> Block)+ using Schemas?  I know it can't be done with DTDs. 


  Actually, what I should have asked previously is: Is there anyway, 
using an XML Schema, to specify that the content model is to be 
inherited from its parent element?.
  ie. No matter where <script> and <noscript> elements occur, we don't 
want elements inside <noscript> that would not normally be allowed to 
occur within the parent element.

CYA
...Lachy
Received on Wednesday, 19 November 2003 06:47:14 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:40:10 UTC