Major components of a new video game version release (example: Animal Crossing: New Horizons)

Versioning, with objects:

1.1.2 objectIdentifierValue (M, NR)	1.2 objectCategory (M, NR)
Animal Crossing: New Horizons	Intellectual Entity
ACNH Version 2.0.6	Representation
ACHN Version 2.0.6 .nps	File
ACHN Version 2.0.6 .bfres	File

Note: The first row consists of the overarching work of this particular game, Animal Crossing: New Horizons. The second row consists of the representation that aggregates all the components that make up a particular version of the game, usually expressed as a number (Version 2.0.6 as of November 2022). The third row consists of the executable file that is the playable game, the file that is downloaded by the user when purchasing the game at this version from Nintendo. The file extension is proprietary to Nintendo. The fourth row consists of a sample of a 3D renderable object, such as a new character, that could be part of a new game version. The file extension is proprietary to Nintendo.

Versioning, with events:

2.2 eventType (M, NR)	Additional event semantic units?
compiling	2.3 eventDateTime
dissemination	2.4.1 eventDetail
exporting	2.6 linkingAgent
modification	2.7 linkingObject
transfering
patching
moveToProduction
overwriting

Note: 2.2 eventType allows us to pick from the controlled vocabulary of options for event types (https://id.loc.gov/vocabulary/preservation/eventType.html) or to make up our own. When a company releases a new version of a complicated digital game, lots of people and components have to come together to make the release a success. This might include internal procedures like compiling new code (a standardized term) or moving content from a dev site to publication (a custom term). Additionally, existing event types can describe new versions by using additional semantic units to capture information like dates and details.