Li Ding/Calendar "Li Ding Blog" 2008-4-17 - Event 1

From Tetherless World Wiki

Contents 1 Policy in Semantic Wiki 2 Highlights 3 Details 3.1 semantic wiki 3.2 policy issues in (semantic) wiki

Policy in Semantic Wiki

Part of: Li Ding Blog
Date: April 17, 2008
Location: Troy, NY
Participant(s): Li Ding

Highlights

• collaborative editing in wiki need better policy control
• most notions in TAMI can be easily mapped to semantic wiki, and semantic wiki serves as a good prototype platform
• if we know the SORN of each user, depending on the users in the editing history, we can determine who in the future can edit a page

Details

semantic wiki

It has the following

• wiki page (which can be further categorized to document, user, group, and etc.)
• editing history;
• semantic annotation and query

these concept can be mapped to TAMI

• document (or its fragment) wiki page-> data item/record, e.g. PNR, diagnose record, phone call log
  • e.g. http://tw.rpi.edu/internal/wiki/index.php/Main_Page

• user wiki page -> e.g. US marshal, policy officer
  • e.g. http://tw.rpi.edu/internal/wiki/index.php/User:Li

• group wiki page --> e.g. hospital database
  • e.g. http://tw.rpi.edu/internal/wiki/index.php/Special:Listusers
  • note: this can be done by creating a wiki page for the group, e.g. http://tw.rpi.edu/internal/wiki/index.php/Tetherless_World_Constellation

• editing history on document wiki page --> how users(identified by user wiki page) access, transfer and modify information
  • e.g. http://tw.rpi.edu/internal/wiki/index.php?title=Main_Page&action=history
  • or there is a semantic one http://tw.rpi.edu/internal/wiki/index.php?title=Main_Page&action=semhis
  • the wiki page import (via tempalte) is another way for capture data transfer, e.g.http://tw.rpi.edu/internal/wiki/index.php?title=James_A._Hendler&action=edit

policy issues in (semantic) wiki

• current wiki has limited support on access control:
  • ( read/write privilege can only be authorized as group/individual level )
  • read/write privilege can be applied on wiki pages grouped by namespace

• one noticeable challenge
  • the move /re-direct feature of wiki may cause unexpected results (e.g. lost permanent URI, fail semantic query)
  • the content import feature is good, but the imported content may change

• here are some wanted access control scenarios
  • how to restrict a collaborator (say TBL) to write just one wiki page (say the collaborator info page), and he cannot change other pages.
  • what if I want to make a previously private project page accessible by public (without changing its permanent URL)
  • more...

• here are some wanted provenance based policy checking scenarios
  • check semantic wiki editing history for unexpected edit, (a non-tw member editing a page create by TW member )
  • classify significant/ minor edits, and raise warning when significant change has been done by non tw member
  • if we know the SORN of each user, depending on the users in the editing history, we can determine who in the future can edit a page.