Crucial design goal decision time, folks:
Do we want to support, through mechanisms in HTTP, the ability to express
a bitmap of capabilities within specific content types (like HTML), or
not?
Supporting exact capabilities seems to make sense given the current modus
operandi of adding new functionality to the web by incremental advances -
a new feature is desired, a new HTML tag or attribute is defined. If
this is truely the evolutionary path developers want to see HTML and the
web in general take, then there's not much choice - we have to do it,
elegance be damned.
Or, we could decide that HTTP negotiation + simple, solid,
easily-implementable-to-conformance-levels MIME types provide a better
evolutionary path, and avoid the cache-busting swamp of capability
bitmaps.
Let's make a decision on this issue, or we'll be passing the buck until
the whole deal is irrelevant.
Awaiting the day when browsers aren't responsible for rendering, Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
[email protected] [email protected] http://www.[hyperreal,organic].com/