# Root Namespace uavcan.\* after Rebranding **URL:** \ **Category:** Development & Maintenance\ **Created:** [April 19, 2022, 12:41pm UTC](https://forum.opencyphal.org/t/root-namespace-uavcan-after-rebranding/1644 "2022-04-19T12:41:59Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![finwood](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/finwood/32/536_2.png) [@finwood](https://forum.opencyphal.org/u/finwood)\ **Post date:** [April 19, 2022, 12:42pm UTC](https://forum.opencyphal.org/t/root-namespace-uavcan-after-rebranding/1644/1 "2022-04-19T12:42:00Z")
In the past few days and weeks, many projects comprising the OpenCyphal ecosystem have been updated to reflect the new name. Do I assume correctly that the [`uavcan.*` root namespace](https://github.com/OpenCyphal/public_regulated_data_types/tree/d0bd6516dac8ff61287fe49a9f2c75e7d4dc1b8e/uavcan) will be renamed as well? If yes, what would be the expected timeline and strategy? ---
**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:** [April 19, 2022, 12:44pm UTC](https://forum.opencyphal.org/t/root-namespace-uavcan-after-rebranding/1644/2 "2022-04-19T12:44:31Z")
There are no plans to rename the standard namespace to avoid the breakage of the deployed systems. It will remain “uavcan”. The rebranded Specification has clarifications on this subject: ![image](https://forum.opencyphal.org/uploads/default/original/2X/9/9044e61149bcdb6234e08da51c1f4ef40e1bdbad.png) ---
**Author:** ![finwood](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/finwood/32/536_2.png) [@finwood](https://forum.opencyphal.org/u/finwood)\ **Post date:** [April 19, 2022, 12:46pm UTC](https://forum.opencyphal.org/t/root-namespace-uavcan-after-rebranding/1644/3 "2022-04-19T12:46:26Z")
Ah, I missed the footnote. Thanks for the clarification!