RE: Proposed introduction for IG charter scope

Hi Dave and all,

Since I could not find this on GitHub, I am commenting here in the mailing list.

The 3rd paragraph may be better understood by describing the heterogeneity first,
then the way WoT copes with it with URIs.

The proposed changes in the 3rd paragraph would result in:


<p>Due to the variations in requirements across application domains, there are many protocols. Things can be interacted with on many kinds of platforms and devices including resource constrained IoT devices, gateways and cloud-based server farms. In addition, Web browsers may be used for the human-machine interface for services based around the Web of Things.</p>

<p>To cope with this diversity and extent, the Web of Things is founded on the core architecture of the Web. Things stand for physical or abstract entities. Each thing is identified with a URI. This URI can be dereferenced to access the thing's description, which can include its relationship to other things.</p>


Thank you,

Takuki Kamiya
Fujitsu Laboratories of America


From: Dave Raggett [mailto:dsr@w3.org]
Sent: Monday, May 09, 2016 7:59 AM
To: Public Web of Things IG
Subject: Proposed introduction for IG charter scope

I am seeking feedback on some proposed wording for the IG charter for a brief introduction. I am having problems with github, Matthias is helping me, but I am not sure that everyone in the IG is tracking the pull requests, and have copied the proposed changes here in the interim.

             <h2>Introduction</h2>

  <p>The Internet of Things (IoT) suffers from a lack of interoperability across platforms. As a result developers are faced with data silos, high costs and limited market potential. This can be likened to the situation before the Internet when there were competing non-interoperable networking technologies. The Internet makes it easy to develop networked applications independently of those technologies. W3C is seeking to do the same for the Internet of Things.</p>

    <p>To achieve this goal, we need platform independent APIs for application developers, and a means for different platforms to discover how to inter-operate with one another. The approach we are taking is based upon rich metadata that describes the data and interaction models exposed to applications, and the communications and security requirements for platforms to communicate effectively. A further aspect is the need to enable platforms to share the same meaning when they exchange data. We are therefore seeking to enable expression of the semantics of things and the domain constraints associated with them, building upon W3C's extensive work on RDF and Linked Data.</p>

    <p>The Web of Things is founded on the core architecture of the Web. Things stand for physical or abstract entities. Each thing is identified with a URI. This URI can be dereferenced to access the thing's description, which can include its relationship to other things. Due to the variations in requirements across application domains, there are many protocols. Things can be interacted with on many kinds of platforms and devices including resource constrained IoT devices, gateways and cloud-based server farms. In addition, Web browsers may be used for the human-machine interface for services based around the Web of Things.</p>

This would be inserted just before the scope heading.

Comments/questions?

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