Skip to content

CPACS 3.5.1-RC2

Pre-release
Pre-release

Choose a tag to compare

View all tags
@MarAlder MarAlder released this 03 Jul 22:20
v3.5.1-RC2
5db8a56

CPACS v3.5.1-RC2

This release is the second release candidate for CPACS v3.5.1.

CPACS v3.5.1 remains a refinement release on top of CPACS v3.5, focused on stabilizing and clarifying recently introduced schema concepts based on stakeholder feedback and first implementation experience.

This RC2 specifically updates and extends the proposed refinement of systemElements. The update is still within the scope of the v3.5.1 systems refinement, but it is substantial enough to warrant an additional explicit community review before the final release.

Main focus of RC2

The main change compared to the previous release candidate is the significantly elaborated structure of predefined systemElements.

Instead of listing all predefined system elements directly below systemElements, the schema now introduces a function-oriented hierarchy. Predefined elements are grouped according to their primary functional role, for example:

  • electricalElements
  • mechanicalElements
  • pneumaticElements
  • hydraulicElements
  • thermoFluidElements

Within these domains, elements are further organized into functional categories where applicable, such as:

  • storageElements
  • conversionElements
  • distributionElements
  • controlElements
  • consumerElements

The goal is to make the system element library easier to understand, easier to extend, and more consistent for CPACS users and tool developers.

System element structure

The updated structure follows the established CPACS schema pattern more consistently:

  • plural container elements for lists
  • singular element names for individual predefined elements
  • uID-bearing singular system elements
  • reuse of the common system element base definition
  • clearer distinction between generic and specialized system element classes
  • improved documentation for hierarchy levels and element groups

Geometry representation

The geometry representation concept has been extended with a placeholder value.

This value is intended for cases where the actual geometry of a system element is not yet known and a simplified geometry is provided only for visualization purposes. A placeholder geometry should not be interpreted as the intended physical shape or installation envelope of the element.

Scope and release process

A release candidate is normally intended as the final review stage before the official release. However, the systemElements refinement has evolved significantly since the first release candidate. Publishing this update explicitly as RC2 is therefore intended to provide a transparent and well-defined review baseline for the community.

Related topics

The overall CPACS v3.5.1 refinement release continues to address the topics discussed during the stakeholder review phase:

While RC2 focuses mainly on the elaborated systemElements structure, it remains part of the same CPACS v3.5.1 release package.

Acknowledgements

We would like to thank everyone who contributed to the systems refinement and the CPACS v3.5.1 review process so far. Your feedback is essential for ensuring that the updated schema remains robust, understandable, and useful across the CPACS tool ecosystem.

Assets 2
Loading