{"id":40343,"date":"2026-08-20T20:06:25","date_gmt":"2026-08-20T18:06:25","guid":{"rendered":"https:\/\/smartdatamodels.org\/?p=40343"},"modified":"2026-08-20T17:14:19","modified_gmt":"2026-08-20T15:14:19","slug":"gaia-x-ontology-joins-smart-data-models-165-candidate-models-for-cloud-connectivity-trust","status":"publish","type":"post","link":"https:\/\/smartdatamodels.org\/index.php\/gaia-x-ontology-joins-smart-data-models-165-candidate-models-for-cloud-connectivity-trust\/","title":{"rendered":"Gaia-X Ontology Joins Smart Data Models: 165 Candidate Models for Cloud, Connectivity & Trust"},"content":{"rendered":"

Smart Data Models’ Candidates repository<\/a> now includes a new candidate standard, gaiax-ontology-v2111<\/code><\/strong>, translated from the Gaia-X ontology v2111<\/strong> \u2014 the vocabulary behind Self-Descriptions in Gaia-X federated data spaces and cloud ecosystems. All 165 classes<\/strong> published at docs.gaia-x.eu\/ontology\/v2111\/classes<\/a> now have an NGSI-LD \/ NGSI-v2 representation.<\/p>\n

What’s in it<\/h2>\n

Gaia-X’s ontology is broader than a typical device\/observation vocabulary \u2014 it describes both the physical\/technical side of an offering and the legal\/governance claims attached to it. That split shows up directly in the model mix:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Category<\/th>\nModels<\/th>\nExamples<\/th>\n<\/tr>\n<\/thead>\n
Legal & governance documents<\/td>\n50<\/td>\nLegalDocument<\/code>, TermsAndConditions<\/code>, DataUsageAgreement<\/code>, ServiceAgreementOffer<\/code><\/td>\n<\/tr>\n
Compute & software<\/td>\n27<\/td>\nCPU<\/code>, GPU<\/code>, Memory<\/code>, Hypervisor<\/code>, ComputeFunctionRuntime<\/code>, Image<\/code><\/td>\n<\/tr>\n
Security<\/td>\n25<\/td>\nEncryption<\/code>, PhysicalSecurity<\/code>, InformationSecurityPolicies<\/code>, ProductSecurity<\/code><\/td>\n<\/tr>\n
Network<\/td>\n23<\/td>\nEndpoint<\/code>, VLANConfiguration<\/code>, InterconnectionServiceOffering<\/code>, PointOfPresence<\/code><\/td>\n<\/tr>\n
Infrastructure<\/td>\n19<\/td>\nDatacenter<\/code>, AvailabilityZone<\/code>, Region<\/code>, PhysicalResource<\/code><\/td>\n<\/tr>\n
Service offerings<\/td>\n17<\/td>\nServiceOffering<\/code>, ComputeServiceOffering<\/code>, StorageServiceOffering<\/code><\/td>\n<\/tr>\n
QoS metrics<\/td>\n13<\/td>\nLatency<\/code>, Jitter<\/code>, PacketLoss<\/code>, Throughput<\/code>, IOPS<\/code><\/td>\n<\/tr>\n
Storage<\/td>\n13<\/td>\nBlockStorageConfiguration<\/code>, ReplicationPolicy<\/code>, SnapshotPolicy<\/code><\/td>\n<\/tr>\n
Data products<\/td>\n13<\/td>\nDataProduct<\/code>, DataProductCatalogue<\/code>, EvidenceTemplate<\/code><\/td>\n<\/tr>\n
Trust framework<\/td>\n10<\/td>\nEcosystem<\/code>, EcoTrustScope<\/code>, EcoTSP<\/code>, CompliantCredential<\/code><\/td>\n<\/tr>\n
+ identifiers, measurement, FaaS, environmental, and more<\/td>\n~19<\/td>\nVatID<\/code>, EORI<\/code>, EnergyMix<\/code>, WaterUsageEffectiveness<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Every model ships the full set of Candidates artifacts: a JSON Schema, an NGSI-LD @context<\/code>, and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized) \u2014 each validated against its own schema.<\/p>\n

Translation notes<\/h2>\n