OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] SOAP and the Web

[ Lists Home | Date Index | Thread Index ]

That is why I am trying to establish which 
engineering features have the potential for 
creating path dependencies and what degree. 
Then the business decisions are clearer. To 
do that, one must compare the payoffs of each 
choice.  I have to discard Fielding's 
"unforeseen benefits" because while one 
can sell a car by telling the buyer it will 
get them laid, one doesn't write that into 
the contract.


-----Original Message-----
From: Simon St.Laurent [mailto:simonstl@simonstl.com]

On Wed, 2002-05-01 at 13:49, Bullard, Claude L (Len) wrote:
> The market could do as you suggest and flock to SOAP 
> based on ease.  It wouldn't be the first time.  But 
> is it the duty of the TAG to warranty an architecture 
> based on ease, or should they warranty only the architecture 
> designed with 'safety in mind' or whatever criteria are 
> chosen?  

I think we need to know whether this is an engineering discussion or a
business discussion to figure out which criteria are important.


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS