WP3 – Requirements from the Recommendation System Rafael González Cabero (UPM) Oxford, 07/2/2011

Embed Size (px)

DESCRIPTION

3 Research Object Definition WP3 – Requirements from the Recommendation System »RO are semantically rich aggregations of resources that bring together data, methods and people in scientific investigations

Citation preview

WP3 Requirements from the Recommendation System Rafael Gonzlez Cabero (UPM) Oxford, 07/2/2011 2 Objective: 2nd WF4Ever scientific and technological challenge WP3 Requirements from the Recommendation System Wf4Ever will archive, classify, and index RO in scalable repositories providing advanced access and recommendation capabilities will provide means to search through collections of RO will support community-based recommendations by means of advanced collaborative filtering techniques, will adhere to the linked data principles for making the data available within and outside the Wf4Ever scientific communities 3 Research Object Definition WP3 Requirements from the Recommendation System RO are semantically rich aggregations of resources that bring together data, methods and people in scientific investigations 4 Recommendation System WP3 Requirements from the Recommendation System RO UserUser Linked Data Infrastructure UserUser UserUser S P S P S P S P RecommendersCombiners + Filters A A A A A A R P R P R P 5 Used Standards(and thechnologies) Standards (and recommendations): The usual suspects RDF(S) OWL (or OWL 2?) SPARQL 1.1 Technologies Plain boring Java Scala+Akka Scala programs run on the Java VM Scala programs can use Java classes Drools(probably) WP3 Requirements from the Recommendation System 6 Mechanisms for Integration WP3 Requirements from the Recommendation System Shared Models Shared ontology for representing RO and users (myExperiment ontology as an starting point perfect for me) Shared ontology for representing Provenance (Provenance Vocabulary Core Ontology Specification as an starting point perfect for me) A triplestore (complete and updated) SPARQL 1.1 (we will make updates) Named graphs (probably) A notification service for relevant operations (asynchronous WS-based API better) Create/Update/Delete RO Create/Update/Delete User