# Uavcan and raspberry pi

**URL:** <https://forum.opencyphal.org/t/uavcan-and-raspberry-pi/592>\
**Category:** PyCyphal\
**Created:** [August 12, 2019, 5:39pm UTC](https://forum.opencyphal.org/t/uavcan-and-raspberry-pi/592 "2019-08-12T17:39:39Z")\
**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:** [December 24, 2019, 10:23pm UTC](https://forum.opencyphal.org/t/uavcan-and-raspberry-pi/592/13 "2019-12-24T22:23:46Z")

</div>

As explained in [Data type regulation policy and membership fees](https://forum.opencyphal.org/t/data-type-regulation-policy-and-membership-fees/707), the idea is to enable vendors to collaborate on abstract, reusable interfaces in a well-regulated fashion. In the longer term, we will use regulated vendor namespaces (such as `regulated.zubax`) as a base to define standard vendor-agnostic profiles. Keeping such generic namespaces in one repository is necessary to reduce the risk of fragmentation and to simplify their maintenance.

I don’t think the name of a namespace could prevent other companies from using it in their systems or products.

---

_[View the full topic](https://forum.opencyphal.org/t/uavcan-and-raspberry-pi/592)._