Minor Description
There are some cases where clients or even the JCR spec expect same name siblings to be supported. We should have some mechanism to allow such cases to work with no or minimal required changes. Such a mechanism doesn't need be fully compliant with the SNS feature as specified by JCR, just good enough to to cover the most common use cases.
My initial thinking on this is that, whichever way we end up implementing this, it would be nice if the underlying oak-core and microkernel -level SNS nodes simply used the "name[index]" naming pattern with no extra semantics associated with it.
