Skip to main content
Release: CX-Neptune (Preview)

Changelog

All notable changes to CX-0146 will be documented in this file.

[3.0.0] - 2026-09-16​

Fixed​

  • changed purl context from httpsHTTP HTTP is an application-layer protocol for transmitting hypermedia documents (such as HTML). It was designed for communication between web browsers and web servers, but can also be used for other purposes. to httpHTTP HTTP is an application-layer protocol for transmitting hypermedia documents (such as HTML). It was designed for communication between web browsers and web servers, but can also be used for other purposes. to reflect correct scheme in example of 4.1.3 DATA ASSET STRUCTURE.
  • ensure that the scheme and examples don't use a property demandAndCapacityNotification in object content. A mistake has been made in version 2.0.0 removing it in the examples but not in the schema. As the schema is more leading, this is considered a major instead of a bugfix change.
  • Added Chapter 4.1.3.1 for backward compatibility and keep both open apiAPI An API is a way for two or more computer programs to communicate with each other. schemes

Changed​

  • bumped versions of referenced standards with cross-checks

[2.0.0] - 2025-06-24​

Added​

  • added field resolvingMeasureDescription to notification.
  • added rules for payload validation for material numbers in a material.

Changed​

Reduced normative language by:

  • introducing (non-) normativeness on higher levels for subsections.
  • referring to other standardized artifacts (aspect modelsAspect Model A formal, machine-readable semantic description (expressed with RDF/Turtle) of data accessible from an aspect. Note 1: An Aspect Model must adhere to the Semantic Aspect Meta Model (SAMM) and be compliant with its validity rules. Note 2: Aspect Models are logical data models that can be used to detail a conceptual model to describe the semantics of runtime data related to a concept; elements of an Aspect Model can/should refer to terms of a standardized Business Glossary (if existing)., standards, etc.).

Message Structure:

  • renamed sourceNotificationId to sourceDisruptionId to signalize that one disruption leads to multiple notifications into multiple directions.
  • Moved material information to a list materials.
    • material numbers follow the industry core characterstic.

Compliance to CX-0151 Industry Core Basics (harmonize notification standards):

  • provide an Open APIAPI An API is a way for two or more computer programs to communicate with each other. definition.
  • update of messageHeader.context to include an operation.

Process Representation:

  • Add information on how to set fields in different scenarios (tables 11 - 14).
  • Replace figures 3 and 4 by one.

Further:

  • inserted validations 5, 6, 7 in section 4.1.5

[1.0.0] - 2024-04-15​

Added​

  • initial version

Copyright © 2026 Catena-X Automotive Network e.V. All rights reserved. For more information, please see Catena-X Copyright Notice.