CargoAdmin, Bureaucrats, Moderators (CommentStreams), fileuploaders, Interface administrators, newuser, Push subscription managers, Suppressors, Administrators
5,287
edits
| Line 12: | Line 12: | ||
== Knowledge graph == | == Knowledge graph == | ||
{{Nutshell|In short: OpenGov Encyclopedia combines Wikipedia-style readability with database-like structure. Humans get helpful narrative pages that point to official sources; machines/AI get a clean, connected, verifiable graph of federal entities and relationships — all without duplicating agency content.}} | |||
OpenGov Encyclopedia uses MediaWiki (the same software that powers Wikipedia) combined with the Cargo extension to function as a lightweight knowledge graph. This setup provides both human-readable pages (like Wikipedia articles) and machine-readable, structured, queryable data — perfect for serving as a "truth layer" that feeds clean information to agency AI systems while helping citizens understand federal structures. | OpenGov Encyclopedia uses MediaWiki (the same software that powers Wikipedia) combined with the Cargo extension to function as a lightweight knowledge graph. This setup provides both human-readable pages (like Wikipedia articles) and machine-readable, structured, queryable data — perfect for serving as a "truth layer" that feeds clean information to agency AI systems while helping citizens understand federal structures. | ||
Here's a simple, step-by-step explanation for someone not familiar with these tools: | Here's a simple, step-by-step explanation for someone not familiar with these tools: | ||
1. What is a Knowledge Graph? (Quick Basics) | === 1. What is a Knowledge Graph? (Quick Basics) === | ||
A knowledge graph is like a smart map of information: | A knowledge graph is like a smart map of information: | ||
| Line 28: | Line 28: | ||
Traditional databases or spreadsheets can store facts, but knowledge graphs excel at revealing connections and enabling complex, relationship-based searches. | Traditional databases or spreadsheets can store facts, but knowledge graphs excel at revealing connections and enabling complex, relationship-based searches. | ||
2. How MediaWiki + Cargo Creates This | === 2. How MediaWiki + Cargo Creates This === | ||
* MediaWiki handles the "Wikipedia-like" part: | * MediaWiki handles the "Wikipedia-like" part: | ||
| Line 66: | Line 65: | ||
**The system doesn't need fancy triple-store tech (like RDF/OWL in heavier graphs); it uses simple relational tables but supports joins, list fields, and hierarchy traversal to mimic graph behavior. | **The system doesn't need fancy triple-store tech (like RDF/OWL in heavier graphs); it uses simple relational tables but supports joins, list fields, and hierarchy traversal to mimic graph behavior. | ||
3. Querying the Graph — The Real Power | === 3. Querying the Graph — The Real Power === | ||
Cargo lets anyone (humans or machines via API/JSON exports) run queries across the data. These queries reveal connections automatically. | Cargo lets anyone (humans or machines via API/JSON exports) run queries across the data. These queries reveal connections automatically. | ||
| Line 102: | Line 100: | ||
* Inline dynamic content (updates whenever source data changes) | * Inline dynamic content (updates whenever source data changes) | ||
4. Why This Counts as a Knowledge Graph (Even If Lightweight) | === 4. Why This Counts as a Knowledge Graph (Even If Lightweight) === | ||
* It has entities (pages/nodes) and typed relationships (via template fields and links). | * It has entities (pages/nodes) and typed relationships (via template fields and links). | ||
| Line 113: | Line 110: | ||
* Unlike heavier graphs (e.g., Neo4j or RDF stores used in some federal pilots), it's simple, open-source, low-maintenance, and integrated with readable wiki pages. | * Unlike heavier graphs (e.g., Neo4j or RDF stores used in some federal pilots), it's simple, open-source, low-maintenance, and integrated with readable wiki pages. | ||
== Safeguards == | == Safeguards == | ||
edits