Web of Things Interest Group Charter

Comments are welcome on the Web of Things Interest Group public email list , and you are encouraged to file issues on GitHub and open pull-requests with concrete proposals. The GitHub location of this document is https://github.com/w3c/wot/tree/master/charters/wot-ig-2016.html .

The mission of the Web of Things Interest Group is to counter the fragmentation of the Internet of Things (IoT) by introducing a Web-based abstraction layer spanning existing IoT platforms and complementing available standards. We seek to reduce costs through the global reach of Web standards, to enable open markets of services, and to unleash the power of the network effect. As a W3C Interest Group, we're seeking to build a shared understanding of the Web of Things, and to identify opportunities for initiating standards track work within W3C Working Groups. Industry alliances and standards development organizations are seeking to collaborate with W3C in two critical areas: semantic interoperability and end to end security across different platforms.

Join the Web of Things Interest Group.

Start date	~~[dd~~ 11 July 2016 monthname yyyy] (date of the "Call for Participation", when the charter is approved)
End date	~~[dd monthname yyyy]~~ 18 months after the start of the charter
Chairs	[chair name]
Team Contacts	Dave Raggett, (0.2 FTE ), Kazuyuki Ashimura (0.1 FTE ), Yingying Chen (0.1 FTE )
Meeting Schedule	Teleconferences: Weekly with additional topic specific calls as appropriate. Face-to-face: we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, with no more than 4 face to face meetings in total per year.

Introduction

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 with the Web of Things.

To achieve this goal for cross platform interoperability, 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. This is the second charter for the Web of Things Interest Group, and continues with the existing work items from the first charter in looking for technology building blocks for the application layer that forms the Web of Things.

The Web of Things is founded on the Architecture of the World Wide Web . Things stand for physical or abstract entities such as devices and, respectively, locations encompassing multiple devices and additional metadata. Each thing is identified with a URI. This URI can be followed to access the thing's description, which can include its relationship to other things, analogous to links in HTML. The Web of Things also allows for on-device data processing and direct thing-to-thing interaction. For this, things can provide a standardized vendor neutral runtime environment for portable apps, similar to Web apps running in every browser. 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.

The short term priority for the Interest Group is to launch a Working Group to initiate standardization for work items that the Interest Group believes are ready for progression along the W3C Recommendation track. In the mid-term, the priority is to demonstrate how the Web of Things can be used across a wide range of IoT platforms in collaboration with the corresponding organizations. This will include work on metadata for describing particular platforms, as well as work on semantic models and constraints, and enabling end to end security across different platforms. In the long term, the priority will be on enabling open markets of services on the scale of the Web.

Scope

The Web of Things Interest Group is a forum for discussion of ideas relating to the Web of Things, and is intended to complement the role of the proposed Web of Things Working Group. In particular, the Interest Group will propose new Work Items for the Working Group based upon new use case considerations, and discussions with IoT developer communities, industry alliances and standards development organizations. Vice versa, the Interest Group will consider new topics that are submitted to it by the Working Group.

The Interest Group will identify requirements for standardization by exploring use cases and requirements for a broad range of application domains, and through examining the requirements for integrating a broad range of IoT platforms into the Web of Things. Two areas that have already been identified as critical are semantic interoperability and end to end security. The Interest Group will work on these in coordination with external groups to address their needs. This is expected to include an exploration of the role of semantic technologies for representing and applying domain constraints, and an exploration of the role of trust assumptions for enabling end to end security across platforms using standards defined by different organizations. This work would combine implementation experience with in-depth analysis.

An important activity is the operation of PlugFests to test interoperability and to validate the current working assumptions of the technology building blocks discussed in the Web of Things Interest Group. These events enable developers to get together to test their implementations and facilitates networking between partners and experts. The Interest Group will seek to encourage work on open source projects and community evaluation of the Web of Things. In more detail, PlugFests enable:

support for the Web of Things WG in respect to implementation reports for Candidate Recommendations
test-drive upcoming or proposed technologies for the W3C Recommendation Track
interoperability testing across implementations for ideas at different levels of maturity
outreach to other communities and new members (open day, demo track)

The Interest Group will use the practical experience gained from these experiments as a basis for identifying new work items. Further ideas for topic areas are expected from discussions and expert presentations of IoT projects, including, for example, decentralised IoT systems and the role of blockchains. Another example is the exploration of ideas for a vendor neutral Web platform for apps that are installed on home gateways. The Interest Group will incubate work items for the Web of Things until they are ready for transfer to the W3C Recommendation Track, either in existing Working Groups, such as the Web of Things Working Group or in new Working Groups.

Scope Summary

~~Statement paragraph~~

~~Concrete items~~

Support the proposed Web of Things Working Group
Organize and run PlugFests to evaluate the current working assumptions of Web of Things technology
Reach out and collaborate with interested organizations, vendors and communities in support of the Interest Group's mission
Explore areas and identify work that is ready for transfer to the W3C Recommendation Track

Deliverables

More detailed milestones and updated publication schedules are available on the group publication status page . ~~Description~~ The first four deliverables listed below were started during the first charter period. The next two cover critical areas for the Interest Group's mission. Note that to help with these, we are seeking new participants with expertise in the areas of embedded systems, IoT platforms and protocols, security, data types and semantic modelling.

Use Cases and Requirements: This document will collect use cases from a range of application domains, and identify requirements that are shared across domains, and those that are specific to each domain.
Technology Landscape: This document will look at existing practices and standards, and identify opportunities for new work.
Architecture: This document will provide a high level overview of the architectural components of the Web of Things.
Current Practices: This document will ~~document~~ describe building blocks that have been evaluated through prototypes and so-called PlugFests (interoperability testing).
End to end security across IoT platforms: ~~Deliverable description.~~ This document will report on an in-depth practical study on enabling end to end security across a hetergeneous set of platforms. This document will be developed in conjunction with experimental implementations for the PlugFests.
Semantic Models and APIs: This document will report on an in-depth practical study on the role of semantic models and domain constraints as a basis for interoperability. This will include work on the role of APIs for providing developers with a more convenient way to work with semantic models. This document will be developed in conjunction with experimental implementations for the PlugFests.

Additional deliverables may be added by the Interest Group as appropriate to explore specific topics in greater depth.

Coordination

For all specifications, this Interest Group will seek horizontal review for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the TAG . Invitation for review must be issued during each major standards-track document transition, including FPWD and CR , and should be issued when major changes occur in a specification.

Issue: The paragraph above replaces line-item liaisons and dependencies with individual horizontal groups. There's been a suggestion to name and individually link the specific horizontal groups inline, instead of pointing to a page that lists them. Issue: The requirement for an invitation to review before FPWD and CR may seem a bit overly restrictive, but it only requires an invitation, not a review, a commitment to review, or even a response from the horizontal group. This compromise offers early notification without introducing a bottleneck.

Additional technical coordination with the following Groups will be made, per the W3C Process Document :

W3C Groups

~~[other name] [specific nature~~ Web of ~~liason] Note: Do not list horizontal groups here, only specific WGs relevant to your work. External Organizations [other name]~~ Things Working Group: [specific nature of liason] Participation To be successful, this Interest Group is expected to have 6 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a day per week towards the Interest Group. There is no minimum requirement for other Participants. The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in Communication . The group also welcomes non-Members to contribute technical submissions for consideration, with the agreement from each participant to Royalty-Free licensing of those submissions under the W3C Patent Policy. Communication Technical discussions charter for this Interest Group are conducted in public . Meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted group is in ~~a manner that can be both read and written to by the general public. Working Drafts~~ preparation, and ~~Editor's Drafts of specifications~~ when it is operating, will be ~~developed on a public repository, and may permit direct public contribution requests. Information about~~ the most important W3C group ~~(including details about deliverables, issues, actions, status, participants, and meetings) will be available from~~ for the Web of Things Interest Group ~~home page.~~ to coordinate with.
~~Most~~ Semantic Web ~~of Things~~ Interest Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis. This group primarily conducts its technical work on the public mailing list public-wot-ig@w3.org ( archive ). The public is invited to post messages to this list. The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion. Decision Policy This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 3.3 ). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required. However, if a decision is necessary for timely progress, but consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote, and record a decision along with any objections. To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. A call for consensus (CfC) will be issued for all resolutions (for example, via email and/or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue. If no objections are raised: For expertise on enabling the ~~mailing list by the end~~ expression of ~~the response period, the resolution will be considered to have consensus~~ semantic models and domain constraints as ~~a resolution~~ part of the ~~Interest Group. All decisions made by the group should be considered resolved unless and until new information becomes available, or unless reopened at the discretion~~ Web of ~~the Chairs or the Director. This charter is written in accordance with the W3C Process Document (Section 3.4, Votes) ,~~ Things, and ~~includes no voting procedures beyond what the Process Document requires. Patent Policy This Interest Group operates under the W3C Patent Policy (5 February 2004 Version). To promote~~ the ~~widest adoption~~ identification of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis. For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation . Licensing This Interest Group will use the W3C Software and Document license best practices.; For collaboration on semantic descriptions, e.g. the Semantic Sensor Network Ontology.
RDF Data Shapes Working Group ~~of the Process Document~~: For expertise on expressing structural constraints on RDF graphs in relation to domain models.
Privacy Interest Group: For collaboration on privacy considerations for the Web of Things.
Web Security Interest Group: For collaboration on areas of mutual interest in respect to security for the Web of Things.
Device and Sensors Working Group: For coordination on APIs for sensors and actuators.
Web and Automotive Business & Working Groups: For collaboration on technologies and requirements relating to connected cars and the Web of Things.
Efficient XML Interchange Working Group: In relation to efficient interchange for thing descriptions.

External Organizations

To succeed in establishing inter-platform standards, W3C needs to coordinate with IoT alliances and standards development organizations. The following provides examples of organizations with which the Interest Group has already had significant coordination, during the period of the first charter. A longer list is available on the Interest Group wiki.

Open Connectivity Foundation: For collaboration on integrating OCF based platforms within the Web of Things, including platform metadata and approaches for enabling semantic interoperability, and end to end security across platforms.
oneM2M: For collaboration on integrating M2M based platforms within the Web of Things, including platform metadata and approaches for enabling semantic interoperability, and end to end security across platforms.
GSMA: For coordination in respect to the interests of Network Operators.
IETF Authentication and Authorization for Constrained Environments (ace) Working Group: In respect to security building blocks for the Web of Things.
IETF Core Working Group: In respect to protocol bindings for the CoAP protocol.
IRTF Thing to Thing Research Group: For coordination of matters of mutual interest in relation to the Web of Things.
Industrial Internet Consortium: For collaboration on use cases, requirements and architecture for the Web of Things.
OPC Foundation: For collaboration on semantic interoperability and end to end security across platforms.
Plattform Industrie 4.0: For collaboration on use cases and requirements for smart manufacturing, including semantic interoperability and end to end security across platforms.

Participation

To be successful, this Interest Group is expected to have 6 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a day per week towards the Interest Group. There is no minimum requirement for other Participants.

The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in Communication . ~~In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence. Dave Raggett , Kazuyuki Ashimura , Yingying Chen~~

The group also welcomes non-Members to contribute technical submissions for consideration, with the agreement from each participant to Royalty-Free licensing of those submissions under the W3C Patent Policy.

Communication

Technical discussions for this Interest Group are conducted in public . Meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed on a public repository, and may permit direct public contribution requests.

Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the Web of Things Interest Group home page. ~~Copyright~~

Most Web of Things Interest Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.

The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.

Decision Policy

This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 3.3 ). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.

However, if a decision is necessary for timely progress, but consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote, and record a decision along with any objections.

To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. A call for consensus (CfC) will be issued for all resolutions (for example, via email and/or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue. If no objections are raised on the mailing list by the end of the response period, the resolution will be considered to have consensus as a resolution of the Interest Group.

All decisions made by the group should be considered resolved unless and until new information becomes available, or unless reopened at the discretion of the Chairs or the Director.

This charter is written in accordance with the W3C Process Document (Section 3.4, Votes) , and includes no voting procedures beyond what the Process Document requires.

Patent Disclosures

The Web of Things Interest Group provides an opportunity to share perspectives on the topic addressed by this charter. W3C reminds Interest Group participants of their obligation to comply with patent disclosure obligations as set out in Section 6 of the W3C Patent Policy. While the Interest Group does not produce Recommendation-track documents, when Interest Group participants review Recommendation-track specifications from Working Groups, the patent disclosure obligations do apply.

For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation .

Licensing

This Interest Group will use the W3C Software and Document license for all its deliverables.

About this Charter

This charter has been created according to section 5.2 of the Process Document . In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.