This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
talks:janes_david:what_should_a_thing_api_look_like [2015-04-12 10:50]
stefan_hupe [Video]
talks:janes_david:what_should_a_thing_api_look_like [2015-04-17 09:40]
stefan_hupe [What should a Thing API look like]
Line 3: Line 3:
 // by [[speakers:​janes_david|David Janes]] // // by [[speakers:​janes_david|David Janes]] //
-tdb ...+In the last 15 years, technologists have converged on a simple but powerful model for writing APIs: HTTP, REST, and JSONThe net result is that developers are usually able to pick up new APIs and start getting useful results within minutes.
 +If we were to use the "API Model" for providing access to Things, what would this look like? This talk walks through real-world examples of what a Thing API should look like, using exactly the same model you would to access any other Internet resource. It outlines some common practical concerns, such as what IDs should be used for Things, how do you differentiate between the "input state" and the "​output state" of "​real"​ Things, and how semantics can be added to enable interoperability.
 ===== Slides ===== ===== Slides =====