I think the focus being on the <whatever> that must be provided for a resource to be considered manageable is the correct way to go. We certainly should not be defining, or even implying implementation patterns for manageability. However, using existing management terms (often overloaded anyway), without defining them within the scope of our charter, could lead to that perception. 

So as we all have agreed we need a glossary of terminology to at least start from, so we are all on the page while we complete requirements. The glossary will need to evolve and become more formal as we start the specification work, but for now I thought I'd stick my neck out and offer an opportunity for everyone to light their flamethrowers!

Many of the terms we need at this point have been defined in the requirements work completed by the MTF at the W3C and seem, to me, to be a good starting point (consensus on these terms was reached by the members of the MTF, many of whom now participate on the TC). Granted they were defined specific to management of the Web services and elements of the Web services architecture, but with a little tweaking can be used for both the management of and management using Web services. MTFers will notice I've already tweaked the definitions submitted to the WSA group to fit both management using and of web services.

Manageable implies that a resource can effectively be managed by a Manager

Manageability implies the existence of a sufficient set of manageability capabilities such that a resource is manageable.

Manager the consumer of manageability capabilities offered by resources

Manageability capabilities include properties, operations and events exposed for the management of a resource.

Management is the utilization of the manageability capabilities by a Manager.

Managed implies that a resource's manageability capabilities are actively being utilised by a Manager.

Manageability interface is the interface through which manageability capabilities are exposed.

Manageability endpoint is the address at which the managebaility interface can be accessed.

Lets not get too pedantic or religious, about these they can change as we go through the work we have ahead, they are simply offered as a start point for the glossary to aid understanding and add clarity for the requirements.

Mark/