890 likes | 1.1k Views
Date. Social Semantic Desktop Reference Architecture Evaluation. People. Evaluation purpose (generic). To involve various stakeholders of the Social Semantic Desktop community in the critical assessment of the Social Semantic Desktop Blueprint
E N D
Date Social Semantic DesktopReference Architecture Evaluation People
Evaluation purpose (generic) • To involve various stakeholders of the Social Semantic Desktop community in the critical assessment of the Social Semantic Desktop Blueprint • Refine the scope functional boundaries of the Social Semantic Desktop Blueprint • To involve the stakeholders in the architectural design by bringing their experience and expertise
Evaluation process • Preparation • Stakeholders profile – Questionnaire A (10 min.) • Introduction (5 min.) • Motivation and Overview (2 min.) • The Social Semantic Desktop Blueprint (40 min.) • Analysis • Scenarios for the Social Semantic Desktop Blueprint (5 min.) • Interactive scenarios revision (20 min.) • Synthesis • Assessment – Questionnaire B(10 min.) • Final assessment – processing the evaluation data to formulate the evaluation results
Please fill-in Questionnaire A … http://www.surveymonkey.com/s.aspx?sm=Y7dGTHTbWa_2biudS_2fM8924g_3d_3d
The Social Semantic Desktop • Extension of the personal desktop … • … into a collaboration environment • Goals: • Improve personal information management • Improve cross-media and cross-application linking • Improve sharing and exchange across social and organizational relations.
Social Semantic Desktop Layers • Personal Information Management • Distributed Information Management • Social Networks and Community Services.
The NEPOMUK IP Project • FP6 Project IST • 17 Partners: • 8 research centres • 4 big industry players • 3 SMEs • Open source
The NEPOMUK IP Project (cont.) • Goals • Definition of the Social Semantic Desktop Blueprint • Standardization of ontologies and APIs • Development • Prototypes • The reference Social Semantic Desktop implementation
Evaluation purpose (technical aspect) • Social Semantic Desktop Blueprint • Personal information management -> Personal knowledge creation and organization • Data interoperability -> Cross-media and cross-application linking • (Distributed) Social collaboration -> Sharing, exchange and alignment of the personal knowledge in a distributed manner • Evaluation = Proof that the SSD Blueprint is able to handle all the possible scenarios arising in the space of these three dimensions
Overview • Social Semantic Desktop – Scenario • Social Semantic Desktop – Engineering cycle • Social Semantic Desktop Models • The Social Semantic Desktop Blueprint
Technical requirements (I) • Knowledge Articulation and Visualization • Semantic data editing and presentation • Standard Desktop Classification Structures • Standard set of vocabularies and ontologies (e.g. calendar, task management) • Mapping and Aligning Algorithms • Alignment of information from similar domains expressed with different schemas • Wrapping of Legacy Information • Standardized semantic representation of structured and unstructured data
Technical requirements (II) • Metadata Storage and Querying • Central place for storing and querying the information and the associated metadata • Linking of Data Items and Relational Metadata • Link of arbitrary information across different media types, file formats and applications • Social Aspects • Social relation building and knowledge sharing within social communities • Open Architecture • Clearly defined and published interfaces • Open for integration with external adopters
Models • Personal Information Model (PIM) • Vocabulary allowing individual persons to express their own mental models in a structured way • Different mental models can be integrated based on matching algorithms or on domain ontologies • Information Element Model (IEM) • Vocabulary for describing information elements which are commonly present on the semantic desktop • Annotation Model (AM) • Vocabulary, commonly required to annotate resources on the semantic desktop
NEPOMUK Models – PIMO • Requirements • a representation of abstract concepts: Love, Rome, Acme Inc. • a representation of concrete, addressable resources: "w3c homepage at www.w3.org" • a representation of documents: "the document at http://www.w3.org/" • multiple names for a thing: "Love", "Liebe“; "W3", "WWW" • same name for two different things: "Apache - helicopter", "Apache - software". • class-subclass relations: a subclass has all properties of the superclass + its own • class-instance relations • part-of relations: the city of Rome is part of Italy • related information: Spaghetti is related to Italy • data properties to describe details: Rome has a population of 2.8 mio • document-has-topic: the document "http://www.w3.org/2001/sw" is about the "Semantic Web" • a representation of time: the document was created in 2005. The project started on 1.1.2006
NEPOMUK Models • The NEPOMUK Information Element (NIE) • Set of ontologies • Vocabulary for describing information elements commonly present on the semantic desktop
NEPOMUK Models – NIE • NIE Core – NEPOMUK Information Element Core Ontology • NFO – NEPOMUK File Ontology • NCO – NEPOMUK Contact Ontology • NMO – NEPOMUK Message Ontology • NCAL – NEPOMUK Calendar Ontology • NEXIF – NEPOMUK EXIF Ontology • NID3 – NEPOMUK ID3 Ontology
NEPOMUK Models • The NEPOMUK Annotation Ontology (NAO) • Vocabulary that enables users to attach custom descriptions, identifiers, tags and ratings to resources on their desktop • Via other properties, the user is also able to make generic relationships between related resources explicit. • Relationships between resources that are too general to be included at the domain ontology level are also defined in the annotation ontology • Given the high-level status of this ontology, these properties can be used to link any related resources on the user's desktop, as well as provide custom human-readable textual annotations
NEPOMUK Models – NAO Basic Conventional tagging Specific
Social Services • Foundational layer for achieving social collaboration • Main functionality • Distributed information management • Communication • Security
Messaging service • Enables cross-desktop communication • Handles both service-to-service and human-to-human communication • Acts as message-carrier for the Notification service