Re: [service-orientated-architecture] What is a Service? What is an Application?

[Ashley at Metamaxim]

I agree with Jan that substitutability is a key concept. Possibly it is a defining characteristic of service.   Unless anyone can suggest counter-examples, in the form of:    - A "service" that is not, at least in principle, capable of being substituted (i.e., provided by more than one supplier), - Something that is provided using IT on a substitutable basis from more than one supplier, but cannot be described as a "service".   Does anyone have thoughts on this?   Rgds Ashley ----- Original Message ----- From: Jan Algermissen To: service-orientated-architecture@yahoogroups.com Sent: Thursday, October 27, 2005 8:29 PM Subject: Re: [service-orientated-architecture] What is a Service? What is an Application? >> Some of the definitions I've come across for a Service are: IMHO, substitutability (of one service by another) is an important  concept. If you go to shoe order processor A and find it is down, you  can equally well turn to shoe order processor B, given you know they  are substitutable. A real world example is that you can use another Web search engine if  your favorite one is down, because you happen to know that they are  both Web search engines. HTH, Jan YAHOO! GROUPS LINKS  Visit your group "service-orientated-architecture" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.