KEOD 2013 – 20 th September 2013 A Comprehensive Framework for Semantic Annotation of Web Content Manuel Fiorelli 1, Maria Teresa Pazienza 2, Armando Stellato 2 1 Department of Civil Engineering and Computer Science, 2 Department of Enterprise Engineering University of Rome, Tor Vergata, Italy

KEOD 2013 – 20 th September Outline Annotation in action The problem Our proposal Our choices Combined managed of ontologies and Web content Event-based behavioural model Convention over configuration End-user customizability Conclusions

KEOD 2013 – 20 th September Annotation in action Annotation is a pervasive activity depending on different assumptions about granularity, level of formality and the use, if any, of ontologies. Collaborative authoring of documents Free text notes by co-authors NLP tools Structured annotations with weak semantics Semantic Web Annotations with respect to formalized knowledge to make explicit the meaning of Web resources (even Web services)

KEOD 2013 – 20 th September The problem The ultimate annotation system is unlikely to appear: Even comprehensive annotation models (e.g. the draft produced by the Open Annotation W3C Community Group) may not cover all usage scenarios Divergent methodologies: automatic vs manual annotation Different applications: NLP, Web Annotation, …

KEOD 2013 – 20 th September The problem Design Choices Supported applications General Purpose Programming Language Full system Specification Don’t take the convexity too strictly :-D

KEOD 2013 – 20 th September Our proposal framework Design Choices Supported applications General Purpose Programming Language Full system Specification Low upfront commitment to specific design choices Progressive levels of customization/implementation

KEOD 2013 – 20 th September Our choices Narrowed Scope Applications dealing with combined management of ontologies and Web content. Behavioural Model Assignment of handlers to predetermined events. We call an assignment of semantically coherent handlers an annotation family Convention over Configuration To ease the development of common interaction patterns.

KEOD 2013 – 20 th September Combined management of ontologies and Web content Interaction with the domain model Interaction with the Web content cross realm interactions

KEOD 2013 – 20 th September Semantic Turkey

KEOD 2013 – 20 th September Semantic Turkey Architecture Three layered extensible architecture Presentation Layer An extension to one of Mozilla Applications User Interface based on XUL, XBL and Javascript technologies Not–only–presentation Extensible via Mozilla Ext. Mechanism Services Layer Enables communication between the client (Firefox browser extension) and the ontology persistence layer. HTTP based Services accessed through the Ajax paradigm OSGi Extensible Servicing System Persistence Layer Access to ontological knowledge. Based on dedicated ontology API, which can be implemented through use of different technologies.

KEOD 2013 – 20 th September Event-based behavioural model From UI gestures (e.g. drag&drop) to events. selectionOverResource fired when a selection from a Web page is dropped onto an ontological resource resourceOverContent fired upon gestures for the association of Web content with an ontological resource regardless of their occurrence in the text contentLoaded triggered when Web content is loaded, in order to execute presentation related activities, e.g. highlighting the annotated fragments Creation of annotations Presentation of annotations

KEOD 2013 – 20 th September Event-based behavioural model Handlers Families bookmarking open annotation (coarse grain) open annotation (fine grain) Events selectionOverResource resourceOverContent contentLoaded selectionOverResource resourceOverContent contentLoaded selectionOverResource resourceOverContent contentLoaded Multiple handlers for offering different choices to the user Events agnostic about the resource type (e.g. class vs individual), but handlers have pre- conditions that may filter incoming events on the basis of the target resource type

KEOD 2013 – 20 th September Convention over configuration Event-based model makes almost no prior assumption about the application or the interaction patterns Therefore, it is comprehensive However, to help the developer we provide a collection of predetermined handlers: Add an annotation to a resource Create a new instance Create a (sub-)concept Set a property value Which are defined up to a bunch of functions that must be implemented by the developer.

KEOD 2013 – 20 th September Convention over configuration Extension point

KEOD 2013 – 20 th September Convention over configuration Extension point

KEOD 2013 – 20 th September End-user customizability Most usage scenarios only concern with a subset of the possible interactions which a given family may offer. Select a subset of the handlers Strengthen the preconditions

KEOD 2013 – 20 th September Future Developments Extend the set of available conventions Evaluate our framework with respect to the coverage of the features of state-of-the-art annotation systems Is it possible to implement the identified features in our framework? How much effort does it require?