W3C home > Mailing lists > Public > www-html@w3.org > January 2001

RE: Add Version Information to Script Element

From: Dave J Woolley <david.woolley@bts.co.uk>
Date: Thu, 4 Jan 2001 20:04:13 -0000
Message-ID: <81E4A2BC03CED111845100104B62AFB50102A362@stagecoach.bts.co.uk>
To: www-html@w3.org
> From:	Axel Dahmen [SMTP:a.dahmen@infozoom.de]
> Thanks, Robin,
> > MIME media type, such as:
> >
> > <script type="application/x-javascript;version=1.3">
	[DJW:]  Oops.  The HTML 4.01 specification is broken
	here in that it uses the term media-type and uses 
	RFC 2045 to define it.  Unfortunately, the definition
	in RFC 2045 only allows "application", not even
	"application/x-javascript", even though, at least the
	latter was clearly intended.

> Hence, I'd like to suggest to endorse that kind of construct in HTML to
> allow cleaner implementations of script-enabled browsers.
	[DJW:]  All that really takes is to change section 6.7 of
	the HTML 4.01 specification to permit (in RFC 2045 terms):
       type "/" subtype *(";" parameter) 
	[DJW:]  The difficult bit is convincing the browser writers
	that not only should they not rely on Language, but they should
	look at the parameters field in the type parameter - what is
	in it for them?

	[DJW:]  (The formal correlation of type and media-type is implied
	by this comment:
; Matching of media type and subtype ; is ALWAYS case-insensitive. 
	on the production rule for Content-Type headers, although the 
	narrative in RFC 2045 always treats media-type as not containing
	the subtype.)

--------------------------- DISCLAIMER ---------------------------------
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of BTS.
Received on Thursday, 4 January 2001 15:05:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:55 UTC