|Zet Universe Glossary|
[This is preliminary documentation and is subject to change.]
Agents represent real people, as well as artificial intelligence systems that operate within the Zet Universe platform. Artificial intelligence systems are generally represented as the installed apps/accounts.
Content is provided to the system via external data providers (apps) and is represented by a Kind. Apps connect Zet Universe to the external data sources (local and network file systems, web, microservices, etc.), enable initial data transformation and load, as well as allow (optional) source change tracking, and (optional) metadata synchronization. App may register own Processors (see below), Kinds’ and Relationships’ definitions. Support is provided (minimally) for file-based documents (local and Dropbox-based), images, audio, video, people (Dropbox users), web (HTML).
Additional kinds, apps and processors can be added to the system.
Entity is the "atom" of information within Zet Universe. It incapsulates information about any kind of the everyday things like people, documents, e-mail, and so on. A special property, Kind, is used to characterize the semantic meaning of the particular Entity.
Entities are extracted and/or derived from the provided data sources or emergent from collections of entities and properties.
Knowledge within the Zet Universe is represented as entities on storage level and kinds on ontology level.
Kinds are flexible representations of both every day and enterprise-specific things: people, organizations, places, events, media, etc.
Models are Agent- or App-generated containers designed to be a place for data integration, organization, and analysis. For the end users, Models can be seen as the workspaces for their projects, while Apps use Models to obtain and synchronize external data, to make it available for the end users. Models contain collections of instances of Kinds.
Content within Kinds is processed via the means of the so-called Semantic Pipeline (see below), which provides a topic subscription service, and both the platform and plugins can subscribe to this service, specify a topic (or topics) they are interested in, process incoming instances of Kinds, and (optionally) publish updated instances of Kinds back to the Semantic Pipeline. There are two kinds of subscribers – lightweight (that can process data in an almost synchronous way) and heavy (that usually spend significant time to analyze and process data). Both kinds of subscribers are usually defined in the form of Processors, that are packaged either as part of Apps, or independently.
Derived, extracted, or user-supplied data about kinds and/or their underlying data sources are provided in two forms: common properties (available for all Kinds), and dynamic properties.
Relationships represent connections between instances of Kinds, and, like Properties, they are derived, extracted, or user-supplied. Relationships are stored with the instances of Kinds as references to other instances.