Request Real5 benchmark framework

eval.yaml

@@ -3,7 +3,7 @@ description: >
   Real5-OmniDocBench is a real-world document parsing robustness benchmark
   covering five physical acquisition scenarios: Scanning, Warping,
   Screen-Photography, Illumination, and Skew.
-evaluation_framework: olmocr-bench
+evaluation_framework: real5-omnidocbench
 
 tasks:
   - id: overall

hf_eval_results/HF_UPSTREAM_REQUEST.md

@@ -0,0 +1,92 @@
+# Requesting `real5-omnidocbench` Support Upstream
+
+To make the Hugging Face native Benchmark UI recognize this benchmark, Hugging Face needs to add a new evaluation framework identifier:
+
+```text
+real5-omnidocbench
+```
+
+The relevant upstream enum is currently in:
+
+```text
+https://github.com/huggingface/huggingface.js/blob/main/packages/tasks/src/eval.ts
+```
+
+## Proposed Enum Entry
+
+```ts
+"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: "https://huggingface.co/datasets/PaddlePaddle/Real5-OmniDocBench",
+},
+```
+
+## Dataset Configuration
+
+The dataset repository already contains a root `eval.yaml` using the requested framework:
+
+```yaml
+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.
+evaluation_framework: real5-omnidocbench
+
+tasks:
+  - id: overall
+    config: default
+    split: test
+  - id: scanning
+    config: default
+    split: test
+  - id: warping
+    config: default
+    split: test
+  - id: screen_photography
+    config: default
+    split: test
+  - id: illumination
+    config: default
+    split: test
+  - id: skew
+    config: default
+    split: test
+```
+
+## Message Template
+
+```text
+Hi Hugging Face team,
+
+We would like to add a new Hub Benchmark evaluation framework:
+
+real5-omnidocbench
+
+Dataset:
+https://huggingface.co/datasets/PaddlePaddle/Real5-OmniDocBench
+
+Paper:
+https://arxiv.org/abs/2603.04205
+
+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.
+
+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: "https://huggingface.co/datasets/PaddlePaddle/Real5-OmniDocBench",
+}
+
+The dataset root eval.yaml already uses:
+evaluation_framework: real5-omnidocbench
+
+Could you add this framework identifier to the supported enum and add the dataset to the Benchmark allow-list so the native Benchmark Leaderboard UI can appear?
+
+Thanks.
+```

hf_eval_results/README.md

@@ -14,9 +14,17 @@ Hugging Face Evaluation Results require:
 3. The benchmark dataset to be accepted by the beta allow-list.
 4. Model repos to submit `.eval_results/*.yaml` files that reference this dataset and task IDs.
 
-As of July 11, 2026, Hugging Face documents this feature as work in progress and benchmark registration as beta / allow-listed. The supported framework enum currently includes document-related frameworks such as `olmocr-bench`, `mdpbench`, and `parsebench`, but not a dedicated `real5-omnidocbench` or `omnidocbench` framework.
+As of July 11, 2026, Hugging Face documents this feature as work in progress and benchmark registration as beta / allow-listed. The supported framework enum currently includes document-related frameworks such as `olmocr-bench`, `mdpbench`, and `parsebench`, but not `real5-omnidocbench`.
 
-For that reason, `eval.yaml.candidate` is intentionally not placed at the repository root yet. Move or copy it to `eval.yaml` only after Hugging Face confirms the framework choice and allow-list registration.
+The intended framework identifier for this benchmark is:
+
+```yaml
+evaluation_framework: real5-omnidocbench
+```
+
+Hugging Face must add this identifier to its supported evaluation framework enum before the Hub can fully recognize the dataset as a native benchmark.
+
+For that reason, the repository includes the target framework name explicitly so the upstream request is unambiguous. If the Hub rejects or ignores the framework before upstream support lands, keep the file as the desired target state and reference it in the Hugging Face support request.
 
 ## Dataset-Side Candidate
 

hf_eval_results/eval.yaml.candidate

@@ -3,7 +3,7 @@ description: >
   Real5-OmniDocBench is a real-world document parsing robustness benchmark
   covering five physical acquisition scenarios: Scanning, Warping,
   Screen-Photography, Illumination, and Skew.
-evaluation_framework: olmocr-bench
+evaluation_framework: real5-omnidocbench
 
 tasks:
   - id: overall