Open Objects on WoT 2013

364 views

Published on

A RESTful and Decentralised Implementation of Open Objects
Dice Lab, Royal Holloway University of London
Paulo Ricca, Kostas Stathis
paper: http://www.webofthings.org/wot/2013/papers/wot3-ricca.pdf

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
364
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
17
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • RFID, near future
  • Quick Example
  • Open Objects on WoT 2013

    1. 1. The Open Object DICE Lab Royal Holloway University of London Paulo Ricca Kostas Stathis
    2. 2. Smarter Objects…
    3. 3. …But Still Electronically Closed
    4. 4. We envision a world of collaborative Open Objects supported by End-User Development
    5. 5. Structure Framework Implementation Scenario and Case-Study Conclusions
    6. 6. Framework
    7. 7. FUNCTIONALITY +
    8. 8. Event Event
    9. 9. Event Event
    10. 10. Event
    11. 11. Actuators Sensors
    12. 12. Actuators Sensors C2 Cn…C1
    13. 13. Actuators Sensors C2 Cn…C1 E1
    14. 14. Actuators Sensors C2 Cn…C1 BnB1 E1
    15. 15. Behaviour Definition
    16. 16. Rule Definition
    17. 17. Implementation
    18. 18. Meta-Workflow
    19. 19. A Complete Open Object Event Listener Rule Execution Rule Storage Behaviour Managing Behaviour Advertising Thin Web Client Thin Web Server Other Behaviours Open Object
    20. 20. An Incomplete Open Object Event Listener Rule Execution Rule Storage Behaviour Managing Behaviour Advertising Thin Web Client Thin Web Server Other Behaviours Open Obje Event Listen Rule Execut Rule Stora Behaviour Man Behaviour Adve Thin Web Cl Thin Web Se Other Behavi pen Object ent Listener e Execution ule Storage iour Managing our Advertising n Web Client n Web Server er Behaviours Open Object
    21. 21. Scenario and Case- Study
    22. 22. Door Sign
    23. 23. Door Sign Door Sign Behaviours Behaviour Advertising Thin Web Client Thin Web Server Message Displayer Traffic Light
    24. 24. Availability Cube
    25. 25. Availability Cube Cube Behaviours Behaviour Advertising Thin Web Client Thin Web Server Orientation Sensing
    26. 26. Example Rules { rule: { when: check_calendar, do: [ { request: calendarchecking get_state, calendar: `https://calendar.google.com/…..', date_time: { request: timekeeping now } } ] } }
    27. 27. Example Rules{ rule: { when: check_availability, do: { request: flowcontrol choose, value: { request: orientationsensing get, on_fail: { request: eventlistener display_availability_from_calendar } }, options: [ { value: 1, do: [ { request: messagedisplayer display, message: "Out for Lunch” }, { request: trafficlight set, colour: red }, ] }, ……
    28. 28. Conclusions A framework definition; An implementation supporting distributed and decentralised choreography of Open Objects; A real-world experimental case-study, based on web standards and embedded implementation.
    29. 29. Thank you! Questions? Ideas?
    30. 30. Json Behaviour Definition { `name': NAME, `description': DESCRIPTION, `capabilities': [ { `name': NAME, `description': DESCRIPTION, `parameters': [ { `name': NAME, `type': TYPE, `description': DESCRIPTION, `optional': `True' | `False' } ] } ], `events': [ { `name': NAME, `description': DESCRIPTION } ], `characteristics': [ { `name': NAME, `description': DESCRIPTION, `unit': UNIT_OF_MEASUREMENT } ] }
    31. 31. Json Rule Definition { rule: { rule_id: ID, cardinality: { PURPOSE: { behaviour: BEHAVIOUR, minimum: MIN_NUMBER, assignment: {} } }, when: PURPOSE EVENT, do: [ { request: PURPOSE CAPABILITY, external: URI, ARGUMENT_NAME: ARGUMENT_VALUE OR REQUEST, execution: “bottom-up” OR “top-down”, on_error: {}, on_unauthorised: {}, on_unavailable: {} } ], on_error: {} } }

    ×