[{"data":1,"prerenderedAt":274},["ShallowReactive",2],{"blog-post-blog_en-dssc-blueprint-3-0-und-maturity-assessment":3},{"id":4,"title":5,"body":6,"cover":258,"date":259,"description":260,"draft":261,"extension":262,"meta":263,"navigation":264,"path":265,"seo":266,"stem":267,"tags":268,"__hash__":273},"blog_en\u002Fen\u002Fblog\u002Fdssc-blueprint-3-0-und-maturity-assessment.md","DSSC Blueprint v3.0: Reference for Data Spaces and a New Maturity Assessment",{"type":7,"value":8,"toc":253},"minimark",[9,22,27,30,72,79,83,86,108,111,114,234,238,249],[10,11,12,13,17,18,21],"p",{},"Building data spaces rarely fails because of a single technology. The blocker is usually a lack of comparability: concepts, roles, trust assumptions, and technical building blocks are named and evaluated differently across initiatives. With ",[14,15,16],"strong",{},"DSSC Blueprint v3.0"," (February 2026), reference elements were updated and complemented by a ",[14,19,20],{},"maturity assessment"," that classifies initiatives against defined criteria.",[23,24,26],"h2",{"id":25},"what-the-blueprint-covers","What the Blueprint Covers",[10,28,29],{},"The blueprint provides a consistent structure that projects can use as shared vocabulary:",[31,32,33,40,46,52,58,65],"ul",{},[34,35,36,39],"li",{},[14,37,38],{},"Business",": use cases, roles, benefits, and value streams",[34,41,42,45],{},[14,43,44],{},"Governance",": policies, contracts, onboarding, and compliance",[34,47,48,51],{},[14,49,50],{},"Trust",": identity, credential profiles, conformity, and enforcement",[34,53,54,57],{},[14,55,56],{},"Technology",": connectors, semantics, interfaces, operations, and security",[34,59,60,61,64],{},"A focus on ",[14,62,63],{},"interoperability"," so different implementations follow compatible flows",[34,66,67,68,71],{},"Guidance for ",[14,69,70],{},"operating models"," (for example platform operations, federation, participant onboarding)",[10,73,74],{},[75,76],"img",{"alt":77,"src":78},"Diagram: Blueprint layers and assessment","\u002Fimg\u002Fblog\u002Fdssc-blueprint-3-0-und-maturity-assessment-diagram.svg",[23,80,82],{"id":81},"maturity-assessment-from-status-to-roadmap","Maturity Assessment: From Status to Roadmap",[10,84,85],{},"The assessment connects architecture blueprints with operationalization:",[31,87,88,95,102,105],{},[34,89,90,91,94],{},"A criteria set for ",[14,92,93],{},"capabilities"," (for example interoperability, governance, operations)",[34,96,97,98,101],{},"Classification into ",[14,99,100],{},"maturity levels"," and identification of gaps",[34,103,104],{},"Self-assessment as a standardized entry point across different starting positions",[34,106,107],{},"Comparability across initiatives to steer roadmaps and investment priorities with data",[10,109,110],{},"Across many ecosystems, trust capabilities tend to lag behind technical connectivity in early phases. The assessment makes such asymmetries visible.",[10,112,113],{},"A schematic result can be documented as a data model:",[115,116,121],"pre",{"className":117,"code":118,"language":119,"meta":120,"style":120},"language-json shiki shiki-themes github-light github-dark","{\n  \"initiative\": \"example-dataspace\",\n  \"dimensions\": {\n    \"governance\": \"defined\",\n    \"trust\": \"emerging\",\n    \"technical\": \"operational\"\n  },\n  \"nextSteps\": [\"credential-profile\", \"policy-enforcement\", \"interop-testing\"]\n}\n","json","",[122,123,124,133,150,159,172,185,196,202,228],"code",{"__ignoreMap":120},[125,126,129],"span",{"class":127,"line":128},"line",1,[125,130,132],{"class":131},"sVt8B","{\n",[125,134,136,140,143,147],{"class":127,"line":135},2,[125,137,139],{"class":138},"sj4cs","  \"initiative\"",[125,141,142],{"class":131},": ",[125,144,146],{"class":145},"sZZnC","\"example-dataspace\"",[125,148,149],{"class":131},",\n",[125,151,153,156],{"class":127,"line":152},3,[125,154,155],{"class":138},"  \"dimensions\"",[125,157,158],{"class":131},": {\n",[125,160,162,165,167,170],{"class":127,"line":161},4,[125,163,164],{"class":138},"    \"governance\"",[125,166,142],{"class":131},[125,168,169],{"class":145},"\"defined\"",[125,171,149],{"class":131},[125,173,175,178,180,183],{"class":127,"line":174},5,[125,176,177],{"class":138},"    \"trust\"",[125,179,142],{"class":131},[125,181,182],{"class":145},"\"emerging\"",[125,184,149],{"class":131},[125,186,188,191,193],{"class":127,"line":187},6,[125,189,190],{"class":138},"    \"technical\"",[125,192,142],{"class":131},[125,194,195],{"class":145},"\"operational\"\n",[125,197,199],{"class":127,"line":198},7,[125,200,201],{"class":131},"  },\n",[125,203,205,208,211,214,217,220,222,225],{"class":127,"line":204},8,[125,206,207],{"class":138},"  \"nextSteps\"",[125,209,210],{"class":131},": [",[125,212,213],{"class":145},"\"credential-profile\"",[125,215,216],{"class":131},", ",[125,218,219],{"class":145},"\"policy-enforcement\"",[125,221,216],{"class":131},[125,223,224],{"class":145},"\"interop-testing\"",[125,226,227],{"class":131},"]\n",[125,229,231],{"class":127,"line":230},9,[125,232,233],{"class":131},"}\n",[23,235,237],{"id":236},"why-this-matters","Why This Matters",[10,239,240,241,244,245,248],{},"Data space initiatives are ecosystem-driven: interoperability only emerges if multiple participants build and operate against compatible rules. A shared blueprint plus maturity assessment improves comparability, reduces fragmentation, and accelerates alignment between ",[14,242,243],{},"governance"," and ",[14,246,247],{},"technology",".",[250,251,252],"style",{},"html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":120,"searchDepth":135,"depth":135,"links":254},[255,256,257],{"id":25,"depth":135,"text":26},{"id":81,"depth":135,"text":82},{"id":236,"depth":135,"text":237},"\u002Fimg\u002Fblog\u002Fdssc-blueprint-3-0-und-maturity-assessment-cover.jpg","2026-02-22","The DSSC Blueprint v3.0 updates the data space reference architecture and adds a maturity assessment including a self-assessment tool.",false,"md",{},true,"\u002Fen\u002Fblog\u002Fdssc-blueprint-3-0-und-maturity-assessment",{"title":5,"description":260},"en\u002Fblog\u002Fdssc-blueprint-3-0-und-maturity-assessment",[269,270,271,272],"Dataspace","DSSC","Data Sovereignty","Regulation","aa4hCEKIO50hVMi2fj1lcTahVu_i72ZXeJ00EN0Bpus",1775892934971]