xml-dev - What is the relationship of product to enterprise? (RE: Joel on XML)

["Bullard, Claude L (Len)" <clbullar@ingr.com>]

Don is right:  people want the music and Napster is a means to 
get it.  What will .net do for them?  Are there alternatives?

Joel's article only serves to ask the question, is this 
real, and that is better answered by reading 
the MS technical documents.  The question to 
ask of MS's competitors is what they have to 
offer to meet the same requirements. MS is getting ready 
to ship code so serious people begin to 
ask how that will be applied.

The useful topic is how does one configure a 
system based on discovery instead of search?  
What is the difference?  What requirements 
does .net meet?

For starters, one has to look at one's  
business in terms of one's own products as 
exposed by these services.  This isn't simple 
topic or key-based discovery.  Contract-negotiation 
is a protocol unto itself.  What do you want to 
buy or offer?  How do you name that?  How do 
you differentiate your product/service from 
your competitors?  Do you really want to 
use intermediaries or do you want to 
work directly with the contractors?  Once a 
contract to negotiate is established, what 
rules do you use to evaluate services?  
Once you contract for product-based services, 
how do you manage the work, schedule the work, 
know when the work is done or not done, at 
what level of acceptable quality?  How do 
you rollback or rollforward scheduled 
events?  How do you decide when a phase closes 
versus a singular process?  

There is a lot to think about. 

.net uses discovery documents containing 
sets of typed links to expose a set of services.  These 
services can be simple RPC-like method all the 
way up to hierarchically nested business 
processes.  The CITIS guys should recognize this 
design.  Enterprises expose a product/process/organization  
view.  

Len Bullard

http://fly.hiwaay.net/~cbullard/lensongs.ram

Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h


-----Original Message-----
From: Box, Don [mailto:dbox@develop.com]

Perhaps that's because there are way more people interested in swapping MP3s
than in administering UserLand stuff. If/when compelling
services/applications are served up via SOAP, then SOAP traffic will be
fairly ubiquitous.