Wikipedia:Articles for deletion/Capability-based programming

Capability-based programming

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

Asserts WP:OR at the moment. Comes from an accomplished software engineer advancing a possible approach to device integration and control for Iot devices/systems but currently not an accepted dev. standard amongst the computing firmament . Almost copied verbatim from his blog which he has licensed. scope_creep talk 19:06, 3 August 2014 (UTC)[reply]

Note: This debate has been included in the list of Software-related deletion discussions. Jinkinson talk to me 19:18, 3 August 2014 (UTC)[reply]

Delete per WP:NOTSOAPBOX. Justlettersandnumbers (talk) 19:38, 3 August 2014 (UTC)[reply]
Delete—I'm not seeing enough in the way of WP:RS to justify an article at this point in time. Lesser Cartographies (talk) 14:20, 5 August 2014 (UTC)[reply]

The article discusses a methodology described within the SMPTE ST2071-1 standards document to address the "Basket of Remotes" and object self-description problems posed by generic device/service control applications. I have added the reference to the prose document in which it is defined and removed any text that sounds promotional. posicks talk to me 17:53, 7 August 2014 (UTC)[reply]
The methodology of using identified features (aka. Capabilities in this case) is becoming a common theme in device/service control applications, such as media & device control within the professional media industry, home automation, and the Internet of Things. For example, the Eclipse Smart Home Core project has/is adding similar concepts, calling the objects "Things" and the identified features "Channels", as has the FIMS 1.1 standard with the introduction of "Capabilities" to their Repository specification. In addition, products by vendors such as Fairlight also use these concepts within their product lines in order to allow clients to work with features, not objects. The methodology of implementing self-describing objects through the use of small, concise, uniquely identified features seems to be an emerging development pattern. Maybe this text is better served as part of the SMPTE ST2071 article until the methodology becomes more commonplace. Please advise. posicks talk to me 19:53, 7 August 2014 (UTC)[reply]