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

RE: Web Design Principles (was Re: Generality ofHT

• To: 'Paul Prescod' <paul@p...>, xml-dev@l...
• Subject: RE: Web Design Principles (was Re: Generality ofHTTP)
• From: "Bullard, Claude L (Len)" <clbullar@i...>
• Date: Tue, 29 Jan 2002 09:00:26 -0600

Which is why there are "parts and assemblies", not 
"The Web".

In the politics of persuasion and creating consensus, 
the terms that associate large numbers of not-very
powerful individuals can easily serve a handful of 
very powerful entities.  So can systems that force 
one to rely on one vendor to get predictable results. 

If you want freedom to innovate, you have to design it 
into the specification.

Specs for *standard components* that can be aggregated 
into mission specific systems are what made object-oriented 
programming attractive.  The HTML browser has almost 
single handedly turned that on its head.  That is why 
some people fought the trend long ago.  The One Ring 
to Rule Them All is the notion that the web browser 
is the centerpiece technology of the Internet.  It isn't. 
It is of THE WEB.   HTML made the domination of the 
Internet software market by one or two large players 
inevitable.

len

-----Original Message-----
From: Paul Prescod [mailto:paul@p...]

The big guy will dictate to the little guy but if there are true
standards, not pseudo-standards, then the little guy will be able to buy
off the shelf software that conforms to the big-guy's wishes, rather
than making custom software to the big guy's spec.

• Prev by Date: Re: Web Design Principles (was Re: Generality ofHTTP)
• Next by Date: RE: Generality of HTTP
• Previous by thread: RE: Re: AF and namespaces, once again (was Re: [xml-dev ] There is a m eaning, but it's not in the data alone)
• Next by thread: PUBLIC id in notations
• Index(es):
  • Date
  • Thread