You should never OSGI configuration explicitly, but you should let the container do this for you!
From what I understood you have these nodes:
* /apps/myapp/config.author/x.y.z (sling:osgiConfig)
* /apps/myapp/config.publish/x.y.z (sling:osgiConfig)
* /apps/myapp/config.development/x.y.z (sling:osgiConfig)
which is correct. Now you need to have a service with the PID x.y.z, which can be done the easiest way, if you "x.y" is the java package name and "z" is the classname of that service. Now you can read the configuration value as part of the service activation.
And as the next part you need to create a slingmodel, which is using your x.y.z service to do something useful, and embed that slingmodel into HTL.
This might sound overkill, but if it's really overkill, you are often trying to store parameters as OSGI configuration, which should not be OSGI configs at all.
HTH,
Jörg