One of the specific features I've been looking at is that of applying firmware updates.
There are some ways to do that. Most imply having a separated bootloader and application. The bootloader's task is that it verifies applies the firmware update. Apply the bootloader is either enabling another partition, or effectively writing the new application over the older one.
Sometimes the application fetches the firmware update candidate, sometimes that task is up to the bootloader using some kind of minimal CANOpen implementation.
Both have their pro's and con's but that is not what I would like to discuss.

I've noticed the CiA paper 814:

Implementation and user guideline for CiA 417 - part 1: bootloader

Part of the paper describes from a user point of view the functionality of applying fwupdates over CANOpen through the bootloader. So some question come to mind:

• I'm wondering how 'default' this fwupdate principle actually is?
• Does everybody do it that way, i.e. is it standardized?
• Or is it just some sort of recommendation, which the document has applied through means of giving a good example?
• As far as I know, CANOpenNode doesn't include such feature. How could it be introduced? Should it follow any standardization?