ne Services 10.3.2.1 Binding Service 10.3.2.2 Matching Services 10.3.2.3 Query Reformulation 10.3.3 PAM Deployment 10.3.3.1 PAM-M: Introducing Personalization in Mediators 10.3.3.2 PAM-A: Introducing Personalization in Applications Service Delivery Platforms 10.3.3.3 PAM-S: Providing Personalization as an Autonomous Service 10.4 Application: Context-Aware Recommender System 10.4.1 Why Is Context Important for Recommender Systems? 10.4.2 CARS Requirements 10.4.2.1 Knowledge Acquisition Processes 10.4.2.2 Personalized Recommendation 10.4.3 Context Discovery and Profile Contextualization 10.4.3.1 Context Discovery Service 10.4.3.2 Contextualization Service 10.4.4 Binding and Matching Services 10.4.4.1 Binding Service 10.4.4.2 Matching Services 10.4.5 Toward Service-Based CARS 10.4.5.1 Aggregating Neighbor Ratings 10.5 Conclusion References 10.1 Introduction Service delivery platform (SDP) refers to a set of components that provide service delivery architecture (such as service creation, session control, and protocols) for a type of service. In spite of some standardization effort (e.g., TeleManagement Forum (TM Forum)) and deployments (e.g., Teligent SDP, HP SDP 2.0), there is not yet a consensus for the definition of SDPs and components composing them. Indeed, some vendors use the term SDP for their application servers, whereas others include a whole portfolio of products and components they offer. However, since SDP aims at enhancing services provided to end users by sim- plifying their interactions and taking benefits from Customer Relationship Management's (CRM) experience to provide them with the most relevant contents and services, personalization is a key issue in such architectures. In our vision, personalization encompasses a set of techniques that make appli- cations sensitive to users' profiles and contexts. The user profile groups information that characterizes the user himself (e.g., preferences, interests, demographic data, etc.) while the context groups a set of features that describe the environment 