It does seem very sensible and relevant.
Except for “Message Scheduling for complex busses”, of course. I would have declined to contribute only if it were about time-triggered communication, but message scheduling does not necessarily imply TT. Asynchronous message scheduling exists and it does not require TT:
But, what I meant when I said about posting here is that if we are ready to share a bit of UAVCAN wisdom with the world, we should make a forum thread or a dozen and let them sit for a while. Collect questions and criticism, etc. Kind of what I attempted to do here: Idempotent interfaces and deterministic data loss mitigation, or maybe even here: RTOS CAN API requirements. Then, having a critical mass of such items accumulated, we could squeeze them all into an e-book, slap a cat pic on top, and ship it 
.