User:Diggr/Data Models of Video Games
Thoughts about a conceptual data model for Video Games in Wikidata [DRAFT]
[edit]Video Games are very complex cultural artifacts and are embedded in complex distribution processes as well. This causes a need of a flexible and fine granular data model with different conceptual layers. As Jett et al[1] described, it's challeging to differ among various editions of games "because of releases of the same game in multiple regions, for multiple platforms or systems, as well as special "collector's editions" or other limited special releases.". In additon there are even more challenges to solve. What about localized or censored releases which results in a different look or story from the origin game?[2]
More questions, ideas and examples on that topic can be found at User:Jean-Frédéric/Videogames data model, too.
One Wikidata Item for each Video Game
[edit]This seems very challeging since the Wikidata model doesn't support complex data. One soultion is to use qualifiers in a huge amount. For instance, every platform (means hardware or system requirement) depending statement must have a qualifier with the specific platform eg. distribution or input method.
But to go further:
- Special Editions, Compilations, DLCs/Add-Ons/Expansions, Demos - are these NEW items with a relationship to an item or part of an item?
- Release History (Re-releases, Mobile Version, Patches (nice example: The Legend of Zelda: Breath of the Wild @ mobygames))
- Publishers can differ from one release country to another (Final Fantasy VII (Q214232) do it right, I think)
One more question is, how far do we want to go in Wikidata? Credits? Barcodes/Product IDs?
Disadavantages:
- There are a very large number of items with a mashup of different things. (eg. the Property:P479 of a PlayStation 4 game differ to the port of the same game for PC)
- External identifiers points to different conceptual entities. For Instance: Metal Gear Solid V: The Phantom Pain (Q2522391) has Property:P1933 which points to https://www.mobygames.com/game/metal-gear-solid-v-the-phantom-pain but, Mobygames describes games at an editon level. That means there are several records for one game. In this case there are two more editions which should be link to Metal Gear Solid V: The Phantom Pain (Q2522391). Mobygames could also be used to point to a platform version with http://www.mobygames.com/game/playstation-4/metal-gear-solid-v-the-phantom-pain-western-tack
Split Wikidata Items into different Video Game Layers
[edit]Like in book context there could be games (work) and editions (expression) of a game.[3][4] A local release item would be to particular, I think. That could be propably done by using qualifiers.
Example:
The relationship between Metal Gear Solid 3: Snake Eater (Q247935) and Metal Gear Solid 3: Subsistence (Q12636722). Subsistance is a revised and enlarged version of Snake Eater.
Advantages:TBD
Disadvanteges: TBD
Release History
[edit]There is no convention how to add release dates to a video game. Here, I'm trying to find out what approaches were used and which advantages and disadvantages are related to them.
I use one game to illustrate these and add real examples below the table.
- A) platform (P400) with qualifier
| platform (P400) |
| ||||||||||||||||||||||||||||||||||||||||||||||
| add value | |||||||||||||||||||||||||||||||||||||||||||||||
Example: Grand Theft Auto 2 (Q94460) (platform + publication date)
SELECT ?entity ?entityLabel ?platformItemLabel ?date ?placeLabel
WHERE {
?entity wdt:P31 wd:Q7889.
?entity p:P400 ?platform.
?platform ps:P400 ?platformItem.
?platform pq:P577 ?date.
OPTIONAL { ?platform pq:P291 ?place. }
SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
None with the combination of platform + publication date + place of publication. 59 with combination of platform + publication date
Advantages:
Disadvantages:
---
- B) publication date (P577) with qualifier
| publication date (P577) |
| |||||||||||||||||||||||||||||||||
| add value | ||||||||||||||||||||||||||||||||||
Example: Call of Duty 4: Modern Warfare (Q76255), Final Fantasy VII (Q214232)
SELECT ?entity ?entityLabel ?releaseDateItem ?platformLabel ?placeLabel
WHERE {
?entity wdt:P31 wd:Q7889.
?entity p:P577 ?releaseDate.
?releaseDate ps:P577 ?releaseDateItem.
?releaseDate pq:P400 ?platform.
?releaseDate pq:P291 ?place.
SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
It turns out, that this find no widespread use at all... Only 231 Items with the combination of publication date + platform + place of publication. 440 with combination of publication date + platform.
Advantages:
Disadvantages:
---
Often publication date (P577) is used only once and refer to the first release date of a game.
Wikidata Items as concept hubs
[edit]Since there are many huge websites/platforms/databases for video game information (Giantbomb, Mobygames, IGDB, ...), Wikidata could be the linking hub for distributed information about video games.
Different goals and perspectives causes heterogeneous data models. Wikidata can bring together different concepts of external databases if it's goal is to record games as an "abstract entity that describes features that are shared among different editions"[1].
This abstract entity finds no widespread use among external databases so it's difficult for users/fans/researches to find a comprehensive view on a particular "game"[5]. But in Wikipedia articles, a game is described compehensive - not single editions.
Examples:
Summary and future tasks
[edit]For other cultural objects such as books or movies there are differentieated models. Wikidata:WikiProject Books | Wikidata:WikiProject Movies/Properties
For me, it lacks on a clear definition and demarcation for what a Wikidata Item of a Video Game stands for. The product for purchase which includes also merchandise? The intellectual work and property of a publisher/developer and what is commonly known as THE game?
- ↑ 1.0 1.1 Q50180436
- ↑ My favorite example is the game NieR. The japanese XBox 360 version is named "NieR Gestalt", the PS3 version "NieR Replicant". NIER/NieR Gestalt: An older main character + father/daugther story NieR Replicant: A younger main character + brother/sister story
- ↑ Q16388
- ↑ Wikidata:WikiProject Books
- ↑ To devide between two games at this level is sometimes a complex tasks, too. "When two or more game researchers are using the word ‘game’, they may or may not be speaking about the same thing" (Aarseth, E. “Define real, Moron!”, DIGAREC Series, 6 (2011), 50-69.)