Roovet Data

Roovet Data

Type	Knowledge graph; structured knowledge base
Available at	data.roovet.com
Owner	Roovet
Language	Multilingual
Software	MediaWiki; Wikibase
Entity types	Items, properties, EntitySchemas
Identifiers	Q-identifiers, P-identifiers, E-identifiers
Data access	Web interface, MediaWiki API, JSON, RDF, Turtle
Registration	Not required for reading
Current status	Active

Roovet Data is the structured knowledge graph and reusable-data repository operated by Roovet. Available at data.roovet.com, it stores referenced facts about people, organizations, creative works, places, services, identifiers, and the fictional Tribal Universe. The repository is designed to give subjects across the Roovet network a consistent machine-readable identity rather than requiring the same facts to be entered independently on every service.

Roovet Data uses the Wikibase data model. Subjects are represented by items with Q-identifiers, relationships and attributes are defined by properties with P-identifiers, and validation structures can be stored as EntitySchemas with E-identifiers. Records can contain labels, descriptions, aliases, typed statements, qualifiers, references, external identifiers, and sitelinks connecting an entity to its corresponding page elsewhere in the Roovet network.

The service is separate from Roovet Articles. Roovet Articles presents knowledge as prose written for readers, while Roovet Data records individual claims in a structured form that software can retrieve and reuse. An Articles page and a Data item may describe the same subject, but each performs a different role.

Purpose

Roovet Data serves as a central identity and fact layer for the wider Roovet platform. Its main page describes the repository as “the knowledge graph behind Roovet” and identifies its scope as people, organizations, creative works, places, services, and the expanding Tribal Universe.

The repository is intended to:

• assign stable identifiers to notable entities;
• connect people, companies, books, series, locations, and fictional subjects;
• store facts in defined data types rather than unstructured text;
• attach references and retrieval dates to individual claims;
• connect entities to canonical Roovet Articles, Roovet Books, and profile pages;
• make records available to browsers, search systems, metadata generators, and other software;
• reduce conflicting information between different parts of the Roovet network; and
• support multilingual labels, descriptions, and aliases.

Its editing guidance emphasizes searching before creating a record, avoiding duplicate entities, using neutral descriptions, and adding sources to statements.

History

Public page histories show that components of the Roovet Data installation were present by September 2022. The early installation used MediaWiki and Wikibase conventions derived from the broader Wikidata software ecosystem.

The repository underwent substantial development in 2026. Roovet-specific properties were introduced for Articles pages, public profiles, publishing records, book identifiers, company relationships, and other network data. The main page was redesigned in July 2026 as a dedicated knowledge-graph portal, with direct paths for searching the graph, creating items and properties, setting sitelinks, and browsing established records.

The 2026 structure also expanded the graph surrounding Tony James Nelson II, Roovet, Roovet Books, Tribal Bloody Beginnings, and the Tribal Universe. These records demonstrate how the repository can connect a creator to companies, occupations, books, series, fictional settings, publication dates, and external identifiers without placing every relationship in a single article.

Data model

Items

An item represents a distinct person, organization, creative work, place, event, concept, or fictional subject. Each item receives a Q-identifier that remains stable even when its English label or aliases change.

Examples featured by Roovet Data include:

Identifier	Item	Entity type or role
Q9	Tony James Nelson II	Person, founder, author, and creator
Q29	Roovet	Organization
Q138	Tribal Universe	Fictional universe
Q140	Tribal Bloody Beginnings	Novel and creative work
Q142	Children of the Dark Alpha	Book series

Each item can include a label, a short disambiguating description, alternative names, and statements describing the entity.

Properties

A property defines the meaning and expected data type of a relationship or value. Properties use P-identifiers and can link one item to another or store values such as dates, URLs, quantities, coordinates, text, and external identifiers.

Roovet-specific and general-purpose examples include:

Property	Label	Use
P9	Roovet Articles page	Stores the canonical Articles URL for an entity
P12	Founder	Connects an organization to its founder
P31	Instance of	Identifies the class or type of an entity
P50	Author	Connects a written work to its author
P67	Reference URL	Records the source URL supporting a statement
P70	Retrieved	Records when an online reference was checked
P71	Publication date	Stores the publication date of a creative work
P72	ISBN-13	Stores a book's ISBN-13 identifier
P74	Part of the series	Connects a work to its series

The repository's property directory can be filtered by data type. Supported types include items, properties, URLs, external identifiers, strings, monolingual text, quantities, points in time, geographic coordinates, Commons media, geographic shapes, tabular data, and EntitySchemas.

Statements and references

A statement combines a property with a value. For example, the item for Tribal Bloody Beginnings uses properties to record its author, publisher, publication date, page count, ISBN, formats, series, and Roovet Book ID. References attached to those statements identify where the information came from and when it was retrieved.

Statements can also carry qualifiers that narrow or contextualize a value. This permits the graph to distinguish, for example, between a current position and a former position, or between a work's original publication date and a later edition.

Sitelinks

Sitelinks connect a Data item to the canonical page about the same subject on another configured Roovet site. Property P9 and the related Roovet Articles title property provide explicit Articles connections, while the sitelink interface creates a direct association at the entity level.

On Roovet Articles, these connections allow an article to identify its corresponding structured record. On Roovet Data, they provide a path back to the longer reader-facing article.

EntitySchemas and constraints

Roovet Data supports EntitySchemas written in Shape Expressions syntax. An EntitySchema can describe the properties expected for a class of records and can be used to validate whether an entity follows that structure.

Property constraints provide a second quality-control layer. They can indicate requirements such as a single value, a particular value type, a required format, or an allowed range. Constraint reports warn editors about incompatible or incomplete statements; they do not automatically replace editorial review or prevent every nonconforming value from being saved.

Relationship with Roovet Articles

Roovet Data and Roovet Articles are complementary parts of the same information system.

Feature	Roovet Articles	Roovet Data
Primary format	Encyclopedic prose	Structured statements
Main identifier	Article title and URL	Q-identifier
Relationships	Explained in sentences and links	Stored through typed properties
Sources	Article-level inline citations	References attached to individual statements
Intended reader	Primarily people	People and software
Typical use	Biography, history, context, analysis	Infobox values, identifiers, entity relationships, metadata

An article can change its title without requiring the underlying Q-identifier to change. Conversely, an item's structured statements can be updated and reused without rewriting an article's narrative. This separation helps preserve stable identity while allowing the prose and the structured record to evolve independently.

Technical architecture

Roovet Data runs on MediaWiki with Wikibase Repository, the software component that allows a MediaWiki installation to operate as a structured-data repository.

As of July 29, 2026, the public software report identified:

• MediaWiki 1.45.3;
• Wikibase Repository;
• EntitySchema;
• PropertySuggester;
• WikibaseQualityConstraints;
• VisualEditor;
• RoovetDataEntitySEO 2.3.2; and
• RoovetDataSeo 1.0.2.

The two Roovet-developed extensions add entity presentation, crawlable browse directories, canonical URLs, indexing controls, Open Graph metadata, and structured-data output for entity pages.

Data access

Entity records are available through ordinary HTML pages and machine-readable interfaces. The site's entry points include the MediaWiki Action API and REST API, while Wikibase adds modules for retrieving and editing entity data.

The `Special:EntityData` interface can serialize an entity in multiple formats. For example:

• Q140.json provides JSON;
• Q140.rdf provides RDF/XML; and
• Q140.ttl provides RDF/Turtle.

The JSON representation preserves entity identifiers, labels, descriptions, aliases, claims, references, qualifiers, and sitelinks in a format designed for programmatic use.

Coverage

The graph covers both real-world and fictional subjects. Its highlighted records include:

• people and public profiles;
• companies and organizations;
• books, albums, comics, and other creative works;
• authors, publishers, and series;
• places and service areas;
• external identifiers and registration numbers;
• the Tribal Universe, its characters, families, locations, and terminology; and
• relationships among Roovet services.

This combined scope allows a single graph to represent both a real author and the fictional universe, books, characters, and publishing entities connected to that author. Fictional subjects remain distinguishable through their entity classes and descriptions.

Size and activity

In July 2026, Roovet Data reported 891 total knowledge pages and 1,519 recorded revisions. The public statistics page also listed three registered active users, including one bot account.

Because Wikibase items and properties use specialized content models and namespaces, MediaWiki's standard “content pages” count does not represent the complete number of structured entities. The total-page count and the item/property directories provide a broader view of the repository's actual contents.

Editorial model

Roovet Data separates a claim's value from the evidence supporting it. Contributors can attach reference URLs, retrieval dates, and other source details directly to individual statements. The repository also preserves revision histories, allowing changes to labels, descriptions, properties, and claims to be reviewed over time.

The site's stated workflow is:

1. search for an existing entity;
2. create an item only when the subject is missing;
3. use an existing property whenever possible;
4. define a new property only when the relationship is not already represented;
5. connect the item to the wider graph; and
6. add reliable references and neutral descriptions.

This model is intended to limit duplicate records and make structured claims easier to verify and reuse.

See also

• Roovet
• Roovet Articles
• Roovet Books
• Knowledge graph
• Linked data
• Semantic Web
• Wikibase
• MediaWiki

External links

• Official website
• Search Roovet Data
• Browse properties
• Recent changes
• Public statistics
• MediaWiki API