Advertisement

The Price of Services

  • Justin O’Sullivan
  • David Edmond
  • Arthur H. M. ter Hofstede
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3826)

Abstract

If we accept that service providers and service users all operate with autonomy in some form of market place, then a necessary prerequisite for service discovery and engagement is the description of the non-functional properties of a service. Price acts as one of the key nonfunctional properties used in choosing candidate services. Conventional services describe prices using several approaches (e.g. fixed price, price ranges, proportional pricing, dynamic price mechanisms). Furthermore, there are associated concepts such as price matching, price granularity, taxes and reward schemes that might need to be taken into consideration. This paper offers a discussion of the non-functional property of price. By incorporating some information about price, service descriptions will move away from the narrow distributed computing view of web services, enabling greater reasoning with respect to service descriptions.

Keywords

Service Provider Service Requestor Service Discovery Service Description Cleaning Service 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

References

  1. 1.
    Berners-Lee, T., Fielding, R.T., Masinter, L.: Uniform Resource Identifiers (URI): Generic Syntax (1998), Available from http://www.ietf.org/rfc/rfc2396.txt (accessed on June 19, 2001)
  2. 2.
    O’Sullivan, J., Edmond, D., Hofstede, A.t.: What’s in a service?: Towards accurate description of non-functional service properties. Distributed and Parallel Databases Journal - Special Issue on E-Services 12, 117–133 (2002)zbMATHCrossRefGoogle Scholar
  3. 3.
    O’Sullivan, J., Edmond, D., Hofstede, A.H.t.: Formal description of non-functional service properties. Technical FIT-TR-2005-01, Queensland University of Technology, Brisbane (2005), Available from http://www.citi.qut.edu.au/about/research_pubs/technical/nofunctional.jsp (accessed on Febrauary 15, 2005)
  4. 4.
    O’Sullivan, J., Edmond, D., Hofstede, A.H.t.: Two main challenges in service description: Web service tunnel vision and Semantic myopia. In: W3C Workshop on Frameworks for Semantics in Web Services, Innsbruck, Austria (2005)Google Scholar
  5. 5.
    Chung, L.: Non-Functional Requirements for Information System Design. In: Andersen, R., Bubenkor, J.A., Sølvberg, A. (eds.) CAiSE 1991. LNCS, vol. 498, pp. 5–30. Springer, Heidelberg (1991)Google Scholar
  6. 6.
    OWL-S Coalition: OWL-S Web Service Ontology, Available from http://www.daml.org/services/owl-s/1.1/ (accessed on November 21, 2004)
  7. 7.
    Bruijn, J.d., Bussler, C., Fensel, D., Kifer, M., Kopecky, J., Lara, R., Oren, E., Polleres, A., Stollberg, M.: Web Services Modeling Ontology (WSMO) - Working Draft (November 21, 2004) Available from, http://www.wsmo.org/2004/d2/v1.1/20041121/ (accessed on November 22, 2004)

Copyright information

© Springer-Verlag Berlin Heidelberg 2005

Authors and Affiliations

  • Justin O’Sullivan
    • 1
  • David Edmond
    • 1
  • Arthur H. M. ter Hofstede
    • 1
  1. 1.Business Process Management Program, Faculty for Information TechnologyQueensland University of TechnologyBrisbaneAustralia

Personalised recommendations