- From: Champion, Mike <Mike.Champion@SoftwareAG-USA.com>
- Date: Mon, 2 Jun 2003 10:46:39 -0400
- To: www-ws-arch@w3.org
> -----Original Message----- > From: Anne Thomas Manes [mailto:anne@manes.net] > Sent: Monday, June 02, 2003 8:09 AM > To: Champion, Mike; www-ws-arch@w3.org > Subject: Re: Explanation / Defense of "+5" > > > I go back to tooling. We want to make sure that developers > have a choice of > tools for building Web services. Tools require a standard description > language (as well as a standard protocols). Hmm ... I'm torn on this. On one hand, you're right! On the other hand, tools can lock us in to sub-optimal architectural patterns (e.g., the Google SOAP API, which could be more RESTful like Google itself but got locked into an RPC paradigm because that's what the tools support). Likewise, tools that hide hideous complexity under the covers (e.g. the Windows APIs) can both prepetuate the complexity and solidify the dominance of the tool vendor's preferred infrastructure. On balance, I think that tooling is an important practical consideration for real-world people and organizations focused on short-term pragmatism (such as WS-I) but I'm not convinced its an important issue for the WSA. Other perspectives welcomed!
Received on Monday, 2 June 2003 10:46:40 UTC