admin, config and custom roles

Release 2.0.9.0 is out, and its beta. This is a worth while release, as it effectively limits the use of header commands to DescriptorUnits where they are needed.

So I've also been working on the specs for 2.0.10. I've beefed it up a bit--it now defines admin, config and custom roles. Basicly a user assigned the role of admin in a Cabinet can do anything in that Cabinet.

The job of a user assigned the role of config is to define DescriptorUnits, while the job of a custom user is to customize the classifiers of the Topics in a Cabinet, as needed. Ordinary users then only see commands applicable to building content.

Note that even with 2.0.10, we will not have effective access control--any user can change the CabinetDescriptorUnit and assign themselves the admin role. (This will likely change in 2.0.11.) Rather, for now we are doing little more than restricting the visibility of commands to roles where they are applicable.

Of course, the Ark doesn't really look simpler to the user until the documentation becomes role-based.