Canonical name confirmation for H5Z_class3_t filter plugins

[Last Update: 2026/06/05]

HDF5 2.x introduces a new filter plugin class, H5Z_class3_t, that turns
the name field from a free-form debug comment into a load-bearing
canonical name — the string identifier used by the new
H5Pappend_filter API, written into the on-disk filter-pipeline message,
and displayed by h5dump / h5repack. See RFC-HDFG-2026-001 (linked in
the companion PR) and the "Canonical Names" section of
docs/RegisteredFilterPlugins.md for the full contract.

This issue tracks maintainer confirmation of the proposed canonical
name for each currently registered plugin. The companion PR pre-fills a
proposed name in the registry table and marks each row (proposed).

What we need from you

Maintainers: please review the proposed name for your filter ID and
reply on this issue with one explicit line naming the ID and the
name so there is no ambiguity. (Please confirm here on the issue, not
on the companion PR #256 — the PR is for review of the doc edit itself
and confirmations would get lost during code review. Also please don't
use a 👍 reaction on the issue body — there's no way to tell which row
a reaction refers to.)

To confirm:

Confirm: ID 32013, canonical name zfp.

To request a correction (subject to the syntactic rules [A-Za-z0-9_.-],
≤255 bytes, case-sensitive):

Correction: ID 32013, canonical name should be zfp-v2.

Once confirmed, we'll drop the (proposed) marker for your row in
docs/RegisteredFilterPlugins.md and flip the row indicator below from
☐ to ✅. (The indicator is a static symbol — GitHub doesn't allow
interactive checkboxes inside a table — so don't try to click it.)

If you don't have a GitHub account, you can also confirm by email to
[email protected] and we'll relay it onto this issue.

This change has no effect on existing plugin builds. Canonical names
only become load-bearing when a plugin opts into the new H5Z_class3_t
class — that is a separate, opt-in code change in each plugin's source.

Comment window

~6 weeks from this issue's open date. After that, rows without a
maintainer reply will keep their proposed name with an unconfirmed
marker. First-registered-wins still applies if a later replacement is
needed.

Checklist

Hyperlinks in the For Filter column point at the per-filter section of
docs/RegisteredFilterPlugins.md on master. Maintainer attributions are
copied from the "Contact" subsection of each filter's entry.

Special cases

• 257 hzip-silo — name corrected from hzip to hzip-silo by Mark Miller (LLNL) to distinguish it from any silo-independent version of hzip.
• 258 fpzip-silo — ID 258 is a historical duplicate of 32014. Name corrected from fpzip-legacy to fpzip-silo by Mark Miller (LLNL) to distinguish it from any silo-independent version of fpzip.
• 32005 apax and 32016 b3d — the registry entries have no current
  contact. If you maintain these or know who does, please reply so we can
  attribute the canonical name.

Companion PR

Companion PR: #256