Shared MIME-info Database

Shared MIME-info Database
Name	Shared MIME-info Database
Developer	freedesktop.org
Released	2000s
Programming language	XML, C
Operating system	Unix-like
License	MIT

Shared MIME-info Database

The Shared MIME-info Database is a centralized collection of MIME media type mappings and file extension rules used to associate filename patterns with media handlers across Linux, Unix, and FreeBSD desktops; it standardizes interactions among GNOME, KDE, Xfce, LXDE, and MATE environments. It provides a consistent registry referenced by freedesktop.org specifications, enabling file managers, desktop environments, and applications to determine default application associations and icon theme selection. The database complements system-level registries maintained by distributions such as Debian, Ubuntu, Fedora, Arch Linux, and openSUSE.

Overview

The project implements the freedesktop.org Shared MIME-info Database specification to map MIME types like image/png, text/html, application/pdf to file extensions and magic number tests. It uses XML-based "mime-info" files to describe glob patterns, magic rules, and aliases allowing GNOME Files (formerly Nautilus), Dolphin, Thunar, Caja, and PCManFM to present consistent file association behavior. The repository is maintained as part of the freedesktop.org project and distributed through shared-mime-info packages in many Linux distributions.

History and Development

Work began in the early 2000s when interoperability issues emerged between KDE, GNOME, and smaller desktop environments; contributors included developers from X.Org Foundation, Red Hat, Novell, Canonical, and SUSE. Early milestones aligned with releases of freedesktop.org specifications and were influenced by portability efforts from X Window System toolchains and standards defined by the IETF for MIME handling. Major updates integrated community submissions from projects such as Mozilla Firefox, Chromium, LibreOffice, GIMP, and Inkscape, while packaging and distribution coordination involved teams from Debian Project, Fedora Project, and Arch Linux.

Data Format and Structure

The database uses XML "mime-info" files conforming to the freedesktop.org XML schema. Elements describe mime-type entries with nested glob patterns, magic tests (byte-level signatures), and sub-class-of relationships for inheritance akin to IANA media type hierarchies. Each entry can reference icon names from Icon Theme Specification and specify generic icon fallbacks used by desktop environments. The structure supports aliases to accommodate vendor-specific types and maps to distribution packaging metadata used by dpkg, RPM, and pacman.

Implementation and Use

Implementations parse the XML to populate binary caches consumed by libraries like shared-mime-info's reference C implementation and bindings for GLib, Qt, and Python. Applications query the cache using APIs exposed by GIO, KService, and xdg-utils to resolve default handlers, present human-readable MIME descriptions, and determine icons. The system is used by file indexing services such as Tracker and search tools like Beagle for content-type categorization, and by email clients such as Evolution and Thunderbird for attachment handling.

Integration with Desktop Environments and Applications

Desktop shells and file managers integrate the database to display appropriate file icons, context menu actions, and "Open With" lists; examples include GNOME Shell, KWin, KDE Plasma, and Xfce Panel. Office suites like LibreOffice and Calligra Suite consult the registry to suggest import/export handlers, while media players such as VLC and Rhythmbox use it to classify audio and video files. Web browsers (Firefox, Chromium) and image viewers like Eye of GNOME and gThumb rely on the same shared data to ensure consistent handling across environments.

Governance and Maintenance

Maintenance follows an open contribution model hosted by freedesktop.org with patch review by maintainers and contributors from projects such as GNOME Project, KDE e.V., and vendor teams from Red Hat, Canonical, and SUSE. Changes undergo review via version control, continuous integration checks, and coordination with Linux Distribution packaging teams for stable releases. Policy discussions and specification edits occur on freedesktop mailing lists and tracking systems used by organizations including X.Org Foundation and OpenDesktop.org stakeholders.

Compatibility and Limitations

While widely adopted across Unix-like systems, the database does not replace platform-specific registries such as Windows Registry or macOS Launch Services and therefore requires translation layers in cross-platform applications like Electron, Flatpak, and Snapcraft. Limitations include ambiguous file extension overlap, incomplete magic coverage for proprietary formats produced by vendors like Microsoft, Adobe Inc., and Apple Inc., and latency in synchronizing new types across distributions such as Debian, Fedora, and Arch Linux. Backwards compatibility is maintained via aliases and inheritance, but edge cases persist when applications bypass shared libraries and implement custom heuristics.

Category:Freedesktop.org Category:File format