# Data type extensibility and composition

**URL:** <https://forum.opencyphal.org/t/data-type-extensibility-and-composition/827>\
**Category:** Specification\
**Created:** [May 10, 2020, 12:31pm UTC](https://forum.opencyphal.org/t/data-type-extensibility-and-composition/827 "2020-05-10T12:31:11Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [May 29, 2020, 9:32pm UTC](https://forum.opencyphal.org/t/data-type-extensibility-and-composition/827/13 "2020-05-29T21:32:28Z")

</div>

This talk about extensibility is fueled by our empirical evidence that any _ **serious** _ system inevitably runs into the problem of modifying data types while retaining compatibility with deployed software (hardware).

 ![image](https://forum.opencyphal.org/uploads/default/original/1X/c88de181a3077574eb0c2f2ab363034ed4061b24.jpeg)

You can see this discussed seriously in-depth in [UAVCAN v1.0 and ArduPilot](https://forum.opencyphal.org/t/uavcan-v1-0-and-ardupilot/671).

At the same time, we need to manage the complexity, which is why we are not actually talking about arbitrary modification of types but we limit ourselves to _appendability_ only. Complexity is also the reason why I am hesitant to _seriously_ consider the introduction of different binary representations, especially within the same transport (Classic CAN and CAN FD are the same in the eye of UAVCAN).

Having _seriously_ analyzed the alternatives discussed here so far, I am inclined to believe that the approach described in my latest post here seems to be the closest to the optimal balance between the complexity and flexibility.

---

_[View the full topic](https://forum.opencyphal.org/t/data-type-extensibility-and-composition/827)._
