[{"data":1,"prerenderedAt":212},["ShallowReactive",2],{"blog-post-blog_en-tractus-x-edwg-partnerschaft-iso-standardisierung":3},{"id":4,"title":5,"body":6,"cover":196,"date":197,"description":198,"draft":199,"extension":200,"meta":201,"navigation":202,"path":203,"seo":204,"stem":205,"tags":206,"__hash__":211},"blog_en\u002Fen\u002Fblog\u002Ftractus-x-edwg-partnerschaft-iso-standardisierung.md","Tractus-X and EDWG: Partnership for Protocols, Conformance, and ISO Standardization",{"type":7,"value":8,"toc":191},"minimark",[9,26,31,34,72,79,83,86,124,127,130,173,177,184,187],[10,11,12,13,17,18,21,22,25],"p",{},"Dataspaces depend on interoperability: participants must exchange data without implementing proprietary one-offs. In February 2026, at the ",[14,15,16],"strong",{},"Dataspace Symposium",", closer collaboration between ",[14,19,20],{},"Eclipse Tractus-X"," and the ",[14,23,24],{},"Eclipse Dataspace Working Group (EDWG)"," was communicated to better align protocols, conformance evidence, and standardization work.",[27,28,30],"h2",{"id":29},"division-of-responsibilities-between-working-group-and-project","Division of Responsibilities Between Working Group and Project",[10,32,33],{},"The partnership can be understood as interplay between specification and implementation:",[35,36,37,45,52,59,66,69],"ul",{},[38,39,40,41,44],"li",{},"EDWG: development and maintenance of ",[14,42,43],{},"protocols"," (for example the Dataspace Protocol) and profiles",[38,46,47,48,51],{},"EDWG: focus on ",[14,49,50],{},"standards"," and conformance (TCKs, claims\u002Ftrust profiles, interoperability approaches)",[38,53,54,55,58],{},"EDWG: definition of ",[14,56,57],{},"credential profiles"," and claims flows as trust building blocks for participants",[38,60,61,62,65],{},"Tractus-X: open source ",[14,63,64],{},"reference implementations",", including kits, connector distributions, and deployment artifacts",[38,67,68],{},"Tractus-X: semantic and use-case oriented building blocks for Catena-X rollouts",[38,70,71],{},"Tractus-X: feedback loops from operations and integration projects into specification work (issues, change requests)",[10,73,74],{},[75,76],"img",{"alt":77,"src":78},"Diagram: Specification → reference → standardization","\u002Fimg\u002Fblog\u002Ftractus-x-edwg-partnerschaft-iso-standardisierung-diagram.svg",[27,80,82],{"id":81},"what-conformance-means-in-dataspaces","What Conformance Means in Dataspaces",[10,84,85],{},"Conformance is multi-dimensional and typically introduced in phases:",[35,87,88,94,100,106,112,118],{},[38,89,90,93],{},[14,91,92],{},"Protocol conformance",": correct implementation of API flows and versions",[38,95,96,99],{},[14,97,98],{},"Identity and claims",": standardized credentials and verifiable identities",[38,101,102,105],{},[14,103,104],{},"Policy enforcement",": traceable evaluation of usage rules on the connector side",[38,107,108,111],{},[14,109,110],{},"Interoperability testing",": repeatable tests across implementations and releases",[38,113,114,117],{},[14,115,116],{},"Conformance statements",": documented versions, profiles, and supported features per participant\u002Fconnector",[38,119,120,123],{},[14,121,122],{},"Semantic conformance",": data contracts and model versions as prerequisites for use-case interoperability",[10,125,126],{},"In a standardization context, conformance becomes especially important because ISO\u002FIEC standards typically require not only a specification, but also clear evidence that implementations can be tested and validated.",[10,128,129],{},"A common entry point is automating conformance testing in CI:",[131,132,137],"pre",{"className":133,"code":134,"language":135,"meta":136,"style":136},"language-bash shiki shiki-themes github-light github-dark",".\u002Fgradlew test\n.\u002Fgradlew :tck:verify -PprotocolVersion=latest\n.\u002Fgradlew :interop:report\n","bash","",[138,139,140,153,165],"code",{"__ignoreMap":136},[141,142,145,149],"span",{"class":143,"line":144},"line",1,[141,146,148],{"class":147},"sScJk",".\u002Fgradlew",[141,150,152],{"class":151},"sZZnC"," test\n",[141,154,156,158,161],{"class":143,"line":155},2,[141,157,148],{"class":147},[141,159,160],{"class":151}," :tck:verify",[141,162,164],{"class":163},"sj4cs"," -PprotocolVersion=latest\n",[141,166,168,170],{"class":143,"line":167},3,[141,169,148],{"class":147},[141,171,172],{"class":151}," :interop:report\n",[27,174,176],{"id":175},"why-this-matters","Why This Matters",[10,178,179,180,183],{},"When protocols are standardized and operationalized through reference implementations, ecosystem fragmentation decreases. This increases the likelihood that dataspaces become cross-industry compatible and that participants can run implementations aligned to the same ",[14,181,182],{},"trust and interoperability rules",".",[10,185,186],{},"Additional conformance artifacts such as TCK reports and conformance statements also simplify procurement and reduce interpretational gaps between partners.",[188,189,190],"style",{},"html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}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":136,"searchDepth":155,"depth":155,"links":192},[193,194,195],{"id":29,"depth":155,"text":30},{"id":81,"depth":155,"text":82},{"id":175,"depth":155,"text":176},"\u002Fimg\u002Fblog\u002Ftractus-x-edwg-partnerschaft-iso-standardisierung-cover.jpg","2026-02-14","At the Dataspace Symposium 2026, closer collaboration between Eclipse Tractus-X and the Eclipse Dataspace Working Group was announced.",false,"md",{},true,"\u002Fen\u002Fblog\u002Ftractus-x-edwg-partnerschaft-iso-standardisierung",{"title":5,"description":198},"en\u002Fblog\u002Ftractus-x-edwg-partnerschaft-iso-standardisierung",[207,208,209,210],"Dataspace","Standards","Eclipse","Tractus-X","h3OfqW1_cGyWd4N2tETsmlYbRem0O34wNXUrWELodo4",1775680579294]