Lists Home |
Date Index |
But ten years later, as the world finally understood what
they were told and began to realize that a web browser is a
technical cul de sac if used as the sole point of integration,
systems such as XAML with its extensibility perfectly reproduce
the HyTime inheritable architectures and the GUI language of
the US Navy MID. Had we stopped at HTML we would be dead. If
we refuse to enable XML inheritable architectures, we are dead.
To have a future, pioneers must secure it. Next time anyone
on the list wants to have a gratuitous go at the SGMLers and
HyTimers, keep in mind, they really were more advanced and
ultimately right. The were too far ahead of their time, but
securing a future means someone has to invent it from scratch.
Then the implementors and the carry-on heros who learned to
edit can trim out the fat that comes of starting from scratch.
"There is a foreground timing and a background timing."
From: Michael Champion [mailto:email@example.com]
> Suggestions for an ASN.2 that is a cut-down, basic, ASN.1 abound. But
> the problem is that for every feature you look at, there are real
> specicifications out there that use it!
> Also, please distinguish the ASN.1 notation from the encoding rules.
> This is a one to many mapping.
Please note that I am just playing with the SGML analogy here; I don't
pretend to know enough about ASN.1 to make a substantive contribution.
I would simply note that many of these good points about the pains that
a subset of the technology would cause the current users were made by
SGML advocates when XML was being debated. In retrospect, they seem to
be vastly outweighed by the benefits that the refactoring brought to
I'd also note that the slightly desperate tone of some of the early
posts in this thread remind me of SGML advocates in the '90s, who could
see the benefits that standardized markup could bring and couldn't
believe why the world didn't realize them. The world began to realize
once this once the core specs were simple enough for ordinary mortals
(and tool developers) to work with.