Request to add real5-omnidocbench framework and Benchmark allow list entry

PaddlePaddle requests adding the Real5-OmniDocBench framework and benchmark entry to Hugging Face's Hub Benchmark evaluation system. The benchmark evaluates document parsing robustness under five real-world acquisition scenarios: Scanning, Warping, Screen-Photography, Illumination, and Skew. Existing framework identifiers do not directly identify this benchmark, prompting the need for a new enum entry.

Hi Hugging Face team, We would like to add a new Hub Benchmark evaluation framework and register our dataset as a native Hub Benchmark. Requested framework identifier: real5-omnidocbench Dataset: Reason: Real5-OmniDocBench evaluates document parsing robustness under five real-world acquisition scenarios: Scanning, Warping, Screen-Photography, Illumination, and Skew. Existing framework identifiers such as olmocr-bench, mdpbench, and parsebench do not identify this benchmark directly. Current status: Proposed enum entry: “real5-omnidocbench”: { name: “real5-omnidocbench”, description: “Real5-OmniDocBench is a real-world document parsing robustness benchmark covering five physical acquisition scenarios: Scanning, Warping, Screen-Photography, Illumination, and Skew.”, url: " PaddlePaddle/Real5-OmniDocBench · Datasets at Hugging Face https://huggingface.co/datasets/PaddlePaddle/Real5-OmniDocBench ", } Could you help us with: Thanks.