Ontotext Platform 3.2 Offers Better System Integration and Control Over Knowledge Graph Access and Integrity

The new version of the Platform features data quality assurance via SHACL validation upon transaction commit, bi-directional GraphQL Federation, Attribute-based Access Control and multi-language support

Sofia/Bulgaria Thursday, October 1, 2020

One of the most important new features of Ontotext Platform 3.2 is the ability to improve data quality by discovering inconsistencies and other anomalies within data during create, update and delete operations. Data quality constraints enforce rules that ensure the integrity of knowledge graphs (KGs) respecting information governance principles. Business analysts (BAs) and subject matter experts (SMEs) can constrain data mutation operations so that they match validation rules, including cardinality checks, pattern checks, value range constraints, min/max length, existence validations and many others. The Platform uses declarative configuration to automatically generate SHACL shapes, binding them to the database to enforce validation. For further information, see Ontotext Platform Validation or read more about the underlying mechanisms in GraphDB’s documentation.

Now, version 3.2 also includes bi-directional federation, making it simple to provide a single unified data graph across diverse backing data sources. It allows one to extend external GraphQL objects and properties with data contained within the Platform’s declarative GraphQL service, augmenting the Platform’s existing support for external service extension upon internally managed data. To set up the federation service, please refer to the Ontotext Platform GraphQL Federation documentation and the Ontotext Platform GraphQL Federation Tutorial.

In addition to the Platform’s declarative Role-Based Access Control features introduced within version 3.1, now we extend the flexibility of the security model by presenting Attribute-Based Access Control (ABAC). ABAC provides an additional security dimension, allowing experts to define access control policies using specific attributes from the KGs data and achieving regulatory compliance. As a result, a particular role can have access only to semantic object instances matching the defined rules in its policy. For further information, see the Ontotext Platform Authentication and Authorization documentation and Ontotext Platform RBAC Filter configuration.

Another new feature is the full support of language tags. Language tags enable multilingual KGs, allowing consumers to choose a  language preference at runtime. When configured, on a property or model level, users will be able to read, write, validate, filter, and order objects by language value. For further information, see the Language Configurations and Tutorial documentation.

Last but not least Ontotext Platform 3.2 has many improvements, the most significant of which are applying GraphQL missing values specification, Helm chart for GraphDB cluster and model generation.

Get ready to take advantage of all new Ontotext Platform 3.2 features!

New call-to-action


For more information, contact Doug Kimball, Chief Marketing Officer at Ontotext