Progress on Rule based matchmaker+alignemnt tool
This work details the advancements in the Rule-Based Matchmaker tool developed by CERTH/ITI, focusing on its integration with the CLOUD4All framework and GPII. The integration allows for online ontology browsing, downloading, and alignment, enabling users to find suitable solutions based on predefined criteria. Key features include an API for effective communication between the Matchmaker and ontology, functionality for instance retrieval, and support for various display enhancements. The tool facilitates user accessibility by matching specific user profiles with the most appropriate assistive technologies.
Progress on Rule based matchmaker+alignemnt tool
E N D
Presentation Transcript
Progress on Rule based matchmaker+alignemnt tool CERTH/ITI Votis Konstantinos
Achievements • Ontology on-line browsing and downloading • Ontology Alignment tool • API for the communication of the MatchMaker with the ontology • MatchMaker - OpenRules support • Integration of the CLOUD4All MatchMaker with the GPII framework
Ontology Alignment tool– Return matching ontology concepts –
Ontology Alignment tool– Set the value of default properties –
Ontology Alignment tool– The new solution has been added to the ontology –
API for the communication of the MatchMaker with the ontology • Functions for getting the instances of every class contained in the ontology • Functions for getting the instances that meet specific criteria • e.g., get all the screen readers running on Linux (in general) or get all the screen readers running on Linux Debian 6 • The implementation was based on the Apache Jena framework
API for the communication of the MatchMaker with the ontology (2) • Example: • //------- • //DEVICES • //------- • //get DTVDevices • ArrayList<Device> allInstances_DTVDevice = getInstances(DTVDevices_ID); • if(printDebugInfo) • { • for(int i=0; i<allInstances_DTVDevice.size(); i++) • System.out.println(allInstances_DTVDevice.get(i).toString()); • }
CLOUD4All MatchMaker – Integration with the GPII framework • The GPII framework is based on Javascript • The CLOUD4All rule-based MatchMaker is based on Java • The Google Web Toolkit (GWT) has been used to enable the use of the CLOUD4All MatchMaker through Javascript • Thus, the CLOUD4All rule-based MatchMaker can be integrated into the GPII framework
GPII - The “Flat” MatchMaker • Simplest possible algorithm • Index into the “skeleton solution input image” with all of the leaves derived from the user’s profile • Pick every solution for which there is an exact match
GPII MatchMaker - Some useful MatchMaker Primitives • Compute the Input Image of a solution: • Step 1: convert to leaf representation with matchMaker.computeLeavesFromSolution { "type": "gpii.integrationTesting.mockSettingsHandler", "capabilities": ["display.screenEnhancement"], "capabilitiesTransformations": { "mag-factor": "display.screenEnhancement.magnification", "show-cross-hairs": "display.screenEnhancement.showCrosshairs", … [ "display.screenEnhancement.magnification", "display.screenEnhancement.showCrosshairs", "display.screenEnhancement.tracking", "display.screenEnhancement" ];
GPII MatchMaker - Input Image Computation [ "display.screenEnhancement.magnification", "display.screenEnhancement.showCrosshairs", "display.screenEnhancement.tracking", "display.screenEnhancement" ]; • Step 2: Convert to “skeleton model” using matchMaker.pathsToSkeleton var magnifierSkeleton = { display: { screenEnhancement: { magnification: {}, showCrosshairs: {}, tracking: {} } } };
GPII MatchMaker User – solution matching var sammyProfile = { "display": { "screenEnhancement": { "fontSize": 24, "foregroundColor": "white", "backgroundColor": "black", "fontFace": { "fontName": ["Comic Sans"], "genericFontFace": "sans serif" }, "magnification": 2.0, "tracking": "mouse", "invertImages": true, "-provisional-showCrosshairs": true } } }; var magnifierSkeleton = { display: { screenEnhancement: { magnification: {}, showCrosshairs: {}, tracking: {} } } };
CLOUD4All rule-based MatchMaker within the GPII framework User Profile 1 Goal: If the user uses a screen reader, find the suitable screen reader according to the defined rules. User Profile 2 User Profile 3
Take into account the defined rules • If the user uses a screen reader • Get system’s time • Return the screen reader(s) that run(s) on the platform used in the current time