SMWCon Fall2013: Wikidata - an experience report

23
FeatureMatrix Wikidata vs. SMW An experience report

description

Markus Glaser and Robert Vogel auf der SMWCon Fall 13: This talk covers the experience of Hallo Welt! developers and decision makers, gathered in a real world project: Creating a Software Feature Matrix for the BlueForge website. We want to explain the idea behind the project, share the evaluation process and report about pitfalls and problems. http://semantic-mediawiki.org/wiki/SMWCon_Fall_2013/BlueForge_Feature_Matrix:_WikiData_-_An_experience_report Here the original talk as video on youtube: http://www.youtube.com/watch?v=LzRItXvzYTM

Transcript of SMWCon Fall2013: Wikidata - an experience report

Page 1: SMWCon Fall2013: Wikidata - an experience report

FeatureMatrix Wikidata vs. SMW – An experience report

Page 2: SMWCon Fall2013: Wikidata - an experience report

FeatureMatrix Wikidata vs. SMW – An experience report

Wikidata – An experience report

Page 3: SMWCon Fall2013: Wikidata - an experience report

FeatureMatrix Wikidata vs. SMW – An experience report

Wikidata – An experience report

Wikidata – An experiment report

Page 4: SMWCon Fall2013: Wikidata - an experience report

• What is BlueForge? What is a Software Feature Matrix?

• Requirements

• Proposed data model

• Showcase

• Implementation experience

• Wrap-up

experience Get to know what we know

1 2 3 4 5 6

Page 5: SMWCon Fall2013: Wikidata - an experience report

• Software directory, focus on

business software

• Target audience

• User/enthusiast

• Decision makers

• Vendors

• Consultants

• Basis for making informed decisions

What is BlueForge? Mapping Software for Professionals

1 2 3 4 5 6

Page 6: SMWCon Fall2013: Wikidata - an experience report

What is a Feature Matrix? Comparing Software Products

• Tool to compare two

or more software

products

• 2-d matrix of

available /

documented features

• Quick visual overview

1 2 3 4 5 6

Page 7: SMWCon Fall2013: Wikidata - an experience report

What tool is best? Requirements

Specifics of

software features

• there are variants and

forks (e.g. "free" vs.

"professional version")

• there are versions with

new features or different

implementations of the

same feature

• features are not binary,

they differ in quality

Feature

comparison

• There are groups /

categories of software

(Schema)

• Features can be added /

evaluated within the wiki

/ wikidata via UI (API)

State of knowledge

Claims (Wikidata) vs.

propositions (SMW)

The vendor says this

feature is well

implemented

1 2 3 4 5 6

Page 8: SMWCon Fall2013: Wikidata - an experience report

Arguments for Wikidata:

• Propositions can be qualified

• Interaction is API-based

• There is already a UI for entering data

• ...

Wikidata Decision was made for the Wikimedia tool

1 2 3 4 5 6

Page 9: SMWCon Fall2013: Wikidata - an experience report

… and we were curious

Page 10: SMWCon Fall2013: Wikidata - an experience report

• An article represents a piece of software, all versions, all

variants

• A category represents a group of software. A piece of

software can be in multiple categories

Proposed data model Unstructured data within Client (BlueForge) Wiki

1 2 3 4 5 6

i.e. „Joomla“

i.e. „Category: Content Management“

Page 11: SMWCon Fall2013: Wikidata - an experience report

1 2 3 4 5 6

i.e. "Joomla!" i.e. "Category:Content

Management"

Page 12: SMWCon Fall2013: Wikidata - an experience report

Proposed Data Model Structured data within Repo Wikibase

A piece of software (= article on

client)

item

A feature

• features have qualifiers

(since version, user rating, ...)

• features have sources (vendor, user)

• features have (custom) data types

Groups (= category on client)

property

item

Features of a group property of property

(aka schema)

Naming is consistent between client and repo link is by convention

=

=

= =

1 2 3 4 5 6

Page 13: SMWCon Fall2013: Wikidata - an experience report

showcase

1 2 3 4 5 6

Page 14: SMWCon Fall2013: Wikidata - an experience report

showcase There are two systems

stage.blueforge.biz

(MediaWiki + BlueSpice,

role "client")

http://stage.blueforge.biz/wiki/

Special:Version

stage-data.blueforge.biz

(MediaWiki + Wikibase,

role "repo")

http://data-stage.blueforge.biz/index.php/

Special:Version

"stage-data" is currently used as

a backend, user interaction only

on "stage"

1 2 3 4 5 6

Page 15: SMWCon Fall2013: Wikidata - an experience report

Implementation experience

Data model can be implemented in Wikidata. Philosopy seems to overlap

Schema via UI / tool support

Officially not ready for 3rd party use: we are very early adopters :)

Architecture seems to be flexible enough

1 2 3 4 5 6

Page 16: SMWCon Fall2013: Wikidata - an experience report

Implementation experience

Hard to set up, we tried using vagrant but ended with a custom/hacked

setup.

Value autocomplete seems to be resource intensive without additional

data stores

Custom value types were hard to implement

PHP dependency: do not use <= 5.3.2:Caution, this one is used on

Ubuntu 10.04 LTS

1 2 3 4 5 6

Page 17: SMWCon Fall2013: Wikidata - an experience report

Wrap-up

• Wikidata has great potential as a foundation for

custom developments

• Most troubles we had where because of the very

early version we used

• Some concepts of Wikidata ("snaks") are hard to

understand in the first place

1 2 3 4 5 6

Page 18: SMWCon Fall2013: Wikidata - an experience report

Wrap-up

• Development of FeatureMatrix will continue on base

of Wikidata. But we consider developing the frontend

first and ...

• ... updating the backend when Wikidata and it's API is

more stable.

• Are there any other 3rd party users of Wikidata?

Are Wikidata people interested in exchange of ideas /

code?

1 2 3 4 5 6

Page 19: SMWCon Fall2013: Wikidata - an experience report
Page 20: SMWCon Fall2013: Wikidata - an experience report
Page 21: SMWCon Fall2013: Wikidata - an experience report
Page 23: SMWCon Fall2013: Wikidata - an experience report

Hallo Welt! – Medienwerkstatt GmbH

Residenzstr. 2

93047 Regensburg

Tel. +49 (0) 941 – 660 800

Markus Glaser

Robert Vogel