When Data Spaces Comes for Test Data, Standardization Amplifies

Ralf Noerenberg HighQSoft
08. June 2026 Dr. Ralf Nörenberg
8. June 2026 - Dr. Ralf Nörenberg

A new perspective from HighQSoft on data spaces and ASAM ODS

HighQSoft has published a new short story, When Data Spaces Come for Test Data, Standardization Connects. The piece argues that data spaces strengthen, rather than weaken, the case for ASAM ODS. A file-based stack works as long as the system stays local. The moment data crosses an organizational boundary, the standard is what makes that boundary tractable.

The article belongs to HighQSoft's standardization series, which dedicates one short story to each of the five test data management pillars. This installment is the Connected pillar, where the ASAM ODS Standard reaches across organizations into data spaces.

Why the connector is not enough

A data space connector solves transport, not meaning. A file dropped into a connector arrives at the consumer as a blob to be re-interpreted from filenames and folders. The Eclipse Dataspace Connector and its Tractus-X derivative move bytes between provider and consumer; they do not move the contents of those bytes. Without a shared schema, the consumer rebuilds the producer's interpretation by hand, every time, which is exactly the delegated re-import that standardized test data management was meant to avoid.

The story sets out five properties that decide whether a cross-organization exchange becomes useful infrastructure or stays a transport layer with a contract attached. These include schema-to-schema exchange, sub-file asset granularity, calculated results as practical assets, contracted reports and exports, and catalogs with lineage that make exchange auditable and reusable. The closest production parallel today is the Catena-X Product Carbon Footprint exchange, where values flow and aggregate across the supply chain only because a rulebook standardizes how each participant interprets each value.

Two connection points HighQSoft already operates

The article shows two clean ways to connect a HighQSoft installation to a data space, both part of the production architecture today. Janus, the federation layer, treats a connector as one more handler and presents incoming assets as a unified ASAM ODS view for the consumer. ASAMCommander's internal NXServices, orchestrated by Merlin, publish measurements, KPIs, results, and reports to the data space as a provider. Both directions have been demonstrated with real connectors in the GAIA-X 4 KI and RepliCar research projects, including cross-cloud exchanges between separate clouds.

Read it

*#ASAM #ODS #TestData #DataSpaces #GAIAX #DataSovereignty #HighQSoft*

data spaces and asam ods

HighQSoft GmbH

Black-und-Decker-Straße 17b
D-65510 Idstein