mime-types-data 3.2024.1203 → 3.2025.0220

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 194a6ab82a7dcc01105cc713335d21c302408686401d62e1f3f72639ec8eb3a8
-  data.tar.gz: f8a358b8ba3d7612698b4f7e06dd258fb0cd852e3d0a691f6194f26015b05c2b
+  metadata.gz: 335e91bdeffdddf816f95c795c8181d90054c62ab203da8e9fc7bba4d401cd32
+  data.tar.gz: e134b524974d525e0bd986038913f80ccdb22732e7e3ad90dd2ecd605882e709
 SHA512:
-  metadata.gz: 5821e06aca5a7cf1a73874f786ff05c60d3e34a1db8231a9e4da0539b2865e2d3803ed5581034eb93436d67ee86db136f83f533144bcd5fbd953aa5974d0d080
-  data.tar.gz: 32dbb4179ef8c8958c27108b0b120a05cea87f7f59be2b1cf5c47cab32caeb803b574b0959779d0ddab73835ee398acb0853b08b8de4f2115472a70b5937304e
+  metadata.gz: 35ba10a184bd975861f12d56876e2a942c8cceb5b6cf35bb0922265fdd6899202db9692ea2c4288c39ac65065cecb6a20138b87b64c0b2e4e84eae1e4670938b
+  data.tar.gz: 6ff470db525f3f5f68e81272ce9fc56d56ea5a5dd4f80c7ff00c1bf610dbecf41c0697a1cfcc117e24c396810cac65b470fa4f05e67909210e00463399c01789

data/{History.md → CHANGELOG.md}

@@ -2,6 +2,44 @@
 
 <!-- automatic-release -->
 
+## 3.2025.0220 / 2025-02-20
+
+- Updated the Apache and IANA media registry entries as of release date
+
+- Added [trusted publishing][tp] for fully automated releases. Developed by
+  Samuel Giddins in [#109][pull-109], merged manually with some updates.
+
+## 3.2025.0204 / 2025-02-04
+
+- Updated the Apache and IANA media registry entries as of release date
+
+- Added the Changelog URL to the README so that RubyGems.org is updated with the
+  `changelog_uri` on release. Contributed by Mark Young in [#96][pull-96].
+
+- Fixed an issue with automated releases that added thousands of files because
+  `vendor/` was no longer ignored.
+
+- Fixed the automated release builder process to handle the case when the
+  `automatic-release` tag is followed by a `## NEXT / YYYY-MM-DD` header so that
+  changes merged normally are picked up on automatic releases. [#98][pull-98]
+
+## 3.2025.0107 / 2025-01-07
+
+- Updated the Apache and IANA media registry entries as of release date
+- Restructured documentation for how I prefer to manage Hoe projects now.
+- Reworked the Rakefile because all data updates are now managed by GitHub
+  Actions and should not be managed manually any longer.
+
+  - `rake release:prepare` now does the same work as `rake release:gha`, but
+    does not commit or create a pull request.
+
+  - `rake convert` no longer has any subtasks.
+
+  - `rake update` has been removed with no replacement.
+
+- Updated `.hoerc` to properly exclude `support/` and `types/` from the
+  manifest.
+
 ## 3.2024.1203 / 2024-12-03
 
 - Updated the Apache and IANA media registry entries as of release date
@@ -23,7 +61,7 @@
 - Updated the Apache and IANA media registry entries as of release date.
 
 - Added `.jxl` extension for `image/jxl`. Contributed by Shane Eskritt in
-  [#81][#81].
+  [#81][pull-81].
 
 ## 3.2024.0806 / 2024-08-06
 
@@ -38,7 +76,7 @@
   - This update adds a new `haptics/` group with three media types defined.
 
 - Moved extensions from `audio/x-aac` to `audio/aac` and mark `audio/x-aac` as
-  obsolete. Based on [#77][#77] by Samuel Williams.
+  obsolete. Based on [#77][pull-77] by Samuel Williams.
 
   - Made the same changes for `audio/flac` and `audio/matroska`.
 
@@ -101,8 +139,8 @@
   information available to deprecate `text/javascript` in favour of
   `application/javascript`. Since the previous update (2022-01-05), IANA has
   officially deprecated `application/javascript` in favour of `text/javascript`.
-  Samuel Williams discovered this in [#55][#55] by noting that all `js` types
-  were marked obsolete in version 3.2023.0218.
+  Samuel Williams discovered this in [#55][issue-55] by noting that all `js`
+  types were marked obsolete in version 3.2023.0218.
 
   A hotfix has been applied to resolve this. However, note that
   `application/javascript` will not be returned by default, only
@@ -113,15 +151,15 @@
 - Updated the Apache and IANA media registry entries as of release date.
 
 - Mohammed Gad added the `jfif` file extension for `image/jpeg` text format.
-  [#52][#52]
+  [#52][pull-52]
 
 - Reworked the loading of IANA provisional media registries to merge them into
   the top-level media-type registries instead of a standalone registry file.
-  [#53][#53] originally identified by Chris Salzberg in [#50][#50].
+  [#53][pull-53] originally identified by Chris Salzberg in [#50][pull-50].
 
   It is worth noting that this is an _imperfect_ solution as if a media type is
   provisionally registered and withdrawn, it will linger in the registry with no
-  clean way of identifying them at the moment. See [#54][#54].
+  clean way of identifying them at the moment. See [#54][issue-54].
 
   This release also fixes [ruby-mime-types#163][ruby-mime-types#163], where logs
   show "Type application/netcdf is already registered as a variant of
@@ -132,25 +170,25 @@
 - Updated the Apache and IANA media registry entries as of release date.
 
 - Fixed an incorrect definition of `image/bmp`, which had been marked obsolete
-  and later registered. Fixed [#48][#48], found by William T. Nelson.
+  and later registered. Fixed [#48][issue-48], found by William T. Nelson.
 
 ## 3.2021.1115 / 2021-11-15
 
 - Updated the Apache and IANA media registry entries as of release date.
 
 - Added conversion utilities that support the `mini_mime` data format. These
-  have been ported from the [mini_mime][mini_mime] repository. [#47][#47]
+  have been ported from the [mini\_mime][mini_mime] repository. [#47][pull-47]
 
-- Added IANA provisional media registries. Added some notes to Contributing.md
+- Added IANA provisional media registries. Added some notes to CONTRIBUTING.md
   about the transient nature of the provisional registration data. This was
-  triggered in part by a pull request by Jon Sneyers. Thanks! [#45][#45],
-  [#43][#43]
+  triggered in part by a pull request by Jon Sneyers. Thanks! [#45][pull-45],
+  [#43][pull-43]
 
 ## 3.2021.0901 / 2021-09-01
 
 - Updated the Apache and IANA media registry entries as of release date.
 
-- Added file extension for WebVTT text format. [#46][#46]
+- Added file extension for WebVTT text format. [#46][pull-46]
 
 ## 3.2021.0704 / 2021-07-04
 
@@ -160,7 +198,7 @@
 
 - Updated the Apache and IANA media registry entries as of release date.
 
-- Added file extension for AVIF video format. [#40][#40]
+- Added file extension for AVIF video format. [#40][pull-40]
 
 ## 3.2021.0212 / 2021-02-12
 
@@ -175,67 +213,68 @@
 
 - Updated the IANA media registry entries as of release date.
 
-- Added `application/x-zip-compressed`. [#36][#36]
+- Added `application/x-zip-compressed`. [#36][pull-36]
 
 - Updated the contributing guide to include information about the release
-  process as described in [#18][#18]
+  process as described in [#18][issue-18]
 
-- Corrected a misspelling of Yoran Brondsema’s name. Sorry, Yoran. [#35][#35]
+- Corrected a misspelling of Yoran Brondsema's name. Sorry, Yoran.
+  [#35][pull-35]
 
 ## 3.2020.0512 / 2020-05-12
 
 - Updated the IANA media registry entries as of release date.
 
-- Added file extensions for HEIC image types. [#34][#34]
+- Added file extensions for HEIC image types. [#34][pull-34]
 
 ## 3.2020.0425 / 2020-04-25
 
 - Updated the IANA media registry entries as of release date.
 
 - Added several RAW image types based on data from GNOME RAW Thumbnailer.
-  [#33][#33] fixing [#32][#32]
+  [#33][pull-33] fixing [#32][issue-32]
 
-- Added `audio/wav`. [#31][#31]
+- Added `audio/wav`. [#31][pull-31]
 
-- Added a type for Smarttech notebook files. [#30][#30]
+- Added a type for Smarttech notebook files. [#30][pull-30]
 
-- Added an alias for audio/m4a files. [#29][#29]
+- Added an alias for audio/m4a files. [#29][pull-29]
 
-- Added application/x-ms-dos-executable. [#28][#28]
+- Added application/x-ms-dos-executable. [#28][pull-28]
 
 ## 3.2019.1009 / 2019-10-09
 
 - Updated the IANA media registry entries as of release date.
 
 - Reordered the `.ai` extension so that it is not the preferred extension for
-  `application/pdf` [#24][#24]
+  `application/pdf` [#24][pull-24]
 
 ## 3.2019.0904 / 2019-09-04
 
 - Updated the IANA media registry entries as of release date.
 
 - Moved the `.ai` extension from `application/postscript` to `application/pdf`.
-  [#23][#23] fixing [#22][#22]
+  [#23][pull-23] fixing [#22][issue-22]
 
 ## 3.2019.0331 / 2019-03-31
 
 - Updated the IANA media registry entries as of release date.
 
-- Added support for `application/wasm` with extension `.wasm`. [#21][#21]
+- Added support for `application/wasm` with extension `.wasm`. [#21][pull-21]
 
-- Fixed `application/ecmascript` extensions. [#20][#20]
+- Fixed `application/ecmascript` extensions. [#20][pull-20]
 
 ## 3.2018.0812 / 2018-08-12
 
-- Added `.xsd` extension to `text/xml`. [#10][#10]
+- Added `.xsd` extension to `text/xml`. [#10][pull-10]
 
 - Added `.js` and `.mjs` extensions to `text/ecmascript` and `text/javascript`.
-  [#11][#11]
+  [#11][pull-11]
 
-- Added `.ipa` extension to `application/octet-stream`. [#12][#12]
+- Added `.ipa` extension to `application/octet-stream`. [#12][pull-12]
 
 - Moved extensions `.markdown` and `.md` and added `.mkd` extension to
-  `text/markdown`. [#13][#13]
+  `text/markdown`. [#13][pull-13]
 
 - Because of a bug found with mime-types 3 before 3.2.1, this version requires
   mime-types 3.1 or later to manage data.
@@ -254,7 +293,7 @@
 - Updated the known extension list for application/octet-stream and
   application/pgp-encrypted to include gpg as an extension. Fixes
   [#3](https://github.com/mime-types/mime-types-data/pull/3) by Tao Guo
-  (@taoza).
+  ([@taoza](https://github.com/taoza)).
 - Updated the IANA media registry entries as of release date:
 
   - Updated metadata for application/EmergencyCallData.Comment+xml,
@@ -307,7 +346,7 @@
 ## 3.2015.1120 / 2015-11-20
 
 - Extracted from [ruby-mime-types][rmt].
-- Added a [Code of Conduct].
+- Added a [Code of Conduct][Code of Conduct].
 - The versioning has changed to be semantic on format plus date in two parts.
 
   - All registry formats have been updated to remove deprecated data.
@@ -348,7 +387,7 @@
 
 ## 2.6 / 2015-05-25
 
-- Steven Michael Thomas (@stevenmichaelthomas) added `woff2` as an extension to
+- Steven Michael Thomas ([@stevenmichaelthomas](https://github.com/stevenmichaelthomas)) added `woff2` as an extension to
   application/font-woff, [ruby-mime-types#99][ruby-mime-types#99].
 - Updated the IANA media registry entries as of release date:
   - Updated metadata for application/jose, application/jose+json,
@@ -380,17 +419,17 @@
     (RFC7396), application/smil, application/vnd.arastra.swi,
     application/vnd.geocube+xml, application/vnd.gmx, application/xhtml+xml,
     text/directory.
-- Andy Brody (@ab) fixed a pair of embarrassing typos in text/csv and
+- Andy Brody ([@ab](https://github.com/ab)) fixed a pair of embarrassing typos in text/csv and
   text/tab-separated-values,
   [ruby-mime-types#89](https://github.com/mime-types/ruby-mime-types/pull/89).
-- Aggelos Avgerinos (@eavgerinos) added the unregistered MIME type
+- Aggelos Avgerinos ([@eavgerinos](https://github.com/eavgerinos)) added the unregistered MIME type
   image/x-ms-bmp with the extension `bmp`,
   [ruby-mime-types#90](https://github.com/mime-types/ruby-mime-types/pull/90).
 
 ## 2.4.2 / 2014-10-15
 
 - Added application/vnd.ms-outlook as an unregistered MIME type with the
-  extension `msg`. Provided by @keerthisiv in
+  extension `msg`. Provided by [@keerthisiv](https://github.com/keerthisiv) in
   [ruby-mime-types#72](https://github.com/mime-types/ruby-mime-types/pull/72).
 
 ## 2.4.1 / 2014-10-07
@@ -448,7 +487,7 @@
 ## 2.2 / 2014-03-14
 
 - Added <tt>.sj</tt> to `application/javascript` as provided by Brandon
-  Galbraith (@brandongalbraith) in
+  Galbraith ([@brandongalbraith](https://github.com/brandongalbraith)) in
   [ruby-mime-types#58](https://github.com/mime-types/ruby-mime-types/pull/58).
 - Marked application/excel and application/x-excel as obsolete in favour of
   application/vnd.ms-excel per
@@ -612,8 +651,11 @@
 [#55]: https://github.com/mime-types/mime-types-data/issues/55
 [#77]: https://github.com/mime-types/mime-types-data/pull/77
 [#81]: https://github.com/mime-types/mime-types-data/pull/81
+[#96]: https://github.com/mime-types/mime-types-data/pull/96
+[#98]: https://github.com/mime-types/mime-types-data/pull/98
 [rmt]: https://github.com/mime-types/ruby-mime-types
-[code of conduct]: Code-of-Conduct.md
+[code of conduct]: CODE_OF_CONDUCT.md
 [mini_mime]: https://github.com/discourse/mini_mime/issues/41
 [ruby-mime-types#99]: https://github.com/mime-types/ruby-mime-types/pull/99
 [ruby-mime-types#163]: https://github.com/mime-types/ruby-mime-types/issues/163
+[tp]: https://guides.rubygems.org/trusted-publishing/

data/CONTRIBUTING.md

@@ -0,0 +1,150 @@
+# Contributing
+
+Contribution to mime-types-data is encouraged in any form: a bug report, new
+MIME type definitions, or additional code to help manage the MIME types. There
+are a few DOs and DON'Ts for contributions.
+
+- DO:
+
+  - Keep the coding style that already exists for any updated Ruby code (support
+    or otherwise). I use [Standard Ruby][standardrb] for linting and formatting.
+
+  - Use thoughtfully-named topic branches for contributions. Rebase your commits
+    into logical chunks as necessary.
+
+  - Use [quality commit messages][qcm].
+
+  - Add your name or GitHub handle to `CONTRIBUTORS.md` and a record in the
+    `CHANGELOG.md` as a separate commit from your main change. (Follow the style
+    in the `CHANGELOG.md` and provide a link to your PR.)
+
+- DO NOT:
+
+  - Modify `VERSION` in `lib/mime/types/data.rb`. When your patch is accepted
+    and a release is made, the version will be updated at that point. Most
+    likely, once merged, your release will be rolled into the next automatic
+    release.
+
+  - Modify `mime-types-data.gemspec`; it is a generated file. (You _may_ use
+    `rake gemspec` to regenerate it if your change involves metadata related to
+    gem itself).
+
+  - Modify the `Gemfile`.
+
+  - Modify any files in `data/`. Any changes to be captured here will be
+    automatically updated on the next release.
+
+Although mime-types-data was extracted from the [Ruby mime-types][rmt] gem and
+the support files are written in Ruby, the _target_ of mime-types-data is any
+implementation that wishes to use the data as a MIME types registry, so I am
+particularly interested in tools that will create a mime-types-data package for
+other languages.
+
+## Adding or Modifying MIME Types
+
+The Ruby mime-types gem loads its data from files encoded in the `data`
+directory in this gem by loading `mime-types-data` and reading
+MIME::Types::Data::PATH. These files are compiled files from the collection of
+data in the `types` directory.
+
+> [!WARNING]
+>
+> Pull requests that include changes to files in `data/` will require amendment
+> to revert these files.
+
+New or modified MIME types should be edited in the appropriate YAML file under
+`types`. The format is as shown below for the `application/xml` MIME type in
+`types/application.yml`.
+
+```yaml
+- !ruby/object:MIME::Type
+  content-type: application/xml
+  encoding: 8bit
+  extensions:
+    - xml
+    - xsl
+  references:
+    - IANA
+    - RFC3023
+  xrefs:
+    rfc:
+      - rfc3023
+  registered: true
+```
+
+There are other fields that can be added, matching the fields discussed in the
+documentation for MIME::Type. Pull requests for MIME types should just contain
+the changes to the YAML files for the new or modified MIME types; I will convert
+the YAML files to JSON prior to a new release. I would rather not have to verify
+that the JSON matches the YAML changes, which is why it is not necessary to
+convert for the pull request.
+
+If you are making a change for a private fork, use `rake convert:yaml:json` to
+convert the YAML to JSON, or `rake convert:yaml:columnar` to convert it to the
+new columnar format.
+
+### Updating Types from the IANA or Apache Lists
+
+If you are maintaining a private fork and wish to update your copy of the MIME
+types registry used by this gem, you can do this with the rake tasks:
+
+```sh
+$ rake mime:iana
+$ rake mime:apache
+```
+
+#### A Note on Provisional Types
+
+Provisionally registered types from IANA are contained in the `types/*.yaml`
+files. Per IANA,
+
+> This registry, unlike some other provisional IANA registries, is only for
+> temporary use. Entries in this registry are either finalized and moved to the
+> main media types registry or are abandoned and deleted. Entries in this
+> registry are suitable for use for development and test purposes only.
+
+Provisional types are rewritten when updated, so pull requests to manually
+customize provisional types (such as with extensions) are considered lower
+priority. It is recommended that any updates required to the data be performed
+in your application if you require provisional types.
+
+## The Release Process
+
+The release process is almost completely automated, where upstream MIME types
+will be updated weekly (on Tuesdays) and be presented in a reviewable pull
+request. Once merged, I need to perform a release and the update is complete.
+
+With the addition of [trusted publishing][tp], there should no longer be a need
+for manual releases outside of the update cycle. Pull requests merged between
+cycles will be released on the next cycle.
+
+If it becomes necessary to perform a manual release, IANA updates should be
+performed manually.
+
+1. Review any outstanding issues or pull requests to see if anything needs to be
+   addressed. This is necessary because there is no automated source for
+   extensions for the thousands of MIME entries. (Suggestions and/or pull
+   requests for same would be deeply appreciated.)
+2. `bundle install`
+3. Review the changes to make sure that the changes are sane. The IANA data
+   source changes from time to time, resulting in big changes or even a broken
+   step 4. (The most recent change was the addition of the `font/*` top-level
+   category.)
+4. Write up the changes in `CHANGELOG.md`. If any PRs have been merged, these
+   should be noted specifically and contributions should be added in
+   `Contributing.md`.
+5. Ensure that the `VERSION` in `lib/mime/types/data.rb` is updated with the
+   current date UTC.
+6. Run `rake gemspec` to ensure that `mime-types.gemspec` has been updated.
+7. Commit the changes and push to GitHub. The automated trusted publishing
+   workflow will pick up the changes.
+
+This is based on an issue [#18][issue-18].
+
+[issue-18]: https://github.com/mime-types/mime-types-data/issues/18
+[hoe]: https://github.com/seattlerb/hoe
+[qcm]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+[release-gem]: https://github.com/rubygems/release-gem
+[rmt]: https://github.com/mime-types/ruby-mime-types/
+[standardrb]: https://github.com/standardrb/standard
+[tp]: https://guides.rubygems.org/trusted-publishing/

data/CONTRIBUTORS.md

@@ -0,0 +1,54 @@
+# Contributors
+
+- Austin Ziegler created mime-types.
+
+Thanks to everyone else who has contributed to mime-types:
+
+- Aaron Patterson
+- Aggelos Avgerinos
+- Alessio Parma
+- Alex Balhatchet
+- Andre Pankratz
+- Andrey Eremin
+- Andy Brody
+- Arnaud Meuret
+- Bradley Meck
+- Brandon Galbraith
+- Chris Gat
+- Chris Salzberg
+- David Genord
+- Eric Marden
+- Garret Alfert
+- Godfrey Chan
+- Greg Brockman
+- Hans de Graaff
+- Henrik Hodne
+- Jeremy Evans
+- John Gardner
+- Jon Sneyers
+- Jonas Petersen
+- Juanito Fatas
+- Keerthi Siva
+- Ken Ip
+- Łukasz Śliwa
+- Lucia
+- Mark Young
+- Martin d'Allens
+- Mauricio Linhares
+- Mohammed Gad
+- Myk Klemme
+- nycvotes-dev
+- Postmodern
+- Richard Hirner
+- Richard Hurt
+- Richard Schneeman
+- Robert Buchberger
+- Samuel Giddins
+- Samuel Williams
+- Sergio Baptista
+- Shane Eskritt
+- Tao Guo
+- Thomas Leese
+- Tibor Szolár
+- Todd Carrico
+- Yoran Brondsema

data/{Licence.md → LICENCE.md}

@@ -1,6 +1,6 @@
 ## Licence
 
-- Copyright 2003–2024 Austin Ziegler and other contributors.
+- Copyright 2003–2025 Austin Ziegler and other contributors.
 
 The software in this repository is made available under the MIT license.
 

data/Manifest.txt

@@ -1,7 +1,8 @@
-Code-of-Conduct.md
-Contributing.md
-History.md
-Licence.md
+CHANGELOG.md
+CODE_OF_CONDUCT.md
+CONTRIBUTING.md
+CONTRIBUTORS.md
+LICENCE.md
 Manifest.txt
 README.md
 Rakefile
@@ -19,18 +20,3 @@ data/mime.use_instead.column
 data/mime.xrefs.column
 lib/mime-types-data.rb
 lib/mime/types/data.rb
-types/application.yaml
-types/audio.yaml
-types/chemical.yaml
-types/conference.yaml
-types/drawing.yaml
-types/example.yaml
-types/font.yaml
-types/haptics.yaml
-types/image.yaml
-types/message.yaml
-types/model.yaml
-types/multipart.yaml
-types/text.yaml
-types/video.yaml
-types/world.yaml

data/README.md

@@ -1,8 +1,9 @@
 # mime-types-data
 
 - home :: https://github.com/mime-types/mime-types-data/
-- code :: https://github.com/mime-types/mime-types-data/
 - issues :: https://github.com/mime-types/mime-types-data/issues
+- code :: https://github.com/mime-types/mime-types-data/
+- changelog :: https://github.com/mime-types/mime-types-data/blob/main/CHANGELOG.md
 
 ## Description
 
@@ -13,11 +14,11 @@ extensions to look up the likely MIME type definitions.
 
 ### About MIME Media Types
 
-MIME media types are used in MIME-compliant communications, as in e-mail or
-HTTP traffic, to indicate the type of content which is transmitted. The
-registry provided in mime-types-data contains detailed information about MIME
-entities. There are many types defined by RFCs and vendors, so the list is long
-but invariably; don't hesitate to offer additional type definitions for
+MIME media types are used in MIME-compliant communications, as in e-mail or HTTP
+traffic, to indicate the type of content which is transmitted. The registry
+provided in mime-types-data contains detailed information about MIME entities.
+There are many types defined by RFCs and vendors, so the list is long but
+invariably; don't hesitate to offer additional type definitions for
 consideration. MIME type definitions found in mime-types are from RFCs, W3C
 recommendations, the [IANA Media Types registry][registry], and user
 contributions. It conforms to RFCs 2045 and 2231.
@@ -26,20 +27,20 @@ contributions. It conforms to RFCs 2045 and 2231.
 
 This registry contains the MIME media types in four formats:
 
-- A YAML format matching the Ruby mime-types library objects (MIME::Type).
-  This is the primary user-editable format for developers. It is _not_
-  shipped with the gem due to size considerations.
+- A YAML format matching the Ruby mime-types library objects (MIME::Type). This
+  is the primary user-editable format for developers. It is _not_ shipped with
+  the gem due to size considerations.
 - A JSON format converted from the YAML format. Prior to Ruby mime-types 3.0,
   this was the main consumption format and is still recommended for any
-  implementation that does not wish to implement the columnar format, which
-  has a significant implementation effort cost.
-- An encoded text format splitting the data for each MIME type across
-  multiple files. This columnar data format reduces the minimal data load
-  substantially, resulting in a performance improvement at the cost of more
-  complex code for loading the data on-demand. This is the default format for
-  Ruby mime-types 3.0.
-- An encoded text format for use with [`mini_mime`][] (as of 3.2021.1108). This
-  can be enabled with:
+  implementation that does not wish to implement the columnar format, which has
+  a significant implementation effort cost.
+- An encoded text format splitting the data for each MIME type across multiple
+  files. This columnar data format reduces the minimal data load substantially,
+  resulting in a performance improvement at the cost of more complex code for
+  loading the data on-demand. This is the default format for Ruby mime-types
+  3.0.
+- An encoded text format for use with [`mini_mime`][minimime]. This can be
+  enabled with:
 
   ```ruby
   MiniMime::Configuration.ext_db_path =
@@ -50,24 +51,24 @@ This registry contains the MIME media types in four formats:
 
 ## mime-types-data Modified Semantic Versioning
 
-mime-types-data uses a heavily modified [Semantic Versioning][] scheme to
-indicate that the data formats compatibility based on a `SCHEMA` version and
-the date of the data update: `SCHEMA.YEAR.MONTHDAY`.
+mime-types-data uses a heavily modified [Semantic Versioning][semver] scheme to
+indicate that the data formats compatibility based on a `SCHEMA` version and the
+date of the data update: `SCHEMA.YEAR.MONTHDAY`.
 
 1. If an incompatible data format change is made to any of the supported
-   formts, `SCHEMA` will be incremented. The current `SCHEMA` is 3, supporting
+   formats, `SCHEMA` will be incremented. The current `SCHEMA` is 3, supporting
    the YAML, JSON, and columnar formats required for Ruby mime-types 3.0.
 
-2. When the data is updated, the `YEAR.MONTHDAY` combination will be updated.
-   An update on the last day of October 2015 would be written as `2015.1031`,
+2. When the data is updated, the `YEAR.MONTHDAY` combination will be updated. An
+   update on the last day of October 2015 would be written as `2015.1031`,
    resulting in the full version of `3.2015.1031`.
 
 3. If multiple versions of the data need to be released on the same day due to
-   error, there will be an additional `REVISION` field incremented on the end
-   of the version. Thus, if three revisions need to be published on October
-   31st, 2015, the last release would be `3.2015.1031.2` (remember that the
-   first release has an implied `0`.)
+   error, there will be an additional `REVISION` field incremented on the end of
+   the version. Thus, if three revisions need to be published on October 31st,
+   2015, the last release would be `3.2015.1031.2` (remember that the first
+   release has an implied `0`.)
 
 [registry]: https://www.iana.org/assignments/media-types/media-types.xhtml
-[semantic versioning]: http://semver.org/
-[`mini_mime`]: https://github.com/discourse/mini_mime
+[semver]: http://semver.org/
+[minimime]: https://github.com/discourse/mini_mime