Cross-Dataspace Traceability KIT

[matbmoser]

On the Fifth Eclipse Tractus-X Community Days we want to collect feedback on how to build a Cross Dataspace KIT for Semiconductor-X and Catena-X + more.

Please document here the output and discussions from the workshop

Views	Stakeholders	Content
Adoption View	Business	Business Value, Motivation, Vision, Mision, Whitepapers, Semantic Models, Standards, Tutorials, Explanations why this use case is important, Context
Development View	Developers/Architects	Overall Architecture, Reference Implementations, API specifications, Policies, Algorithms, Functional Requirements, Sequence Diagrams, Process, Architecture Guidelines
Operator View	Operators/Service providers	Non-Functional Requirements, Security Requirements, Recommendations, Restrictions
Documentations	any	Extra Documentation and Links
Success Stories	Operators/Service providers/Business	Success Stores from Reference Implementations that used this KIT. Open Source and COTS.
Dataspace Extensions	Semiconductor-X Adopter / Catena-X Adopter	One Folder per Dataspace. Extends the contents from the other views on regards to a specific dataspace.

Based on the connector KIT (which adds the Catena-X specifics on a tab), we would scale that for all KITs in a structured way:

There will be shared KITs which have both dataspace specifications, and also KITs which are only used in a Dataspace (Example):