Next Release

The following changes have occurred to the open metadata types.

• New entity type called DataQualityRule, a subtype of GovernanceRule, describes a check on the quality of data in the terms used by data contract standards (quality dimension, check type, metric, severity, business impact, schedule, comparison operator and threshold values).
• DataField has three new attributes: allowsDuplicateValues, isPartitionKey and partitionKeyPosition. They record constraints and organization intent from a data specification, ready for when the implementing schema is catalogued.
• The PrimaryKey classification may now be attached to a DataField as well as a RelationalColumn.
• End 1 of the ContactThrough relationship is now Referenceable rather than ActorProfile, so that, for example, digital products and data sharing agreements can record their support channels.

The data file, media file, software file and folder templates in the Files Content Pack declare a deployedImplementationType placeholder. They now substitute it into the asset they create, where previously the template's own type (for example YAML File) was always used. Callers of these templates should supply the placeholder; the file cataloguers already do.

Egeria can now exchange data contracts and data product descriptors with the teams that keep them in git, using the Bitol open standards. See digital product management for the mapping to open metadata.

• The Open Integration Framework (OIF) provides beans for both document kinds, a YAML/JSON formatter, mappers and generators between the documents and open metadata, and a listener mechanism in the integration daemon that mirrors its Open Lineage support. Documents can also be published to an integration daemon through its REST API.
• The new Bitol Content Pack supplies six integration connectors: receivers for file directories (such as a git checkout) and Apache Kafka topics, cataloguers that turn ODCS documents into data sharing agreements and ODPS documents into digital products, a publisher that generates the documents from the digital products and agreements in open metadata, and a file store that writes them out ready to commit.
• The Product Manager API can publish documents to an integration daemon, import them directly, and generate the ODPS document for a digital product or the ODCS document for a data sharing agreement.
• The Solution Architect API now supports the definition and retrieval of solution ports, which are used to represent the input and output ports of a data product.
• Sample ODPS and ODCS documents for the Coco Pharmaceuticals clinical trial are included with the sample data, and a new functional verification test suite (bitol-fvt) exercises the whole chain.
• The document files themselves are catalogued as data assets from the YAML and JSON file templates, with deployed implementation types that identify ODCS and ODPS documents in either format, and linked to the agreement or product catalogued from them as a Bitol Document resource.
• The vocabularies of the standards (quality check types, metrics, dimensions, severities and comparison operators, logical types, semantic types, server types, support tools and scopes, authoritative definition types, management port content and types, and data product types) are registered as valid metadata values by the Core Content Pack for the properties the Bitol cataloguers store them in.
• The support follows ODCS v3.2.0 and ODPS v1.1.0 (released 8 September 2026): enumerations, maps, vectors, synonyms, semantic types (measures and dimensions), the deprecated flag, the AI context block, vendor attribution on custom properties, SLA extensions, relationship ids, variable references, the physical encoding of servers and the SAP HANA, Apache Iceberg, Exasol, Teradata and Actian server types.

Multi Language API supports the attachments of translations for different languages to metadata instances.

DevOps Pipeline API supports the maintenance of infrastructure metadata when new software is deployed to production.

Privacy Officer API supports the maintenance of data processing descriptions associated with data processing purposes using in data privacy and data sharing agreements.