Jump to content

Game Metadata Contents

From Game Discovery Project
Revision as of 18:11, 17 August 2025 by Tom Voros (talk | contribs) (Created page with "<onlyinclude> The metadata file should contain the essential details about a game. For example: title, developer, publisher, description, genre, URL(s) to buy or download, etc. We should include information that would be useful to a potential player when browsing games to check out, so we can look at existing platforms like Steam and itch.io for inspiration. We'll need to decide exactly which details we want to include and how they should be represented in JSON.</onlyin...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The metadata file should contain the essential details about a game. For example: title, developer, publisher, description, genre, URL(s) to buy or download, etc. We should include information that would be useful to a potential player when browsing games to check out, so we can look at existing platforms like Steam and itch.io for inspiration.

We'll need to decide exactly which details we want to include and how they should be represented in JSON.

Considerations

Some details will be relatively straightforward to represent (e.g. title is a string property) but others will require more discussion (e.g. is genre a string property? an array of strings? an id/enum of some kind? does it need its own property or should be it be lumped into a more generic property like "tags" the way Steam handles it?).

Even a simple detail like game title may not be as straightforward as it first appears. Should the metadata include localized titles when available? If so, how does that change the JSON format?

Localization

The metadata schema should provide a way to include localized properties. You should also be able to specify what language the base properties are in. We shouldn't assume the base language will always be English.