Strawman Proposal: Web Thing Protocol HTTP Sub-protocol

Dear Web Thing Protocol Community Group members,

We recently published a first draft of the Web Thing Protocol WebSocket
Sub-protocol <https://w3c.github.io/web-thing-protocol/>, which is one of
the two main deliverables in our charter
<https://w3c.github.io/web-thing-protocol/charter/>.

The other main deliverable in our charter is the definition of an "HTTP
sub-protocol for the Web of Things". The idea of this sub-protocol is to
create a common protocol for communicating with connected devices over
HTTP, enabling consumers to carry out the full set of WoT operations
<https://www.w3.org/TR/wot-thing-description11/#table-well-known-operation-types>
using the familiar pattern of a REST API (i.e. the same as our WebSocket
sub-protocol, but using plain HTTP).
I have created a very rough strawman proposal
<https://w3c.github.io/web-thing-protocol/proposals/http-subprotocol/>
which defines an HTTP sub-protocol (alongside the current WebSocket
sub-protocol) that is essentially a combination of the common HTTP Basic
Profile <https://www.w3.org/TR/wot-profile/#http-basic-profile> and HTTP
SSE Profile <https://www.w3.org/TR/wot-profile/#http-sse-profile> protocol
bindings from the WoT Profiles specification, with Server-Sent Events
<https://html.spec.whatwg.org/multipage/server-sent-events.html> (SSE)
being used for event-based operations like observeproperty and
subscribeevent.

Please see this issue <https://github.com/w3c/web-thing-protocol/issues/116>
on GitHub for more background information and discussion. I would love to
hear what you think.

Kind regards

Ben

-- 
Ben Francis
Founder
Krellian Ltd. <https://krellian.com>