> On 01 Aug 2016, at 13:32, Georg Henzler <[email protected]> wrote: > > Hi Robert, > >> ... I would rather see it named org.apache.sling.jcr.oak-restrictions >> and placed under contrib/jcr . > > That sounds like a better location, +1 to move > >> There was some discussion related to the name of the >> 'sling:resourceTypesWithChildren' restriction [1]. I want to make sure >> that we have agreement that this is the best name > > I think sling:resourceTypesWithChildren is the clearest suggestion up to now > ([1] gives an example). From a pure user point of view, the terms "parent" or > "ancestry" would be rather misleading, because what is matched by the > restriction in the end are nodes below (and not above) the matched node with > the given resource type, e.g. the restriction matches a node with resource > type "myproj/news" with (or including) all children. For me the matched node is the one I want to modify/insert, not the one carrying the ACE with the restriction. Maybe we should clarify that even more in the documentation, because when it comes to applying ACEs you are dealing with two different nodes: the one you try to modify and the one where the ACE is set (this is not necessarily the same node). For me the documentation at [1] is not clear enough in that regard, especially how inheritance is being treated. On which level is the resourceType being compared? On the level where the ACE is set or on the matched node level?
Also the sentence: "Only resources that have one of the supplied resource types are matched, child and parent resources with other resource types are not matched." What node does parent and child refer to in this sentence? > > Regards > Georg > > > [1] > https://sling.apache.org/documentation/bundles/sling-oak-restrictions.html#restriction-slingresourcetypeswithchildren
