Following up my own post with another pain point of v0 that I forgot to mention.
We’ve found it quite common that a message gets added by a vendor, let’s call them COMPANYX, and then later we want to adopt that message into a different namespace, say ardupilot namespace or uavcan namespace.
Right now if we renamed a DSDL from org/COMPANYX/equipment/foo/2000X.FooBar.uavcan to org/ardupilot/equipment/foo/200YY.FooBar.uavcan then the signature would change, which means the original vendors equipment would no longer be compatible. This makes it really painful to do the natural migration of new messages from vendor namespaces into more widely used namespaces. The original vendor needs to carry patches against the upstream code that has adopted their message in order to use it with their equipment.
I don’t see how this is addressed in v1, although I could be wrong.
There are many ways this could be addressed. Perhaps the simplest would be to allow DSDL directives to specify an override for the signature, or allow an override for the namespace to be used when computing the signature.