If we manage configuration container wide for multiple applications and parts of those then we _might_ like to introduce 'categories'.
In DeltaSpike we decided to not needing them because it is easy to just use namespacing and be done. But DeltaSpike config is mostly used inside an application and Tamaya should target container-wide configuration. So do we need those? We need to think through a few scenarios e.g. with multiple WARs configured on the same server. And also clustering. All the configuration along the classpath is 'local' to the current application anyway, but what about java env and properties, or a database configuration? Do we simply suggest using namespaces or do we like to introduce some application/category context? As always: adding this adds complexity and we really ONLY must do that if the advantages outpace the complexity. LieGrue, strub
