Make naming more consistent/better for "controllable" and "ACLControllable" Object-Type properties

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • None
    • Affects Version/s: None
    • Component/s: Domain Model, Schema
    • None
    • Hide

      Rename the two concepts as follows:

      Controllable --> Policy-controllable
      ACLControllable --> Securable

      This clarifies what "controllable" means, while removing the vague term "controllable" from ACLs and instead being more descriptive that they're for security purposes.

      Show
      Rename the two concepts as follows: Controllable --> Policy-controllable ACLControllable --> Securable This clarifies what "controllable" means, while removing the vague term "controllable" from ACLs and instead being more descriptive that they're for security purposes.

      Currently in CMIS (now that we've accepted ACLs), we have the following two properties on Object-type:

      • Controllable (means you can get/set policies on it)
      • ACLControllable (means youc an get/set ACEs on it)

      These names sound way too similar to each other.

            Assignee:
            Al Brown (Inactive)
            Reporter:
            Ethan Gur-esh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: