# RFC-HDFG-2026-001: String-Based Filter Configuration API — Request for Community Feedback

**URL:** <https://forum.hdfgroup.org/t/rfc-hdfg-2026-001-string-based-filter-configuration-api-request-for-community-feedback/13776>\
**Category:** HDF5 Library\
**Created:** [May 1, 2026, 8:33pm UTC](https://forum.hdfgroup.org/t/rfc-hdfg-2026-001-string-based-filter-configuration-api-request-for-community-feedback/13776 "2026-05-01T20:33:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![koziol](https://forum.hdfgroup.org/letter_avatar_proxy/v4/letter/k/4da419/32.png) [@koziol](https://forum.hdfgroup.org/u/koziol)\
**Post date:** [May 1, 2026, 10:46pm UTC](https://forum.hdfgroup.org/t/rfc-hdfg-2026-001-string-based-filter-configuration-api-request-for-community-feedback/13776/2 "2026-05-01T22:46:38Z")

</div>

I haven’t read the entire RFC yet, but I’m also working on extending the H5Z\_class\_t struct for the Accelerator-native I/O pipeline work that I’m preparing to upstream. Let’s coordinate so that both of our updates to the H5Z\_class\_t get into the same release and we don’t end up with H5Z\_class4\_t in the release immediately after H5Z\_class3\_t is introduced.

---

_[View the full topic](https://forum.hdfgroup.org/t/rfc-hdfg-2026-001-string-based-filter-configuration-api-request-for-community-feedback/13776)._