Safe Mode: On
Game Sprite Metadata Design Using Dublin Core

Collection
For this assignment, I have chosen to design an application profile for the collection of video game sprites in the Game Sprite Archives.

Target Audience: Video Game Enthusiasts

Information Need
At the risk of overgeneralizing, I’m going make a blanket statement that video game enthusiasts have very exacting information needs. Thus, when seeking video game sprites, this user group would expect to find exacting information about the video game sprites they might search for. These individuals will expect to quickly locate the video game sprites of their choice, select/download/use/regard the sprite(s) that they were seeking, browse forgotten sprites because they’re now in reach, and perhaps gather trivia along the way to impress their video game enthusiast friends.

Rationale
I thought Dublin Core would be a good metadata set for this collection because it provides a solid baseline for describing information objects. Clearly, a video game sprite is nothing if not an information object. DC is frequently used to describe culturally relevant objects. While many frown upon the habits of video gamers, these individuals most certainly cohere into a culture of their own (perhaps as a defense mechanism against judgmental outsiders). Thus, video game sprites qualify as cultural objects that could reasonably be expected to be described by the Dublin Core. Dublin Core is a simple and straightforward standard, and video game sprites tend to have simple characteristics. Therefore, the Dublin Core is likely to be an excellent metadata set for this collection.

Major Elements
The application profile is structured as follows:

• games – container for many “games”
o game – contains information about each game and also the “sprites” element
 sprites – container for many “sprites”
• sprite – contains information about each sprite

The majority of information about “games” and “sprites” is described using http://purl.org/dc/terms/ namespace elements such as “title,” “date,” “format,” and “publisher.”

Some descriptive information is captured in the gsa: namespace such as video game genre or sprite classifiers that define the kind of sprite and whether it is animated or not.

Controlled Vocabularies
Recommended vocabularies were implemented in the Dublin Core schema, but were mostly unused in the sprite schema. Default controlled vocabularies such as MIME were used for format of the sprites, and if necessary, RFC5646 was designated the default scheme to be used for language.

The W3CDTF syntax encoding scheme for dates was implemented, bit it was unclear whether the encoding scheme was able to provide feedback as to the accuracy of structure of the dates entered in the instance.


Added: Jan-31-2011 Occurred On: Jan-29-2011
By: mserni
In:
Other
Tags: video games, metadata design, dublin core, dcmi, xsd
Views: 7558 | Comments: 3 | Votes: 0 | Favorites: 0 | Shared: 0 | Updates: 0 | Times used in channels: 1
You need to be registered in order to add comments! Register HERE