#### §B.1.(2) Between OTJLD 1.1 and OTJLD 1.2

- §1.2.1.(e): Visibility of role features

  Clarification has been added that a role can always access all the features that its enclosing team has access to.

- §2.1.2.(e): Generic roles/bases

  Relaxed the rules about generic bound roles. This change also subsumes what previously was a specific restriction in §4.1.(b).

- §3.1.(i) and §3.5.(f): Visibility of shorthand callout

  A role method defined by a shorthand callout binding can now specify a visibility modifier (see also §A.3.2), otherwise it inherits the visibility modifier of it's bound base method/field.

- §3.1.(j) and §3.5.(h): Visibility of inferred callout

  Role methods inferred as a callout binding are either `public` (inferred via interface) or `private` inferred from self call / field access.

- §3.5.(h): No explicit use of inferred callout to field

  Clarification has been added that an accessor method generated for an inferred callout to field can not be explicitly invoked.

- §4.1.(b): No callin in generic role

  A restriction has been made explicit that a generic role cannot define callin bindings.

- §4.2.(d) : Callin methods

  Slightly rephrased and extended the rule to make explicit that a callin method can indeed be intercepted using a second level callin binding.

- §6.1.(a) : Reflective methods `getAllRoles`

  More precision: answer only bound roles.