DOC REVIEW: Spelling error and a comment on the extension of the Collective Attribute standard(s)

[JesseCoretta]

OpenDJ Administration Guide - Version 4.8.0 (PDF)

Page 57, Procedure 5.3, Paragraph 2

OpenDJ extends collective attributes to give you fine-grained control over the which entries in the subtree are targeted. Also, OpenDJ lets you use virtual attributes, such as isMemberOf to construct the filter for targetting entries to which the collective attributes apply.

First off, targetting should be targeting

Next, the spirit of the actual comment should expanded.

Not only were Collective Attributes (RFC 3671) extended, but OpenDJ also extended SubtreeSpecification.SpecificationFilter (RFC 3672 § 2.1) to allow for RFC 4515 Search Filters as an alternative to the typical Refinement ASN.1 CHOICE:

     Refinement ::= CHOICE {
         item                [0] OBJECT-CLASS.&id,
         and                 [1] SET OF Refinement,
         or                  [2] SET OF Refinement,
         not                 [3] Refinement }

I realize the two standards often go hand-in-hand, but as someone who has done directory consulting for many years, your subsequent example on the next page ...

subtreeSpecification: {base "ou=people", specificationFilter "(isMemberOf=cn=Directory Administrators,ou=Groups,dc=example,dc=com)"}

... initially led me to believe that this was a documentation error, and not just a really cool feature 😎

You may also want to offer a word of CAUTION to users who leverage third-party LDAP client software -- particularly Apache Directory Studio -- that offers its own Subtree Specification "value editor". In Apache DS's case, it is sensitive to such non-standard values, such as a Search Filter, and will NOT support them.

Thanks! 😃

[JesseCoretta]

Screenshot from preliminary built test.