Eclipse S-CORE Verified

<p dir="ltr">Eclipse S-CORE Verified provides an open, versioned suite of reproducible tests to verify that candidate distributions based on Eclipse S-CORE conform to its APIs, runtime characteristics, component integration contracts, documented external interfaces, expected behavior, and quality standards.</p><p dir="ltr">The Eclipse S-CORE Verified project defines “distribution” as followed: A distribution is a commercial or non commercial software stack that leverages a certain Eclipse S-CORE version as a middleware building block. The scope of the Eclipse S-CORE verified&nbsp; project is to:</p><ul><li dir="ltr" data-list-item-id="ef06e10797168adab4a53c130708b1a87">Define, in collaboration with the Eclipse S-CORE project and the broader Eclipse S-CORE community and the X-CORE platform council, the&nbsp;<strong>verification criteria</strong>&nbsp;that a distribution full-fills to demonstrate it is genuinely based on Eclipse S-CORE upstream components.</li><li dir="ltr" data-list-item-id="edfc3b863431a5ae75306d6f521e8abf3">Develop, maintain, and version an&nbsp;<strong>open verification test suite</strong>&nbsp;that exercises the public APIs, interfaces, runtime behaviour and integration points defined by Eclipse S-CORE.</li><li dir="ltr" data-list-item-id="e1a6875da092e2296b09c03770f00f541">Provide tooling and software infrastructure that allows any party — e.g. Eclipse S-CORE contributors, distributors, OEMs, independent integrators, academia — to&nbsp;<strong>run the test suite themselves</strong>&nbsp;against a candidate distribution and obtain reproducible, comparable results.</li><li dir="ltr" data-list-item-id="ec5040e4f1fc28f599e1b6e12c8c06ca2">Define a transparent, open&nbsp;<strong>result-reporting format</strong>&nbsp;so that verification outcomes can be shared, archived, and compared across distributions and across different Eclipse S-CORE versions.</li><li dir="ltr" data-list-item-id="ebdfa690262f235ca69be8b3b82613314">Maintain&nbsp;<strong>traceability</strong>&nbsp;between upstream Eclipse S-CORE source artefacts (Git commits, release tags, documentation) and the corresponding versioned test assets in this project, so that verification results are unambiguously tied to a specific upstream baseline.</li><li dir="ltr" data-list-item-id="e72c08966520bfb2faa15386852215a1c">Develop materials and documentation that make it straightforward for a distributor or downstream consumer to adopt the test suite and to understand the meaning — and limits — of a passing result.</li><li dir="ltr" data-list-item-id="e63d48d459dbfb474e4bc045892a6f681">Continuously evolve the test material in sync with new S-CORE releases, newly added components, and lessons learned from real-world execution.</li><li dir="ltr" data-list-item-id="ec716b8dc92c3881f12fb4a71a40d82c9">The project reuses the same versioning schema and methodology of the Eclipse S-CORE project. With each Eclipse S-CORE version a corresponding version of this project shall be available.&nbsp;</li></ul><p dir="ltr"><strong>Out of Scope</strong></p><p dir="ltr">To avoid confusion with related project types and existing Eclipse S-CORE governance, the following are explicitly&nbsp;<strong>out of scope</strong>:</p><ul><li dir="ltr" data-list-item-id="eabeb58561be27257c3ea35034588aadd"><strong>Issuing legally binding compatibility certifications</strong> or operating a trademark licensing program. These trademark and licensing frameworks are part of a broader program developed by the Eclipse Foundation around the Eclipse S-CORE Verified project, and authority over the "Eclipse S-CORE", "S-CORE Compatible", and "S-CORE Certified" marks rests exclusively with the Eclipse Foundation.</li><li dir="ltr" data-list-item-id="e03a01bdc0d153c09c9b7a04f8b4561a3"><strong>Determine the scope or roadmap of the Eclipse S-CORE project.</strong>&nbsp;This project consumes the Eclipse S-CORE specification and codebase as inputs; it does not define them.</li><li dir="ltr" data-list-item-id="ea9e533a144a90039032987e02e668131"><strong>Functional safety assessment</strong>&nbsp;for a specific downstream use is out of scope.</li><li dir="ltr" data-list-item-id="eb1c39227db2417e83ed2bc9f672468b3"><strong>Eclipse Specification Project.</strong>&nbsp;This proposal explicitly scopes the project as a verification / test suite project. Should the S-CORE community decide in the future to pursue a formal Eclipse Specification Project with an associated Technology Compatibility Kit, the assets developed here may serve as input to such a future effort, but that transition is not part of this proposal.</li></ul>