1 / 15

WP 203 - Federating repositories of Solutions and Components

WP 203 - Federating repositories of Solutions and Components. WP 203 – Federating reposit. of solution and components . WP 203 – Federating repositories of solution and components . Activities started in May 2012 (till August 2015).

chibale
Download Presentation

WP 203 - Federating repositories of Solutions and Components

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WP 203 - Federating repositories of Solutions and Components

  2. WP 203 – Federating reposit. of solution and components • WP 203 – Federating repositories of solution and components Activities started in May 2012 (till August 2015) • To develop (the methods for maintaining)a single entry point for the retrieval of the information and data required to implement appropriate assistive solutions. • The creation of efficient mechanisms for search and retrieval of accessible services and applications that will be provided in the envisioned Cloud infrastructure • Integrate the information on assistive solutions into the GPII unified listing and marketplace. Objectives in the DoW

  3. Federatedrepositoryof Assistive solutionwithin the GPII vision A way for users to find all of the solutions that exist and to figure out which ones meet their needs.

  4. Federatedlistingof AT devices The Cloud4All FederatedRepositoryof avaliableAT solutionswillrepresentone of the sources of information for: • The GPIIUnified Listing – a comprehensive listing of free and commercial, open and proprietary source, assistive technologies and features in mainstream products • The GPII Marketplace - i.e. a marketplace for "purchasing" commercial and free Access solutions • The GPII “shopping aid” thathelps the user to find the most appropriate assistive solutions in the unified listing and marketplace • The semantic framework for contents and solutions ?/ The matchmaker: one source of information used by the Matchmaker to propose activation of installed AT as well as installation of Assistive technology not yet available locally (see use cases 11-12 D101.2)

  5. Where the WP 203 fits in the overall cloud4all process Propose the most appropriate solutions for the user (“pre-sale” matchmaking) Preference server Preference wizard Device charact. reporter Cloud4All Federated Repository of AT Propose activation of installed AT and install. of AT not available locally Matchmaker (fitter) Local Solutions reporter User listener Launch manager

  6. The starting point – the EASTIN network The startingpointfor the Solution Database is the EASTIN web portal

  7. FederatingDatabasesof AT The current EASTIN approach Query from the user I wantan on screen keyboard EASTIN User interface (eastin website) Retrieved product description EASTIN Searchengine Webservice Client Data in EASTIN format Provider 1 (e.g. SIVA) Provider 2 (e.g. HMI Basen) Provider 3 (e.g. DLF Data) Webservice Server Webservice Server Webservice Server … Product DB Product DB Product DB

  8. Product description in the EASTIN portal Basic information • Example Additional details (formatted text)

  9. Metadata extraction/enhancement Free text Human and machinereadable Humanreadable Metadata extraction according to solutions ontology (WP 201)

  10. WP 203 – Connection between EASTIN-Cloud4All and GPII Automatic generation of metadata for solution (A 202.1) ? Semantic Framework for Contents and Solutions ? Cloud4All FederatedRepositoryof AT GPII GPII Unified listing GPII Marketplace Cloud4All compliant product descriptions YES EASTIN 2.0 EASTIN are Metadata complete? Cloud4all Metadata extractor EASTIN search engine NO EASTIN Distributed DB of AT products other DB of AT Vendor Alert Email sent to vendor Tools for vendor entry of metadata (A202.4 – A202.1) Vendor

  11. Activities led by FDCGO • A 203.1: Approach and mechanism for federating solution repositories • Definition of a method to harmonize and efficiently retrieve data coming form distributed databases • A 203.2: Integration of the appropriate subsections of federated data with the GPII Marketplace • Develop and demonstrate the ability to extract relevant information from more general topic disability databases + • A 202.4 Toolbox for professional and vendor entry and maintenance of Metadata • Implement an application suite for the manual creation, maintenance and update of metadata, based on the developed semantics framework

  12. Challenges • Harmonize the content coming from different sources and avoid duplication of data in the federated repository (the same product could be stored in different DBs) • Maintenance/update of data (ICT products become obsolete very fast) => distributed-collaborative update, update by vendors • Maintenance/update of ontologies and metadata (e.g. when new technologies become available) => automatic generation of metadata • Evaluate/validate the quality of the information (is the information correct, complete and accurate) => responsibility of each distributed information source • Clearly mark (and credit) the source of information

  13. Whatiswhat • Cloud4all Federated Repository  : This is a federated repository of open source and commercial AT of many types, based on the (distributed) databases of AT  • The GPII Unified Listing : This is a federated repository of open source and commercial AT related to ICT access as well as access features in mainstream products • The GPII Marketplace :The GPII Marketplace is a place to buy some ICT access products (those that the developers would like to distribute this way). The GPII Marketplace has a "shopping aid" that will draw from Cloud4all work • The Cloud4all/GPII Solutions Database: In the Cloud4all/GPII architecture - there is reference to two different "Solutions databases”: • a database of solutions that are present at a particular device that a user is at.  This lists all the local solutions that are available to the user • a database of information about (ideally all) devices. This can be used by the matchmaker to determine what features are available for any device that a user might encounter. It allows the matchmaker to know what features are available if the device does not offer up any more information than just its name/make/model. (is this the Semantic Framework of Content and Solutions ?) • Fromwiki: http://wiki.gpii.net/index.php/Unified_Listing_and_MarketPlace

  14. Cloud4All FederatedRepositoryof AT Sem. Frame. of solutions ? “Realtime” Not in “Realtime” Pref. server Preference wizard GPII GPII Marketplace GPII Unified listing Shopping aid ? List of suggested solutions for the user Localsolution Reporter (?) ?

  15. Thankyouforyourattention

More Related