I think you're confusing the term "language" with "media type."
The html+/3 LANG tag is a hint at the writing system, for issues
like writing direction, glyph combination, and the like. It's not
really related to the issue of scripts in Safe-Tcl vs. Java.
I like the idea of scrapping <app> for <applet>, and scrapping
<applet> for <fig>. The media type of the resource idicated by the SRC
attribute of the FIG is not generally specified in the markup, any
more than the media type of a resource indicated by the HREF attribute
of an A tag. The media type is discovered during the information
retrieval.
So:
<a href="foo">who knows?</a> might point to a CGM graphic,
and
<fig src="foo">who knows?</fig> might point to a Java script.
Also I like the idea of using the #fragment identifier as the java
script parameters too. I agree that "Client side specializer" is a
better term. Someone mentioned the other day that:
<a href="foo.3d#vx=100;vy=200;d=300">our building</a>
might be a link to a 3d drawing of a building, and the vx, vy, d
parameters would set the viewpoint and disance.
Now... a point of order... this feels like a www-talk or www-html
discussion. Exactly what proposal are we discussing? Is someone
writing an internet draft? I have suggested a couple times that
somebody write a "forms and interactive applications" draft.
I nominate Paul Burchard as editor. If nothing else, somebody
here at the W3 Consortium will write it up eventually. But I'd
rather do it sooner than later.