From Event to Action: Accelerate Your Decision Making with Real-Time Automation
Â
A Semantic Wiki Based Light-Weight Web Application Model
1. A Semantic Wiki Based Light-Weight Web Application Model Jie Bao, Li Ding, Rui Huang, Paul R. Smart, Dave Brains, and Gareth Jones Presenter: Zhenning Shangguan Dec. 07, 2009
2.
3.
4. Web App Models Server Side Usersâ Control Web Server Database/Files Web Browser Conventional Model HTML+CSS Server Side Usersâ Control Web Browser Ajax Engine Web/Data Server Database/Files AJAX Model HTML/XML data HTML+CSS Server Side Wiki Engine Usersâ Control Web Browser Wiki Func. Wiki-based Model Web Server Database/Files Wiki UI HTML+CSS
5. Semantic Wiki Semantic Wiki Multi-user content creation and editing Browser-based, cross-platform easy to use Supports semantic annotations for automated processing and inference
6.
7. Semantic MediaWiki SMW: What you edit (Modeling Script) what you see To author knowledge typed link (property)
10. SemWiki-based Model Server Side SemWiki Engine Usersâ Control Web Browser SemWiki Data Wiki Func. SemWiki-based Model Web Server Database/Files Wiki UI HTML+CSS Structured data from SemWiki annotations Parser functions to process the structured data Wiki scripts to build application interface Both structured data and wiki scripts are accessible!
11.
12.
13.
14. Case Study RPI Map http://map.rpi.edu CNL Wiki http://tw.rpi.edu/proj/cnl
15.
16.
17.
18.
19.
20. Schema definition in DB-based applications Template defines the data structure for each class in RPI Map
21.
22. SMW-mOWL Class(Rabbit partial intersectionOf(animal restriction(eat someValuesFrom(FreshVegetable))) OWL: âRabbit eats some fresh vegetableâ Wiki templates to define axiom/annotation information. Form-based editing interface associated with templates
23. OWL Class Templates Similarly, we have templates for properties and individuals
24.
25. With little efforts, we can generate a map of todayâs events based on the previous query
User-contributed structured contents: limited ways for users to annotate web pages and publish their annotations as structured data, which can be shared and used in various ways. [tags, web forms only provide limited ways to annotate a page]. Access paradigm to those structured contents: users have to follow fixed interaction paradigm hard-coded in the web application. But with structured data, users actually can do more: avoid unnecessary overhead in NLP; and leverage services using the preserved semantics (e.g., semantic search) These limitations are rooted from the application models behind these web apps.
The missing part in the conventional models: no control over the underlying data and programming logic of the app prohibits users from building customizable applications â only server side developers or administrators can do that. Wiki-based model improves a bit by enabling users to directly do some simple manipulation and computation on the data. UI can be generated from user contributed templates Parser functions support simple computational tasks However, the wiki-based model only enables users to establish links between wiki articles and layout wiki pages. Typically, we cannot answer questions like âall Euro countries that have female government leadersâ. To answer it, we need embedded knowledge in wiki pages.
Lots of efforts use semantic technologies to address these limitations, notably Semantic Wikis. The SemanticWiki-based effort takes advantage of the fact that wiki-based model already enables collaborative authoring of scripts. Based on that, it adds functionalities to make semantic annotations and parser functions to process them. As you will see later, it will promote a new app model in which web apps are developed. But first, I just want to show a few slides introducing the basics of Semantic Wikis.
The model is not limited to wiki-based implementations, as more web 2.0 applications provide semantic extensions (Drupal), this model can also be used in other platforms
Thus supporting * Social structured knowledge construction * Social programming
CRUD = create, read, update, delete
[TODO] link does not work.
Wiki scripts: table, picture, tree, etc Javascirpt: wikicafe.metacafe.com, metavid.org
Location-based information: information (e.g., events, people, phone, etc.) based on their locations
[TODO] need discussion
not supporting all owl features, but almost all commonly used features are covered by the meta-model (e.g., partial vs. complete at the same time)
isDefintion: partial and complete 2) support automatic owl file importing 3) semantic forms facilitate content editing, minimal manual editing of scripts needed