About the Capability Type Suggestions category

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

@copyninja

Second, do we have a firm description of what capabilities in general is all about so developers understand what to request for.

Third, do we have any extra guidelines for naming conventions (just to satisfy my OCD)

No… But I’m willing to suggest a definition and guidelines and let SmartThings adjust me…

I’d recommend my post below as background on why there is no simple answer.

Capabilities: Existing and Process to Add New. Note: Capabilities ~= Interfaces?: Capabilities MUST be very strictly defined and enforced (attributes / commands / events)?

Continuing the discussion from How to add a new device “capability”?: Hi guys… Great topic! This is something I’ve brought up in discussion with @Ben ages ago, and with @Jim very recently. My discussions with SmartThings (at great length) are tied to the fact that Capabilities are quite similar to the concept of OO Interfaces (Java and other strict object-oriented environments). Interfaces are a very powerful way to manage polymorphism and extensibility of classes and functionality. Ummm… somewhat briefly…(?) Capabilities (including all existing ones) must be thoroughly documented, particularly all attributes, commands, and event types. (NB: For interfaces, I believe that only methods (i.e., commands and getters/setters) are a part of the definition, so Capabilities have some extras…