DAOnt: A Formal Ontology for EU Data Act Compliance
This paper introduces DAOnt, a formal ontology that integrates LKIF-Core, ODRL, and DPV to machine-readably represent the EU Data Act's normative structure, enabling automated compliance checking for specific B2C, B2B, and B2G scenarios through SPARQL queries.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine the EU Data Act as a massive, complex rulebook for a new global game called "Data Sharing." This rulebook, which starts being enforced in September 2025, tells companies and governments exactly how they can share, use, and sell data. It covers three main types of players:
- You and your gadgets (Business-to-Consumer).
- Companies sharing with other companies (Business-to-Business).
- Companies sharing with the Government (Business-to-Government).
The problem? The rulebook is written in dense, legal language. For a small business or a busy IT manager, reading it is like trying to understand a 50-page contract written in ancient Latin. It's easy to make a mistake, and checking if you're following the rules usually requires hiring expensive lawyers to read every single contract manually.
Enter "DAOnt" (The Data Act Ontology).
Think of DAOnt as a universal translator and a digital referee for this game. It takes that confusing legal rulebook and turns it into a language that computers can actually understand and check automatically.
Here is how the paper explains this using simple analogies:
1. The "Lego" Approach (Reusing Existing Blocks)
The authors didn't build this translator from scratch. Imagine you are building a house. Instead of making your own bricks, you use high-quality, pre-made bricks from three famous construction sets:
- LKIF-Core: The "Legal Bricks" (for understanding laws and rules).
- ODRL: The "Permission Bricks" (for saying what is allowed or forbidden).
- DPV: The "Privacy Bricks" (for handling personal data).
By snapping these existing, trusted blocks together, they built a sturdy digital structure that represents the EU Data Act. This ensures that when a computer reads the rules, it understands them the same way a human lawyer would.
2. The Three "Test Cases" (The Proof of Concept)
To prove their system works, the authors tested it on three specific, tricky rules from the Data Act. They created a digital "simulator" to see if the computer could catch rule-breakers.
Scenario A: The "Smart Watch" Rule (B2C)
- The Rule: If you own a smartwatch, the company must let you access your health data immediately and for free.
- The Test: The computer checks a contract. If the company didn't give the data when asked, the system instantly flags it: "Violation! You forgot to share the data."
- The Metaphor: It's like a vending machine that refuses to give you a soda after you put money in. The computer sees the missing soda and rings an alarm.
Scenario B: The "Secret Recipe" Rule (B2B)
- The Rule: If two companies want to share data, they can say "No" only if the data is a trade secret (like a secret recipe). But they must prove it's a secret.
- The Test: The computer looks at a refusal. If the company says "No" but doesn't provide a "Trade Secret" label, the system flags it: "Violation! You can't just say no; you need a valid reason."
- The Metaphor: It's like a bouncer at a club. If they say "No entry," they must have a valid reason (like "no shoes"). If they just say "No" without a reason, the computer knows they are breaking the rules.
Scenario C: The "Government Spy" Rule (B2G)
- The Rule: The government can ask for data during an emergency (like a pandemic), but they are strictly forbidden from using that data to build a product that competes with the company that gave it to them.
- The Test: The computer scans the government's actions. If it sees the government using the data to build a competing app, it screams: "Violation! You are using the data for the wrong purpose!"
- The Metaphor: It's like borrowing a friend's car to go to the hospital in an emergency. You are allowed to drive it, but you are strictly forbidden from using it to start a taxi service. The computer watches the odometer and the destination to make sure you aren't cheating.
3. The "Magic Search Engine" (SPARQL)
How does the computer actually check these rules? The authors use a special search language called SPARQL.
Imagine you have a giant library of all the contracts and data exchanges in the world. Instead of a human reading every book, you ask the library a specific question:
"Show me every company that owns a smartwatch but didn't give the data to the user."
The computer instantly scans the entire library and pulls up a list of the rule-breakers. This turns a task that used to take weeks of human work into a task that takes milliseconds.
Why Does This Matter?
- For Small Businesses: They don't need to hire a team of lawyers to check every contract. They can use this tool to ensure they are safe.
- For Consistency: Right now, one company might interpret a rule differently than another. DAOnt makes sure everyone plays by the exact same digital rules.
- For the Future: As the world moves toward "Data Spaces" (where data flows freely between countries and industries), we need a way to automate trust. DAOnt is the digital infrastructure that makes that trust possible.
In short: The paper presents a tool that turns the confusing, scary world of data laws into a clear, automated checklist that computers can read, ensuring that everyone plays fair in the new era of data sharing.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.