Data-Standards Teardown
Verdict: The spec artifact is real — a maintained YAML/JSON schema with releases, docs, and a coherent scope (data-product metadata). What surrounds it is the problem. A two-founder project — now effectively one — with roughly $44 of lifetime external funding, pay-to-vote governance, an NDA'd advisory board, and Delaware series-LLC hosting marketed as "Linux Foundation standards family," whose own spec page cross-sells the founder's paid course. As a document, perhaps 60% substance. As a standard — the claim that matters for an architecture bet — closer to 90% marketing. For a data-mesh/contracts stack, Bitol (ODCS/ODPS-Standard) plus OpenLineage remains the recommendation.
ODPS is a specification for describing a "data product" — a metadata schema (name, description, pricing, SLAs, data access, quality) meant to make data products discoverable and contractable. The schema itself is genuine engineering work: an actual maintained YAML/JSON structure with versioned releases, documentation, and a defensible scope. That part is not vapor, and this teardown does not claim otherwise.
The question is not whether the document exists. It is whether ODPS is what its marketing says it is — a vendor-neutral, Linux-Foundation-associated industry standard with community governance and real adoption. On every one of those axes, the branding borrows more authority than the status carries.
The homepage brands ODPS as part of a "Linux Foundation standards family." The literal facts underneath:
| Claim | Reality | Status |
|---|---|---|
| "Linux Foundation standards family" | Assets are hosted under LF Projects, LLC — the Foundation's generic legal-hosting shell (a Delaware series LLC). A Technical Charter is dated 14 May 2024. This is hosting, not membership. | Overstated |
| An LF AI & Data Foundation project | It is not one, at any stage — checked directly against the LF AI & Data project list. A May 2025 post said it was "setting course for incubation"; as of mid-2026 that had not landed, and it still lacked the required sponsoring member org. | Not a member |
| Peer to established standards | Compare: Bitol (ODCS/ODPS-Standard) is LF AI & Data Incubation; OpenLineage is Graduated. Both have cross-vendor TSCs, staged review, and public governance rosters. ODPS has none of that structure. | Not comparable |
Read: "hosted under an LLC that the Linux Foundation operates" is true. "Linux Foundation standards family" invites the reader to hear "vetted, multi-vendor, foundation-governed" — which is precisely what it is not.
A standard derives its value from who is bound by it. That is the axis where ODPS is thinnest.
| Dimension | Finding | Status |
|---|---|---|
| Authorship | Essentially two people: Dr. Jarkko Moilanen (author of nearly all announcements, roadmap, governance posts, and the "complementary, not competing" positioning) and Jussi Niilahti. Per the org's own maintainer list Niilahti is now a past maintainer; current maintainers are Moilanen and Manfred Sorg (since Feb 2025). Effectively one-founder-driven. | Solo |
| Governance model | A TSC plus a "Strategy Group" in which the chairman "can invite full members." No independent membership roster is verifiable from the TSC repo — it names no members. | Self-published |
| Pay-to-vote | ODPI sells corporate memberships (roughly €1,000–6,000/year) that confer voting rights. The Business Advisory Group is invitation-only under NDA. Partner logos on the site are advisory-group members, not funders. | Pay-to-vote |
| External funding | The Open Collective raised $43.59 total, from three individuals — one of whom is Moilanen contributing $21 to his own collective. | ~$44 lifetime |
This is the strongest confirmation that the spec functions as a marketing asset for a personal business rather than a neutral community standard.
dataproductbusiness.com — the same domain that hosts the initiative's governance page.jarkko@vimo.fi); the org's stated location is the UAE, where Moilanen relocated in Nov 2022 to work for Abu Dhabi's Department of Government Enablement.Read: a spec whose governance page, newsletter, toolkit, and training course all route to one person's consulting business is not structurally vendor-neutral, regardless of the Apache-2.0 licence on the schema file.
Near zero, and churning.
odpv, odpr, odpg, an "AI-agent-first" SDK) — mostly 0–1 stars — and shipping fast major versions. Proliferation without adoption.In the interest of not overstating the case: the verification pass refuted two claims that surfaced during research. Moilanen's exact current job title as self-described was stale (a bio not updated after a role change), and one adoption datapoint could not be stood up. Neither changes the structural picture; both are noted so the charge stays precise.
Not fraud. The schema is legitimately hosted and Apache-2.0 licensed; there is no misconduct here. The accurate description is overstated legitimacy: a competent solo specification marketed with the vocabulary of an industry standard it has not become. The mechanism is simple — standards derive value from who is bound by them, and here nobody verifiably is.
If you are choosing a data-product standard for an architecture that has to live for years, the fitness test is not "is the schema reasonable" (it is) but "will enough other parties be bound by it that building on it compounds." On that test ODPS fails today, and its governance and funding give little reason to expect the answer to change. Bitol ODCS/ODPS-Standard plus OpenLineage — real cross-vendor TSCs, staged foundation review, public governance — remains the safer bet.