Developer call 1/28 & calendar invite

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

Perhaps we can carefully block a short window of time on the Agenda for this, if available?

I have several threads and messages in progress surrounding this Topic, but there hasn’t been broad participation, so the Call may be a way to rapidly collect some thoughts… (I can send you more info offline).

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…

Thanks,
… CP / Terry.