[http://creativecommons.org/licenses/by/3.0/]
This work is licensed under a CC
Attribution 3.0 Unported License [http://creativecommons.org/licenses/by/3.0/]
Web Architecture provides a general-purpose way of establishing an interlinked network
of resources, which are interacted with through the exchange of representations of
their state. We argue that the Web of Things fits well into this general framework, and thus should be built firmly on the foundation
provided by Web Architecture. We also argue that in order to allow an evolutionary
path towards a Web of Things, it is important to take small and incremental steps towards the final goal, instead
of trying to establish a grand Web of Things Architecture
in one monolithic step. One interesting first step could be to focus on Activity
Streams as one way how streams of resource updates can be represented in a uniform,
extensible, and machine-readable way.
last mile(how to efficiently connect constrained things)
thing models(in order to find/understand/use things, we need domain models)
thing technology(we have technology X, it's really great for WoT!)
thing scenarios(we want use certain things a certain way)
surfaces
The last mile(how to connect the thing) might be better left to specialists
Atom framework
thing-orienteduse cases
Your friend X has just Y-ed resource Z on the Web.
WoT thing surface