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

RE: What does SOAP really add?

• To: 'John Cowan' <jcowan@r...>
• Subject: RE: What does SOAP really add?
• From: "Bullard, Claude L (Len)" <clbullar@i...>
• Date: Tue, 23 Apr 2002 11:01:34 -0500
• Cc: xml-dev@l...

Good catch, John.  It seems that breakwaters protect a local ecosystem by forcing 
movement elsewhere.  Life is lively in the ecotones.

"We can affect the deposition or erosion of sand, but we can't stop the incessant pressure of the waves. "
 
So the only way out of this is a Web Barrier Resources Act that specifies which 
parts of the "web" get to have business on them and others that don't?  And someone 
buys part of the "web" to keep it natural?  The analogy is frightening.

It does seem that access is where the beach meets the ocean.  What is wrong with 
the web reaching only as far as WSDL (accessible and identifiable by URI), then 
everything behind it is private property?

len

From: John Cowan [mailto:jcowan@r...]

"Bullard, Claude L (Len)" scripsit:

> [S]ome may 
> want to consider if it will be better overall 
> to put up a breakwater before the beaches 
> erode into unusable rock ledges.  

A great analogy, brother; but it is precisely the creation of breakwaters
(and jetties and seawalls and other such things) that cause natural
beaches to erode.  The beaches are moving, as Pilkey's book says, and
efforts to stop them are in general quite literally counterproductive.

Here's a high-quality but accessible page on the subject:
http://www.virginiaplaces.org/barrier.html

• Prev by Date: RE: W3C Culture and Aims (Was: What does SOAP really ad
• Next by Date: Re: What does SOAP really add?
• Previous by thread: Re: What does SOAP really add?
• Next by thread: RE: What does SOAP really add?
• Index(es):
  • Date
  • Thread