Embed Size (px)
Citation preview
Semantic MediaWiki for strategic foresight creation
(C) WikiVote! 2012
Yury Katkov
• We use crowdsourcing to improve structured documents – laws, bills and legislative acts– reports and projects– standards
• Knowledge management• Strategic planning, social roadmapping and foresight
About the company
(C) WikiVote! 2012
• We use crowdsourcing to improve structured documents – laws, bills and legislative acts– reports and projects– standards
• Knowledge management• Strategic planning, social roadmapping and foresight
About the company
(C) WikiVote! 2012
SMWis here!
• About the company• WikiVote platform– principles– features– practices and tricks
• Use case: Rapid Foresight on a Foresight trip– foresights and roadmaps– specific aspects
• Results for the community• Development plans
Outline
(C) WikiVote! 2012
• About the company• WikiVote platform– principles– features– practices and tricks
• Use case: Rapid Foresight on a Foresight trip– foresights and roadmaps– specific aspects
• Results for the community• Development plans
Outline
(C) WikiVote! 2012
Wikivote platformPrinciples and features of the platform for social roadmapping and knowledge engineering
(C) WikiVote! 2012
1. Wiki website don’t have to be encyclopedia.2. Wiki has to be easy to learn and goal-oriented.3. Wiki is a social tool.4. Develop the potential of voting in a wiki.Design principles:5. Deploying of the new project must be fast.6. Common format for all the data.7. More wiki-level programming for flexibility.8. Be Open Source to be stronger.
Ideas behind the platform
(C) WikiVote! 2012
• Semantic Forms for all the pages– Make forms more dynamic– New form inputs– Escaping for security– New page handling
• Social Features:– Social Profiles with Forms+Semantic Signup– Karma (user ratings)– Viewing the users’ contribution
• Voting, a lot of voting• Visual diffs and comprehensible history line
Features of the platform
(C) WikiVote! 2012
• MediaWiki markup is awfully difficult• Markup is too powerfulGoal: user can edit the pages without knowing the markupSolution: • use Semantic Forms for every page on a wiki• WYSIWYG editor for everything inside the
textareas– past: FCKEditor– present: WikiEditor– future: VisualEditor
Markup
(C) WikiVote! 2012
Wiki can be easy
• Forms are vulnerable to user input• We need more forms inputs! • Forms can be more dynamic and powerful– going beyond show on select and values dependent
on
Forms
(C) WikiVote! 2012
values from querydynamic
possible
values escaping in Forms
two listboxes
input
spinner input
• Two listboxes– easy way to multiselecting: no Ctrl+Click– searching to add quicklier
FormsSFI inputs
(C) WikiVote! 2012
• Spinbox– well, just spinbox– help user to quickly understand that we need
only numeric value in this field
• More to come!
FormsSFI inputs
(C) WikiVote! 2012
• Problem: the form allows you to use any symbols, but some of them we don’t want user to put in:– }}, {{, {{{Smth}}}, etc– |, || , |- can broke the tables– [[Category:Smth]], [[Smth1::Smth2]]– {{#smth}}
• Solution: Semantic Forms Escaping extension– Prevent template broking– Prevent using of templates, semantic properties
and parser functions
Forms Security
(C) WikiVote! 2012
Handling new pages Clicling on a red link
(C) WikiVote! 2012
‘values from query’ for semantic forms• it works like ‘values from concept’ but you don’t
need to create a concept!
{{for template|Trend}}{{field|related events|values from query = [[Category:Event]][[belongs to::Foresight 1]]|input type=two listboxes}}• Especially useful when you use templates in
forms
Forms More dynamics in Forms
(C) WikiVote! 2012
• conditional possible values (substitute
feature): the forms that change on-the-fly
{{for template|Trend}}{{field|foresight|mandatory}}{{field|related events|values from query = [[Category:Event]][[belongs to::#1]]|substitute=Trend[Foresight]|input type=two listboxes}}
Forms More dynamics in Forms
(C) WikiVote! 2012
What can we do with structured data about the user:• Social network analysis• More data for the semantic history• Improved statistics• Improved search• Personalized UI• Turn wiki into FOAF-editor
Social Features Social Profiles
(C) WikiVote! 2012
Wiki is a social tool
Common
format for
all the data
(C) WikiVote! 2012
Social FeaturesTools to represent social profiles:
past
(C) WikiVote! 2012
Social FeaturesTools to represent social profiles:
new
Social FeaturesTools to represent social profiles
Past: Social Profile + SSPNow: SemForms + Semantic Signup
+ very flexible
+ no data duplication
+ out-of-the-box semanticness– all the data is totally open– no write access control
+ private fields
+ good access control
+ private chats
– not flexible– many things we don’t need– design issues– duplication of the data
(C) WikiVote! 2012
Social FeaturesTools to represent users’
contributions
Why voting? • Collective decision making• Collective expertise of objects• Indirect expertise of people• Kinds of votingKinds of voting:• Simple “agree/disagree”, “+1/-1”• Multi-criteria scales• Big questionnaries
Voting
(C) WikiVote! 2012
Develop the potential
of voting
Article Feedback
VotingFirst attempts
(C) WikiVote! 2012
Many evaluation criteria
Nice lookSemantic Article Feedback
Article Feedback: disadvantages:• One voting form for everything• Only one type of voting: stars (1–5 grades)• No access control for voting• Duplication of the data during semantification
VotingFirst attempts
(C) WikiVote! 2012
Article Feedback’s main direction now:
Oh common!!!
VotingFirst attempts. Disappointment.
(C) WikiVote! 2012
WikiVote Voting:• Questionnaries that are connected to a
category• Flexible appearance• Flexible logic and computations (easy to
change formulae):– computing average votes– computing users’ ratings
• Administrator’s UI• Queue processing of the complex calculations
VotingCurrent solution
(C) WikiVote! 2012
VotingWikiVote Voting: appearance
(C) WikiVote! 2012
VotingWikiVote Voting: appearance
(C) WikiVote! 2012
VotingWikiVote Voting: appearance
(C) WikiVote! 2012
VotingWikiVote Voting: appearance
(C) WikiVote! 2012
VotingWikiVote Voting: flexibility
(C) WikiVote! 2012
VotingWikiVote Voting: structure
(C) WikiVote! 2012
Voting group
Widget1 (checkboxes)
value 1 value 2 value 3
Widget2 (dropdown)
value 1 value 2
Category
WikiVote Voting + SMW? • Average votes as sorting criteria• Average votes as conditions in wiki-level
application logic: #if, #switch, Lua scripts• Easy export of votes for analysis• Average votes in result formats: – just print the votes– create new formats where sizes /posistions/
colors of elements are dependent on average votes
VotingCurrent solution. Semantification.
(C) WikiVote! 2012
Common
format for
all the data
Visual diff and history
(C) WikiVote! 2012
Deployment and wiki-coding
(C) WikiVote! 2012
Templated Forms &
Templates
Forms & Templates
Some cool features that people rarely use: • Page Schemas is a great tool to quicky create
the initial structure of the project• Templated forms for similar kinds of objects
Rules of a good style: • Avoid redundancy with templates• Implement logic of the project with wiki
programming: templates, queries (#ask, #show), parser functions (#if, #switch, #arraymap), Lua scripts
Deployment and wiki-coding
(C) WikiVote! 2012
• About the company• WikiVote platform– principles– features– practices and tricks
• Use case: Rapid Foresight on a Foresight trip– foresights and roadmaps– specific aspects
• Results for the community• Development plans
Outline
(C) WikiVote! 2012
• About the company• WikiVote platform– principles– features– practices and tricks
• Use case: Rapid Foresight on a Foresight trip– foresights and roadmaps– specific aspects
• Results for the community• Development plans
Outline
(C) WikiVote! 2012
Pilot project: Foresight TripUsing WikiVote platform in the intranet for roadmapping and future studies
(C) WikiVote! 2012
Foresight tripDescription of the event
(C) WikiVote! 2012
Foresight tripDescription of the event
(C) WikiVote! 2012
Foresight trip:• Aug 13-18 (six days)• Full-day brainstorming sessions• Participants:
– Business representatives (mostly CEO and CFOs)– Government representatives– Future studies researchers and methodologists– Analytics– Journalists
• Creating foresights with “Rapid Foresight” methodology
• Results: roadmaps that represent shared understading of the future of participants and their shared plans
Methodology
(C) WikiVote! 2012
Rapid Foresight is a brainstorming methodology for roadmaps creation. Goal: agreement and shared understanding of the future of the certain field / industry / sector / regionSpecifics: • Managerial rather than analytical: addresses
management of the future, not only future studies.
• Very fast: one to three working sessions, 2-3 days each
In a nutshell:Participants use paper cards representing objects and put them on a timeline discussing the content, position and relationships between the objects.Source: Rapid Foresight, see http://www.slideshare.net/teplok/rapid-foresight-eng-v-feb2012
Rapid Foresight methodology What’s a roadmap?
(C) WikiVote! 2012
Rapid Foresight methodology What’s a roadmap?
(C) WikiVote! 2012
Rapid Foresight methodology What’s a roadmap?
(C) WikiVote! 2012
Rapid Foresight methodology What’s a roadmap?
(C) WikiVote! 2012
(C) WikiVote! 2012
Rapid Foresight methodology What’s a roadmap?
(C) WikiVote! 2012
Roadmap consists of different kinds of objects:• Prolonged entities
Trend: tendency in the future, observable process
Format: how people will do certain things
Technology that will strongly affect the field• Momentary entities
Event that represents the climax of a trend
Law that will strongly affect the field
Menace: something that can endanger other
entitiesThese objects can be related to each other and every object belongs to trend.
Rapid Foresight methodology Anatomy of a roadmap : objects
(C) WikiVote! 2012
Roadmap consists of different kinds of objects:• Prolonged entities
Trend: tendency in the future, observable process
Format: how people will do certain things
Technology that will strongly affect the field• Momentary entities
Event that represents the climax of a trend
Law that will strongly affect the field
Menace: something that can endanger other
entitiesThese objects can be related to each other and every object belongs to trend.
Rapid Foresight methodology Anatomy of a roadmap:
relations/properties
(C) WikiVote! 2012
Roadmap consists of different kinds of objects:• Prolonged entities
Trend: tendency in the future, observable process
Format: how people will do certain things
Technology that will strongly affect the field• Momentary entities
Event that represents the climax of a trend
Law that will strongly affect the field
Menace: something that can endanger other
entitiesThese objects can be related to each other and every object belongs to trend.
Rapid Foresight methodology Anatomy of a roadmap:
relations/properties
(C) WikiVote! 2012
Roadmap consists of different kinds of objects:• Prolonged entities
Trend: tendency in the future, observable process
Format: how people will do certain things
Technology that will strongly affect the field• Momentary entities
Event that represents the climax of a trend
Law that will strongly affect the field
Menace: something that can endanger other
entitiesThese objects can be related to each other and every object belongs to trend.
Rapid Foresight methodology Anatomy of a roadmap:
relations/properties
(C) WikiVote! 2012
Roadmap consists of different kinds of objects:• Prolonged entities
Trend: tendency in the future, observable process
Format: how people will do certain things
Technology that will strongly affect the field• Momentary entities
Event that represents the climax of a trend
Law that will strongly affect the field
Menace: something that can endanger other
entitiesThese objects can be related to each other and every object belongs to trend.
Rapid Foresight methodology Anatomy of a roadmap:
relations/properties
Our mission in the project
(C) WikiVote! 2012
During the brainstorming the group: + can think creatively– can’t think very deeply – can’t see the hidden relationships between the objectsWhere wiki-technology can help:• Collaboration• Revision controlWhere SMW can help:• Representation of the relations between the
objects• Tracking those relations• Discovering new relations with reasoning• Instantly display the results
What we have done
(C) WikiVote! 2012
• Analyzed the problem domain• Defined the schemas• Replaced the redundacy with reuse• Enriched the templates with queries
and logic• Createe the aggregation pages• Imported all the users from the list of
trip participants• Imported all the foresight sessons via
bot
{{PAGENAME}} can
make miracles
