Re: updated slides for web of things framework

> On 22 Apr 2015, at 09:25, Satoru Takagi <sa-takagi@kddi.com> wrote:
> 
> Hi dave,
> 
> You may know it, but we show the possibility that web browsers are incorporated in any things on last monday's demo. It is the concept that can be called as "Web browsers of Things" or "Pervasive Browsers". Seeing from this point of view, we have some comments for your slide.

Thanks much appreciated.

> 
> 4/20
>> From Pages to Things
> ....
>> Thing Description Language (TDL)
>> * Semantics and data formats as basis for interoperability
>> * Relationships to other things as basis for discovery
> 
> TDL will not necessarily have to be different from HTML.
> "HTML for pages and for discovery AND for Things" can be considered.

HTML is mainly about document structure for presentation by browsers.  TDL is essentially about linked relationships between things and their events, properties and actions, and relationships to other things.  So from this perspective, it  would be a conceptual mismatch.  HTML5 is well suited to provide a user interface for interacting with things.

But perhaps I am misunderstanding you?  I can imagine an HTML page that itself hosts things and exposes them via Web Sockets or perhaps WebRTC, although, I have yet to think of appropriate use cases.

> And we cannot think about today's web page in defiance of WebApps.
> In other words, we point out that logics by javascript are useful for interpretation of such a semantics.

Indeed JavaScript can be used to interpret thing descriptions, particularly when they are expressed in JSON. For example, consider a web page that is loaded from example.com <http://example.com/>. The single origin security policy would allow the web page scripts to access things hosted by that server using either HTTP or Web Sockets. A JavaScript library could be used to create objects in the web page’s execution environment that act as proxies for the things hosted by the server. Direct access to things hosted by other servers would be disallowed unless those servers had set an appropriate CORS policy.
> 
> 6/20
>> Web of Things Framework
>> Bindings to a range of protocols
> 
> Not only the protocols but also the HTML should be considered as the binding by the comment mentioned above.
> 
> Furthermore, Forms etc. of the HTML can be bound to things.

HTML pages are clearly fine as a user interface for interacting with things, but I am not sure precisely what you mean here by “bound to things”.  

> 
> The CG related to "Web browsers of Things" in the W3C is here.
> https://www.w3.org/community/browserobo/
> 
> I can introduce many documents to you if you have further interests.


Do you have some particular use cases you can share with us?

—
   Dave Raggett <dsr@w3.org <mailto:dsr@w3.org>>