I'll leave it to Ryan to confirm but I believe the primary reasoning for using the domain names is to avoid any collisions in the settings database (dconf in the normal case). In the case of /apps/onboard you are potentially at risk of another application called onboard using this name and colliding with your settings. If you use a domain name that you own, then the chances of collision are low. You probably can do what Gwibber has done an pick a domain name that would be appropriate for your project, but if you don't actually own that domain then there is some (incredibly low) risk that someone could register onboard.org project in the future and try and use that name.
I'll leave it to Ryan to confirm but I believe the primary reasoning for using the domain names is to avoid any collisions in the settings database (dconf in the normal case). In the case of /apps/onboard you are potentially at risk of another application called onboard using this name and colliding with your settings. If you use a domain name that you own, then the chances of collision are low. You probably can do what Gwibber has done an pick a domain name that would be appropriate for your project, but if you don't actually own that domain then there is some (incredibly low) risk that someone could register onboard.org project in the future and try and use that name.