On Wednesday 06 January 2016 11:33:03 Bertrand Delacretaz wrote: > Hi, Hi,
> On Wed, Jan 6, 2016 at 10:59 AM, Carsten Ziegeler <[email protected]> wrote: > > ...Perfect :) .. > > Ok, glad that we agree! > > So how about the following implementation based on the above 3 requirements: > > a) tweak the provisioning model tools so that a new ProvisioningModel > service makes the content of :additional model sections available as > unprocessed full text at runtime this is for auditing, right? Does it really help if ACLs can be changed in several ways? > b) implement a component to process :basetree additional sections, > with a micro-language to define the initial paths (with node types) to > create for requirement 2) Does it need to be a _new_ micro-language or can we use the existing JSON and XML formats? > c) implement a component to process :accesscontrol sections using the > SLING-5355 ACL defs language (almost done in the acldefs/oak-jcr > module) > > d) later, implement a validation of the :accesscontrol against the > current repository state > > WDYT? Please make sure we have an "API" for these components which can be used when not using the provisioning model. O. > -Bertrand
