Hi, In the spirit of keeping it simple. Why not "Configuration" ?
OSGi Configuration is nearly always referred to as "OSGi Configuration" by those that use Sling/AEM. I think it's only referred to as Configuration by those whose context is nearly always OSGi, ie OSGI developers. Most deployers don't see Sling/AEM as an OSGi container, they see it as Sling/AEM. Could be wrong about that. Best Regards Ian On 26 July 2016 at 16:04, Robert Munteanu <[email protected]> wrote: > On Tue, 2016-07-26 at 16:46 +0200, Bertrand Delacretaz wrote: > > On Tue, Jul 26, 2016 at 4:37 PM, Carsten Ziegeler <[email protected] > > rg> wrote: > > > ...it's neither Preferences nor > > > Configuration :) Configurences maybe (just a joke) ... > > > > I was thinking about Prefiguration...that's unusual but actually > > expresses the mix between both concepts, and it's a unique name in > > the > > Sling space. > > Prefigure means something else though > > an early indication or version of (something) > > So that might be a not-so-welcome association. I also think it's not a > very google-able word. > > Having thought about this a little I believe configuration pretty much > reflects what the new module does, even though it's not a perfect fit. > It's mentioned in the Jira issue several times, we have classes with > that name and also the wcm.io terminology page [1] talks about > 'Configuration' in many places. > > The only downside that I'm aware of is that there might be some > confusion regarding the relation between this module and OSGi configs. > But sadly there's (IMO) just one word which captures this properly. > > Maybe we could go with Context-Aware Configuration? This outlines what > the module brings on top of 'plain' OSGi configurations. > > Robert > > [1]: http://wcm.io/config/api/terminology.html >
