[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: is that a fork in the road?

• From: Michael Fitzgerald <mike@w...>
• To: Mike.Champion@S..., xml-dev <xml-dev@l...>
• Date: Fri, 02 Mar 2001 18:01:14 -0800

Nicely said.

When a small contingent decides for of a larger contingent, the larger
contingent does not readily accept the decision, esp. when delivered
condescendingly. A Bloody Sunday (Jan. 9, 1905) eventually yields a
Bolshevik revolution which eventually yields a Perestroika which eventually
yields a...

Buy-in is very important. Grassroots efforts seem to get buy-in easier than
top-down efforts, but everyone knows that, right? Right?

Mike

-----Original Message-----
From: Mike.Champion@S...
[mailto:Mike.Champion@S...]
Sent: Friday, March 02, 2001 3:18 PM
To: xml-dev@l...
Subject: RE: is that a fork in the road?

> -----Original Message-----
> From: Bullard, Claude L (Len) [mailto:clbullar@i...]
> Sent: Friday, March 02, 2001 5:25 PM
> To: Simon St.Laurent; xml-dev@l...
> Subject: RE: is that a fork in the road?
>
>
>
> So I am really missing your point.  Change seems
> inevitable.  Will it be ad hoc or planned?

I'm trying to think of successful examples of "planned" change.  I can think
of all sorts of plans that went nowhere commercially viable and were blown
away by "ad hoc" innovations ... X/Open, OSI Networking, Ada, DSSSL/HyTime
... the Soviet economy.  Someone please offer counter-examples to undermine
the hypothesis that "planned change" mainly tidies up ad hoc innovation,
then gets over-ambitious, bloats up, and ultimately rots.

• References:
  • RE: is that a fork in the road?
    • From: Mike.Champion@S...

• Prev by Date: Re: Coordination of <script> between SVG, XSLT 1.1 and HTML 4.01
• Next by Date: Re: Coordination of <script> between SVG, XSLT 1.1 and HTML 4.01
• Previous by thread: RE: is that a fork in the road?
• Next by thread: RE: is that a fork in the road?
• Index(es):
  • Date
  • Thread