Note: Introduction needs to be revised
The matchmaker is a component of the Cloud4All architecture that will match the needs and preferences of a user with the current software and software settings the user is using to solve a specific task. The matchmaker is a cloud-based service. The matching process between the user needs and the user environment can be performed by several approaches: rule-based approaches, statistical approaches and hybrid approaches are appropriate. A process construction unit of the matchmaker decides which matching process will be executed. If more than one matching processes is necessary, the process construction unit defines the order and combination of the matching processes. The process execution unit of the matchmaker is called to execute the constructed matching process. Another component of the Matchmaker is the Transformer, which is responsible for several types of transformations. As defined by the architecture group of GPII the transformer is the final part of the matching process:
- Translating generic preferences into settings for specific devices or applications).
- translating settings for specific devices or applications into generic preferences;
- Translating settings from one application or device to another, for example from Mac OS to Microsoft Windows, without going through generic preferences.
The GPII architecture defines other components within a personalization framework. For instance, the Flow Manager is a central component that sends and receives information to and from the matchmaker. The lifecycleHandler (previously Launch Manager, Configuration Manager and Launch Handler), is responsible for controlling and keeping track of the lifecycles of the launched/configured AT. The personalization framework is under development. Definitions and components can be changed or renamed.
For the technical concept of matchmaking, please refer to deliverable D204.1: Profile Matching Technical Concept.
Matchmaking Working Pages
- Matchmaker Meetings.
- Matchmaker Division of Work.
- Matchmaking Algorithms (ID204.1, ongoing development)
- Thoughts for the June technical F2F meeting (PiratePad).
- Matchmaker Framework Architecture
Pages related to the first evaluation phase:
- Cloud4all Testing: Essential Registry Terms & Mapping between application-unique terms (Google Docs).
- Matchmaker code in GPII pilot branch on GitHub.
- Installation Instructions First Pilots.
- Cloud4all Integration Tests.
- Cloud4all Pilot Scenario Tests.
- Matchmaker Benchmarking Metrics.
Pages related to ontologies and semantic infrastructure:
- Scenario on service composition (WP204.5).
- Specification of Cloud Semantic Infrastructure (D201.1).
- Solutions and Content ontology.
- Rules Engines.
- Matchmaker Configuration Mechanisms.
- Profile Initialization Brainstorming.
- Matchmaker Feedback Loop & Personal Control Panel.
- Device Profile & Device Profile Brainstorming: TBD.
- Glossary (check whether everything from Device Profile is in the glossary; if yes, remove this page).
Need a general page about preference sets.
The following page presents results of A204.1 Compiling existing Strategies and Tools.
- Rule-Based Matchmaker:
- RESTful web-service of the Cloud4All rule-based matchmaker.
- Original repository for the Rule-Based Matchmaker: Node.js part of the Cloud4All rule-based matchmaker.
- Fork of the above.
- Older, archived version of the Rule-Based Matchmaker.
- Statistical Matchmaker:
This presentation: File:The MatchMaker Ecology.ppt delivered at ICCHP 2012, Linz, describes the role of matchmakers in the architecture as envisaged in 2012, presents two "baseline MatchMakers" and maps out some important problems to be addressed, including the relationship of different MatchMaker processes and requirements.