Major Description
upon the initial creation of a JCR repository the associated SPI layer (oak-core) should
take care of setting up the corresponding MK-instance. this includes (incomplete list):
- create the jcr repo (not sure what that means in terms of mk-implementation)
- create the jcr:system node (unique for the repository, across workspaces)
- create the default workspace (-> name from config)
- create the root node of the default workspace
in addition the repository would need to have access to the following
information (maybe also mk-nodes underneath jcr:system ??)
- built-in node types
- built-in namespace
- built-in privileges
- built-in permissions
- repository configuration (can that be stored in the mk?)
as far as the workspace is concerned a functional repository would in
addition need to have:
- build-in users (based on some sort of configuration)
- workspace configuration