BlueForge Feature Matrix: WikiData - An experience report
From semantic-mediawiki.org
| SMWCon Fall 2013 | |
|---|---|
| BlueForge Feature Matrix: Wikidata - An experience report | |
| Talk details | |
| Description: | This talk covers the experience made with Wikidata by "Hallo Welt! Medienwerkstatt GmbH". It's about why we chose it and what were the difficulties we had to deal with. |
| Speaker(s): | Markus Glaser, Robert Vogel |
| Slides: | see here |
| Type: | Talk, Technical talk |
| Audience: | Everyone, Developers |
| Event start: | 2013/10/29 01:30:00 PM |
| Event finish: | 2013/10/29 02:00:00 PM |
| Length: | 30 minutes |
| Video: | click here |
| Keywords: | Wikidata, BlueForge, API |
| Give feedback | |
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.
Contents
[hide]What is BlueForge? What is a Software Feature Matrix?[edit]
- Software directory
- Stakeholder
- User / enthusiast
- Decision makers
- Vendors
- Consultants
- Not: End user in need for a manual
Requirements / Evaluation / Selection[edit]
- Specifics of software features
- there are variants (e.g. "free" vs. "professional version") / forks
- 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 / cateories of software
- Features can be added / evaluated within the wiki/wikidata via UI
- State of knowledge (Wikidata) vs. actual knowledge (SMW)
Proposed data model[edit]
Within Wiki
- 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
Structured data[edit]
- A piece of software is an item
- A feature is a property
- features have qualifiers (since version, user rating, ...)
- features have sources (vendor, user)
- features have (custom) data types
- Groups are an item
- Features of a group are a property of property (aka schema)
- Naming is consistent between wiki and wikidata -> link is by convention
Server setup[edit]
- there are two systems: Wiki and (local instance of) Wikidata
Experience with Wikidata[edit]
- Data model can be implemented in Wikidata. Philosopy seems to overlap
- Architecture seems to be flexible enough
- Officially not ready for 3rd party use: we are very early adopters :)
- Schema via UI / tool support
- Hard to set up, we used vagrant in the end (?)
- PHP dependency: do not use > 5.3.6 (? have to look that up)
- Value autocomplete seems to be resource intensive without additional data stores
