About the Capability Type Suggestions category

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

Can this include discussion about attributes and/or commands that could be added to existing Capabilities?

Though: That could be a can of worms, if Capabillites must be “strictly” implemented by Device Types (see:

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…

).

---

I suppose in the meantime, it would be nice for the “observers” to consider if any of the suggested “New Capabilities” could or should be rolled-into existing Capabilities, and discuss the implications.

Random example of “add” suggestion: capability.switch … add command: toggle() (no parameters).