Aerospace.Wikibase: Towards a Knowledge Infrastructure for Aerospace Engineering

This paper introduces Aerospace.Wikibase, a collaborative knowledge infrastructure built on Wikibase that addresses fragmentation in aerospace engineering by providing an open, extensible platform for sharing and curating over 700 terms related to processes, software, and data.

Tim Wittenborg, Ildar Baimuratov, Jamal Eldemashki

Published 2026-03-06
📖 4 min read☕ Coffee break read

Imagine the world of aerospace engineering (building planes, rockets, and satellites) as a massive, high-stakes construction site. Right now, this site is full of brilliant engineers, but they are all working in separate, locked sheds.

One team has a shed full of blueprints for engines. Another has a shed full of software code for navigation. A third has a shed full of data on how materials react to heat. They know they should be sharing, but their sheds are built on different foundations, use different languages, and are often locked up tight because of security or project deadlines. The result? Everyone is reinventing the wheel, wasting time, and missing out on the big picture.

This paper introduces a solution called Aerospace.Wikibase. Think of it as building a giant, public, digital "Central Library" specifically for aerospace engineers.

Here is how it works, broken down into simple concepts:

1. The Problem: The "Tower of Babel"

Currently, aerospace knowledge is scattered. It's like if every chef in the world wrote their own recipe book using their own secret code, and no one could read anyone else's book. Even worse, once a specific project (like building a specific rocket) is finished, that knowledge often gets locked away in a filing cabinet or a private server, never to be seen again.

2. The Solution: A Universal Lego Set

The researchers decided to build a platform based on Wikibase (the same technology that powers Wikidata, the database behind Wikipedia).

  • The Analogy: Imagine a giant box of Lego bricks. In the past, every engineer had their own unique, incompatible bricks. This new platform provides a standardized set of Lego bricks (terms for processes, software, and data) that everyone agrees to use.
  • The Result: Now, an engineer in Germany can snap a "rocket engine" brick onto a "fuel system" brick, and an engineer in the US can snap a "flight simulation" brick onto the same engine. They are building on the same foundation, even if they are in different rooms.

3. How They Built It: The "Data Vacuum Cleaner"

You can't just build a library and hope people fill it. The team didn't wait; they went out and gathered the first batch of books themselves.

  • They took a massive list of 700+ technical terms from a recent scientific review (like a "best of" list of aerospace concepts).
  • They used a computer program (a bot) to vacuum this data up and organize it into their new library.
  • They created a strict "filing system" (a data model) so that every piece of information knows exactly where it belongs and how it connects to other pieces.

4. The Safety Feature: "The Glass Wall"

One of the biggest fears in aerospace is: "If I put my secret project data here, will my competitors steal it?"

The authors designed this system with a clever safety feature. Think of it as a Glass Wall.

  • The "Universal Library" (Aerospace.Wikibase) is public and open. It holds the concepts (e.g., "What is a jet engine?").
  • Your specific project (e.g., "The secret fuel mix for Rocket X") stays in your private shed.
  • However, your private shed can have a window looking out at the public library. You can link your secret project to the public concepts without giving away your secrets. You get the benefit of the shared knowledge without losing your competitive edge.

5. Why This Matters

The paper argues that the aerospace industry is too complex for one company or one country to solve alone anymore. We need to stop working in silos.

  • Before: Engineers waste years rediscovering things others already figured out.
  • After: Engineers can stand on the shoulders of giants, using a shared, permanent, and open infrastructure that doesn't disappear when a project ends.

The Bottom Line

The researchers have built a permanent, open-source "Wikipedia for Aerospace Engineering." It's not just a website; it's a new way of thinking. It allows engineers to share the rules of the game without giving away their winning moves.

They hope that big organizations (like NASA or major aerospace companies) will eventually adopt this library, turning it into the central nervous system for how the world builds the future of flight. Until then, the library is open, the doors are unlocked, and the first 700+ books are already on the shelves, waiting for the rest of the world to add their own.