{'fraction_non_alphanumeric': 0.02262443438914027, 'fraction_numerical': 0.013574660633484163, 'mean_word_length': 5.6254681647940075, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Business Rules Enabled Semantic Service Discovery and Selection for B2B Integration

In service-oriented business applications, B2B integration happens when a service requester invokes services of one or more service providers. Typically, there are several candidate services with similar capabilities that can be chosen by a requester in order to serve his business needs. The selection of the service to be invoked may depend on different functional and non-functional properties. The nonfunctional properties usually address security, reliability, performance, and so forth. The functional properties address the business process interplay at the level of the technical Web service interface and the message choreography associated with it. At the technical integration level, the description of functional and non-functional service properties has been exhaustively addressed in the scientific literature in the past. The business level however, namely, the requester’s business need, the business meaning of an offered service, and the capability of a service provider to successfully perform the requested business transaction, has been rather ignored. This chapter describes a solution for service discovery and selection at the business level, that is, at the level of offered business capability of a service provider and the ability to serve a concrete requested business transaction. The proposed solution is based on semantic interpretation of offered service capabilities, contractual restrictions, business rules of the requestor specifying selection preferences, and the parameters of the run-time service request. The applicability of the proposed solution is demonstrated on a shipper-carrier integration scenario. DOI: 10.4018/978-1-60566-804-8.ch008