Filter plugin maintainers: confirm a canonical name for your filter

HDF5 Library
1

If you maintain a registered HDF5 filter plugin, we’d like a few minutes of your time.

What’s changing. HDF5 2.x introduces a new filter plugin class, H5Z_class3_t, that adds a string-based configuration API for filters — letting users write things like H5Pappend_filter("zfp", "mode=rate, rate=3.5") instead of hand-packing cd_values arrays. As part of that, the existing H5Z_class_t::name field gains a stronger contract: in H5Z_class3_t it becomes a canonical name, a short stable identifier that the library writes into the on-disk filter-pipeline message and that tools like h5dump and h5repack display. This is the design from RFC-HDFG-2026-001.

What we need from you. We’ve proposed a canonical name for every currently registered plugin. Please look up your filter ID and **reply on the tracking issue (issue #255) with one explicit line** that names the ID and the name — so we can match the reply to a row. Please confirm 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.

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.

The proposed list, the syntactic rules, and the tracking issue:

Comment window is roughly six weeks. After that, any unconfirmed rows keep their proposed name with an unconfirmed marker; first-registered-wins still applies if anyone needs to correct it later.

If you don’t have a GitHub account, you can confirm by email to help@hdfgroup.org, and we’ll relay it to the issue.

What this does not change. Your existing plugin builds keep working unchanged with HDF5 2.x. The canonical name only becomes load-bearing when you opt your plugin into the new H5Z_class3_t class, which is a separate, opt-in code change that you control on your own schedule.

If you’ve moved on from a plugin and you’d like someone else to weigh in, please point us at the current maintainer, as we’d rather hear from the current owner than guess.

1 Like