60 likes | 189 Vues
WP3 – Requirements from the Recommendation System Rafael González Cabero (UPM) Oxford, 07/2/2011. Objective : 2nd WF4Ever scientific and technological challenge. WP3 – Requirements from the Recommendation System. Wf4Ever will archive, classify, and index RO in scalable repositories
E N D
WP3 – Requirements from the Recommendation System Rafael González Cabero (UPM) Oxford, 07/2/2011
Objective: 2nd WF4Everscientific 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
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
RecommendationSystem WP3 – Requirements from the Recommendation System Recommenders Combiners + Filters A A RO P User S A A RO … … P P User A A RO S R P P Linked Data Infrastructure P P S R S R User
UsedStandards(andthechnologies) WP3 – Requirements from the Recommendation System • 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)
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