Re: <NEWHTML>???

nir dagan (dagan@upf.es)
Fri, 6 Mar 98 0:40:53 MET


From: nir dagan <dagan@upf.es>
Message-Id: <199803052340.AAA14861@sahara.upf.es>
To: afabrikant@smtpgtwy.ausd.k12.ca.us
Date: Fri, 6 Mar 98 0:40:53 MET
Cc: www-html@w3.org
In-Reply-To: <s4feb9c0.065@smtpgtwy.ausd.k12.ca.us>; from "Alex Fabrikant" at Mar 05, 98 2:41 pm
Subject: Re: <NEWHTML>???

The NEWHTML proposal is more related I think to XML or the HTML-Math 
working group. The question there is how to embed
MathML (or other XML) in HTML documents.

I think that one proposed solution is to use a MATH element
that is similar to the NEWHTML element.

As for new features of HTML, complexity shouldn't run that high
and new elements are designed to be backward 
compatible. The HTML4.0 strict model is a super-HTML2.0 that 
kicks out the mess done by adding zillions of ill defined elements. 

There is the NOSCRIPT element for 
browsers that do not show scripts, and also mechanisms like OBJECT 
or IFRAME seem adequette for most cases.

Putting both new and old version in the same document 
(as NEWHTML and  NOSCRIPT do) reduces downloading time.
The user always will download data he doesn't get anyway!
That is an advantage of OBJECT, the old browsers don't download 
what they can't understand. (but new browsers may load everything)  

Best regards,
Nir Dagan.

> 
> With HTML advancing as fast as it is, a fundamental question comes to
> mind, for which no satisfactory answer as of yet exists. How will it possible
> to create an HTML document in HTML x.y (where x>4) so that any browser
> supporting a version of HTML that exists today will be given an alternative
> to any codes that are new in HTML x.y?
> 
> Here's my suggestion. Take a look at the following code:
> 
> <NEWHTML>
> <!--
> parameter="html"; version=6.1; end="--"
> [code that uses HTML 6.1 tags]
> --
> parameter="css"; version=3.0; end="END-OF-CSS-EXTENSION"
> [code that uses CSS 3.0]
> END-OF-CSS-EXTENSION
> -->
> <OLDVER>
> [code compliant with any version of HTML that will be created before the NEWHTML is implemented]
> </OLDVER>
> </NEWHTML>
> 
> This is just an idea. I'm sure there're better ways to organize the syntax,
> rename the tags, and so on. I just want to bring up for discussion the
> problem which definitely exists, and will grow over the years as HTML
> advances further.
> 
> --
> Alex Fabrikant
> afabrikant@ausd.k12.ca.us
> 
>  
> 
>