This repository was archived by the owner on Nov 21, 2026. It is now read-only.
Repository navigation
Benchmarks: graph tables carry LDBC's "not an LDBC Benchmark Result" wording - #493
Merged
Merged
Conversation
…wording and their deviations, held by page_check Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Every generated table built from LDBC data (
l2graph OLTP,l2olapgraph OLAP, andrestartfor its graph rows) now opens with two registered sentences inexport_web.py:LDBC_NOTICE: "These are not LDBC Benchmark Results." plus the CC BY 4.0 credit to the Linked Data Benchmark Council, "we ran it ourselves, it was not audited by an LDBC-approved auditor, and LDBC has not endorsed it".page_check._check_ldbc_noticeis a new gate: a table inLDBC_DERIVED_TABLES(or whose dataset or size label names LDBC) that lacks the exact disclaimer or the deviations sentence fails the publish.PAGE-SPEC.mdsection 7 and its gate table describe the rule. Because the sentences are registered inOCT_PROSE, the existing condition gate also checks them for unpinned numbers (CC BY 4.0is added toCONDITION_EXEMPT).Why
LDBC's fair-use policy (https://ldbcouncil.org/benchmarks/fair-use-policies) lets only a result audited by an LDBC-approved auditor be called an LDBC Benchmark Result. Unaudited or derived work must say it is not one (for example "These are not LDBC Benchmark Results"), give CC BY 4.0 attribution, and say briefly how it differs from the standard. Implying LDBC endorsement is treated as trademark infringement. The positioning report found that none of this wording existed anywhere under
benchmarks/, and the late-November paper and the DBBench page both show these tables.Checked locally
uv run --no-project --with numpy --with pandas --with pytest python -m pytestontest_page_check_2611.py(three new tests: wording present on the fixture payload and free of unpinned numbers, removed wording caught, reworded disclaimer caught),test_export_client_twin.py,test_gen_engines_doc.py,test_publish_2611_e2e.py,test_refresh_web_page_2611.pyandtest_stage_generator_2611.py: all pass.Not covered
The humemai/dbbench repo (docs only; no LDBC mention) and
humem.ai/src/lib/dbbench/lanes.ts(no LDBC mention) are unchanged. Figures and the paper PDF generators were not touched; they need the same sentence in their captions when they are built from these tables.🤖 Generated with Claude Code