:) 1. Marked Sections
:) -------------------
[.. desc deleted ..]
I think a single "level" is insufficient, since some may be able to
handle the "capability" of a graphic display but not "tables" but vice
versa. It seems to me you're after a list of items and the support is
an indication of which of these items is or is not in the client.
Perhaps it would be helpful if one can define the set of capabilities
and the basic requirements, as well as the "alternative" -- example,
"label in place of graphics as follows" so that either the server or the
client has a means of handling the "out condition"
:) 2. Processing instructions
:) ---------------------------
[.. desc deleted ..]
I agree this is ugly... but it may be because of the phrasing then the
intent?
:) 3. New HTML elements
:) ---------------------
[.. desc deleted ..]
This is much closer to what I would like to see happen.
But perhaps the *server* could negotiate and decide on some aspect of
*what* to send before that, that would definitely speed things up.
I would suggest some form of client-server negotiation prior to delivery
so that the client and server are doing some of the job and allowing the
best use of net and system.
:) 4. The CONCUR construct
:) ------------------------
[.. desc deleted ..]
I'd say: Keep away from CONCUR. I got this advice from quite a few
SGML experts (for real).
-- [Daneel Pang] | Eventually, everything will be there. [email protected] | Big is beautiful, big is accomodating. (65)770-3801 | I needed it yesterday.