Since then, the Working Group is working on new specifications such as the WoT Profiles and WoT Discovery, while
working on the newer versions of Thing Description, Architecture, Scripting API and Binding Templates. If you are
- interested in learning about WoT, check our
- documentation page.
+ interested in learning about WoT, check our documentation page.
diff --git a/docs/about/index.html b/docs/about/index.html
new file mode 100644
index 0000000..6fc4278
--- /dev/null
+++ b/docs/about/index.html
@@ -0,0 +1,80 @@
+---
+layout: default
+title: About
+---
+
+
+
+
+
+
+
About W3C Web of Things
+
+ Learn more about the history of the Web of Things, read related articles, and find out how to get in touch with
+ us.
+
- The Web of Things (WoT) groups meet during the W3C's annual Technical Plenary week and additional face-to-face
- meetings are scheduled by the participants that happen 2 times a year. Moreover, the work items are prototyped and
- tested in WoT IG PlugFests that are scheduled for the weekend or week before the face-to-face meetings.
-
- We have grouped our weekly meetings in the table below. We also recommend you to use
- the W3C calendar system
- in order to download ICS files for all our meetings.
-
- The Web of Things (WoT) groups conduct some of their work via task forces and use a
- main wiki & call to provide an opportunity to
- summarize and coordinate the activities of the various task forces.
- See each task force page for details about specific work.
-
The WoT Architecture task force is responsible for the abstract architecture for the Web of Things.
-
Status: Suspended
-
-
Normative Deliverables
-
-
WoT Architecture
-
- The WoT Architecture specification describes the abstract architecture for the W3C Web of Things. It defines the
- terminology that is used by all other WoT building blocks. The specification defines a conceptual framework that
- can be mapped onto a variety of concrete deployment scenarios.
-
-
-
-
-
People
-
-
TF-Leads:
-
Michael Lagally (Oracle Corp.) and Michael McCool (Intel Corp.)
-
WoT Architecture Co-Editors:
-
- Michael Lagally (Oracle Corp.), Ryuichi Matsukura (Fujitsu Ltd.), Michael McCool (Intel Corp.), and Kunihiko
- Toumura (Hitachi, Ltd.)
-
- The WoT Discovery task force is responsible for defining a distribution mechanism for WoT Thing Descriptions that
- can be used to facilitate access to WoT Things and services while supporting security and privacy.
-
-
Status: Suspended
-
-
Normative Deliverables
-
The WoT Discovery TF is working on the first release of the following normative deliverable.
-
-
WoT Discovery
-
- The WoT Discovery specification defines a mechanism to provide access to WoT Thing Descriptions in both local
- and global contexts. It uses a two-phase approach to take advantage of existing discovery mechanisms for "first
- contact" but provides for authenticated web services to actually provide metadata in order to support security
- and privacy goals. WoT Thing Descriptions can be retrieved from services running either on a Thing itself (that
- is, directly from self-describing objects), or from a directory service that provides a searchable database of
- WoT Thing Descriptions.
-
-
-
-
-
People
-
-
TF-Lead:
-
Michael McCool (Intel Corp.)
-
WoT Discovery Co-Editors:
-
- Andrea Cimmino (Universidad Politécnica de Madrid), Michael McCool (Intel Corp.), Farshid Tavakolizadeh
- (Fraunhofer-Gesellschaft), and Kunihiko Toumura (Hitachi, Ltd.)
-
- The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the
- adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such as Web
- presence, Social Media presence, and more.
-
-
- Status:
- Active
-
-
-
People
-
-
TF-Lead:
-
Ege Korkan (Siemens AG)
-
-
-
-
Tasks
-
- The Marketing Task Force aims to reach out and support the wide Web of Things community. Our charter contains the
- goals for a certain period of time. The overall tasks of the task force are:
-
-
Maintaining the web page
-
- Creating visual materials such as:
-
-
Powerpoint templates
-
Figures
-
Animation
-
Videos
-
-
-
- Establishing the representation of WoT like a brand identity at:
-
-
WoT Repositories
-
WoT Web Page
-
WoT Wiki Pages
-
WoT Twitter account and other possible social channels
-
-
-
- Reaching out to the wide community through:
-
-
Social Media
-
Web Pages
-
Blog Posts
-
Promotional Text and Videos
-
Explainer Text and Videos
-
Tutorial Text and Videos
-
-
-
Assuring consistent style for all the points above
The WoT Profiles task force is responsible for interoperability profiles for the Web of Things.
-
Status: Active
-
-
Normative Deliverables
-
-
WoT Profiles
-
- The WoT Profiles Specification defines a Profiling Mechanism and a set of WoT Profiles which enables out of the
- box interoperability among things and devices. Out of the box interoperability implies that devices can be
- integrated into various application scenarios without deep level adaptations. Typically only minor configuration
- operations are necessary (such as entering a network key or IP address) to use the device in a certain scenario.
- These actions can be done by anyone without specific training.
-
-
-
-
-
People
-
-
TF-Leads:
-
Luca Barbato (Invited Expert) and Ben Francis (Invited Expert)
-
WoT Profiles Co-Editors:
-
- Michael Lagally (Oracle Corp.), Ben Francis (Invited Expert) Michael McCool (Intel Corp.), Ryuichi Matsukura
- (Fujitsu Ltd.), Sebastian Kaebisch (Siemens AG), and Tomoaki Mizushima (Internet Research Institute, Inc.)
-
- The WoT Scripting API task force is responsible for specifying an application programming interface (API)
- representing the WoT Interface that allows scripts to discover, invoke interactions with Things, and expose
- interactions for locally defined Things.
-
-
Status: Active
-
-
Informative Deliverables
-
The WoT Scripting API TF has its own informative deliverable.
-
-
Web of Things (WoT) Scripting API
-
- Scripting is an optional building block in WoT and it is typically used in gateways, hubs, or browsers that are
- able to run a WoT Runtime and script management, providing a convenient way to define the behavior of exposed
- Things, extend WoT support to new types of endpoints, orchestrate interactions among multiple Things, and
- implement WoT applications.
-
-
-
-
-
People
-
-
TF-Lead:
-
Daniel Peintner (Siemens AG) and Cristiano Aguzzi (Invited Expert)
-
WoT Scripting API Co-Editors:
-
Zoltan Kis (Intel Corp.), Daniel Peintner (Siemens AG), and Cristiano Aguzzi (Invited Expert)
- The WoT Security task force is responsible for identifying and analyzing the security and privacy considerations of
- the WoT and providing recommendations to support appropriate security technologies and to mitigate security and
- privacy risks.
-
-
Status: Suspended
-
-
Informative Deliverables
-
- In addition to contributions to other normative and informative WoT deliverables, such as security features in the
- WoT Thing Description and in WoT Discovery, the WoT Security TF has its own informative deliverables.
-
-
-
WoT Security and Privacy Guidelines
-
- The WoT Security and Privacy Guidelines document defines general security and privacy concepts and terminology
- for the W3C Web of Things, catalogs stakeholders and threats, and provides general guidance on best practices to
- mitigate these threats.
-
-
-
-
-
People
-
-
TF-Lead:
-
Michael McCool (Intel Corp.)
-
WoT Security and Privacy Guidelines Co-Editors:
-
Elena Reshetova (Intel Corp.) and Michael McCool (Intel Corp.)
- The WoT Thing Description task force is responsible for defining the information model for WoT Thing metadata, its
- interpretation, and its common representation. In addition, the task force covers WoT Binding Templates topics to
- define the mapping from the abstract interaction model used in the Thing Description metadata to concrete IoT
- protocols and payload encodings.
-
-
Status: Active
-
-
Normative Deliverable
-
-
WoT Thing Description 1.1
-
- This document describes a superset of the features defined for Thing Description 1.0. In general, this document
- describes the formal model of a Thing and its common representation in JSON-LD 1.1. It introduces a simple
- interaction model with Properties, Actions, and Events to describe the capabilities of a Thing, including its
- data model, communication protocols used, security mechanisms, and other semantic metadata. A WoT Thing
- Description defines a specific instance of a Thing. The WoT Thing Description 1.1 also formally introduces the
- Thing Model concept that describes sets of Things. It has fewer restrictions than the Thing Description and does
- not contain any instance-specific information.
-
-
-
Informative Deliverable
-
-
WoT Binding Templates
-
- This document describes a set of vocabulary extensions to the WoT Thing Description that make up the Binding
- Templates. Binding Templates enable a Thing Description to be adapted to specific protocol or data payload
- usages across different standards. This is done through additional descriptive vocabulary that is used in the
- Thing Description.
-
-
-
-
-
People
-
-
TF-Lead:
-
Ege Korkan (Siemens AG) and Michael Koster (Invited Expert)
-
WoT Thing Description Co-Editors:
-
Sebastian Kaebisch (Siemens AG), Michael McCool (Intel Corp.), Ege Korkan (Siemens AG)
-
WoT Binding Templates:
-
Michael Koster (Invited Expert), Ege Korkan (Siemens AG)
diff --git a/docs/activities/task-forces/tf-usecases/index.html b/docs/activities/task-forces/tf-usecases/index.html
index 6074100..fd86ef9 100644
--- a/docs/activities/task-forces/tf-usecases/index.html
+++ b/docs/activities/task-forces/tf-usecases/index.html
@@ -1,51 +1,18 @@
---
-layout: default
-title: Use Case Task Force
-group: 'navigation'
+layout: null
---
-
-
W3C WoT – Use Case Task Force
-
- The WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases
- can include both specific vertical applications as well as relevant horizontal technologies or other horizontal
- usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains,
- technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
-
-
Status: Active
-
-
Informative Deliverables
-
The WoT Use Case TF is working on the following informative deliverable.
-
-
WoT Use Cases and Requirements
-
- The WoT Use Cases and Requirements document includes a catalog and taxonomy of use cases and a set of general
- requirements extracted from an analysis of these use cases. These requirements are then used to drive the
- development of other normative WoT specifications.
-
-
-
-
-
People
-
-
TF-Leads:
-
Tomoaki Mizushima (Internet Research Institute, Inc.), Michael McCool (Intel Corp.),
-
WoT Use Cases Co-Editors:
-
- Michael McCool (Intel Corp.), Luca Barbato (Luminem Srl), Ege Korkan (Siemens AG), Tomoaki Mizushima (Internet
- Research Institute, Inc.)
-
-
Previous Editors:
-
Michael Lagally (Oracle Corp.), Ryuichi Matsukura (Fujitsu Ltd.)
- The aim of the Web of Things Community Group (CG) is to accelerate the adoption of Web technologies as a basis for
- enabling services for the combination of the Internet of Things with rich descriptions of things and the context
- in which they are used.
-
The mission of the Web of Things Japanese Community Group includes the following:
-
-
- to facilitate focused discussion in Japanese on the Web of Things specifications and related specifications;
-
-
to gather comments and questions in Japanese about those specifications;
-
- to collect information about specific use cases in Japanese for technologies defined in those specifications;
- and
-
-
- to report the results of its activities as a group back to the Web of Things Working Group/Interest Group, the
- W3C membership, and the Web community.
-
- The mission of this group is to define a common protocol for communicating with connected devices over the web, to
- enable ad-hoc interoperability on the Web of Things.
-
-
-
Deliverables of the group may include use cases, requirements and specifications.
- This community group focuses on the design of Web-based Multi-Agent Systems (MAS) for deploying world-wide hybrid
- communities of people and artificial agents. It aims to develop a new class of 'Hypermedia MAS' (hMAS) aligned
- with Web Architecture, utilizing Linked Data and Semantic Web standards to enable uniform interaction among
- heterogeneous entities like people, devices, digital services, and knowledge repositories.
-
-
-
Chairs: Andrei Ciortea, Rem Collier, Antoine Zimmermann, Ege Korkan
+ New to the Web of Things? These beginner-friendly community-based tutorials will help you understand the core
+ concepts behind WoT and get you up to speed quickly. Whether you're a developer, researcher, or just curious, these
+ are the best place to start.
+
-
Web of Things in a Nutshell
-
-
-
- Typically, in classical IoT projects, developers have to face a challenging situation. They have to understand a
- heterogeneous technology landscape consisting of diverse IoT systems and services from different vendors and
- manufacturers. This diversity includes variations in communication protocols, data models for payload data
- exchange, and security requirements. IoT applications are usually developed using high effort applied to a
- narrow and specific use case. During their lifetime, such applications are difficult to extend, maintain or
- reuse.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- The Web of Things (WoT) provides a set of standardized technology building blocks that help to simplify IoT
- application development by following the well-known and successful Web paradigm. This approach increases
- flexibility and interoperability, especially for cross-domain applications, as well as enabling reuse of
- established standards and tools. WoT unlocks commercial potential being held back by IoT fragmentation
-
-
- Please read the
- WoT Architecture document to get more background on WoT
- use cases and basic paradigms.
-
-
-
-
-
-
-
WoT Interactions
-
-
-
- WoT introduces a simple interaction abstraction based on properties, events, and actions. Any IoT network
- interface can be described in terms of this abstraction. By using this abstraction, applications have a common
- anchor to retrieve an IoT service’s metadata as well as way to understand what and how the data and an IoT
- services' functions can be accessed.
-
-
- Please read here
- to get more background about the properties-action-event paradigm.
-
-
-
-
-
-
-
-
-
-
WoT Building Blocks
-
-
-
-
-
-
- An IoT device's metadata, including all information needed to enable this common abstraction, is documented in
- what is called WoT Thing Description (TD). The TD is a central building block in the W3C Web of
- Things and can be considered as the entry point of an IoT instance (much like the index.html of a Web site). It
- provides information on which data and functions are provided, which protocol is used, how data is encoded and
- structured, and security mechanism is used to control access, and further machine-readable and human-readable
- metadata. A TD is expressed in JSON-LD and can be provided by an IoT device itself or hosted externally in a
- repository such as a TD Directory.
-
-
- Please read
- here
- to get more background on the WoT Thing Description.
-
-
-
-
-
-
-
-
-
- In general, WoT is a protocol agnostic approach and provides a common mechanism to define how specific protocols
- such as MQTT, HTTP, CoAP or Modbus can be mapped to the WoT’s interaction properties-action-event abstraction.
-
-
- This mapping and protocol specific metadata are provided by the WoT Binding Templates. A
- binding template for a specific protocol provides a guideline how a client can activate each WoT interaction
- abstraction through a corresponding network-facing interface for that protocol.
-
-
- Please read
- here
- to get more background on WoT Binding Templates.
-
-
-
-
+
+
+
+
+
What is WoT?
+
+
+
+ A gentle introduction to the Web of Things. Learn what WoT is all about, why it matters, and how it connects
+ everyday devices to the Web using open standards.
+
- The (optional) WoT Scripting API building block defines an ECMAScript (JavaScript) API that
- closely follows the WoT Thing Description specification and supports the WoT interaction abstraction. It defines
- the interface between behavior implementations and a scripting-based WoT runtime. Please note however that
- implementations of WoT are not limited to scripting environments. Programming language APIs in Java or C/C++ can
- also be derived from the WoT Scripting API.
-
-
- Please read
- here
- to get more background on the WoT Scripting API.
-
+
+
+
+
+
Thing Description 1.1 Explainer
+
+
+
+ Understand the Thing Description (TD) — the cornerstone of WoT. This explainer walks you through how TDs
+ describe the capabilities, interfaces, and metadata of connected devices in a machine-readable format.
+
- The Web of Things also provides guidance on WoT Security and Privacy. WoT provides guidelines
- for the secure implementation and configuration of Things. Security and privacy should be considered in any
- system implementing W3C WoT.
-
-
- Please read
- here
- to get more background on WoT Security and Privacy.
-
+
+
+
+
+
WoT Discovery Explainer
+
+
+
+ Learn how devices and services find each other on the Web of Things. This explainer covers the WoT Discovery
+ mechanism, which makes it easy to search for and locate Thing Descriptions across networks.
+
+ The W3C WoT Working Group publishes and maintains a suite of documents that define the Web of Things. These are
+ categorized into normative specifications and informative deliverables. The tables below provide an overview of our
+ current deliverables and their publication status.
+
- The W3C WoT Interest Group (IG) plays a complementary role to the Working Group. The IG organizes and runs PlugFests
- to evaluate the current working assumptions, reaches out and collaborates with interested organizations, vendors,
- and communities, and explores new areas to identify work that is ready for transfer to the W3C Recommendation Track
- (i.e., any W3C Working Group).
-
- The Web of Things (WoT) Interest Group (IG) conducts some of its work via the following task forces.
- See each task force page for details about specific work.
-
+ The Web of Things (WoT) counters IoT fragmentation by extending proven Web standards. Through standardized metadata
+ and reusable building blocks, W3C WoT enables seamless integration across IoT platforms and application domains.
+
+
+
+
+
+
Web of Things in a Nutshell
+
+
+
- The Web of Things (WoT) seeks to counter the fragmentation of the IoT by using and extending existing,
- standardized Web technologies. By providing standardized metadata and other re-usable technological building
- blocks, W3C WoT enables easy integration across IoT platforms and application domains.
+ In typical IoT projects, developers face a fragmented landscape of proprietary systems, incompatible
+ communication protocols, differing data models, and varying security requirements. Applications built this way
+ demand high effort for narrow use cases and become difficult to extend, maintain, or reuse over time.
+
+
+
+
+
+
+
+
+
+ WoT provides standardized building blocks that simplify IoT application development by applying the
+ well-established Web paradigm. This approach boosts flexibility and interoperability—especially for cross-domain
+ scenarios—while enabling reuse of proven standards and tooling. WoT unlocks the commercial potential held back
+ by IoT fragmentation.
+
- Get more background about the Web of Things in the Documentation area and check out
- upcoming Events.
+ WoT introduces a simple, universal interaction model based on
+ Properties, Actions, and Events. Any IoT network interface
+ can be described using this abstraction, giving applications a common way to discover an IoT service's metadata
+ and understand how to access its data and functions—regardless of the underlying technology.
+ The WoT Thing Description (TD) is the central building block of the Web of Things. Much like an
+ index.html serves as a website's entry point, a TD documents everything needed to interact with an
+ IoT device: available data and functions, communication protocols, payload encoding, and security mechanisms.
+ Expressed in JSON-LD, TDs can be served directly by devices or hosted in a TD Directory.
+
+ WoT is protocol-agnostic. WoT Binding Templates define how specific protocols—such as MQTT,
+ HTTP, CoAP, or Modbus—map onto the Properties–Actions–Events abstraction. Each binding template provides a
+ guideline for clients to activate WoT interactions through the corresponding network interface.
+
+ The WoT Scripting API defines an ECMAScript (JavaScript) API that mirrors the Thing Description
+ specification and supports the WoT interaction model. It provides the interface between behavior implementations
+ and a scripting-based WoT runtime. While the API is defined for JavaScript, equivalent APIs can be derived for
+ Java, C/C++, or other languages.
+
+ WoT Security and Privacy guidelines help ensure the secure implementation and configuration of
+ Things. Security and privacy considerations are essential for any system implementing W3C WoT.
+
diff --git a/docs/participate/community-groups/index.html b/docs/participate/community-groups/index.html
new file mode 100644
index 0000000..ba33e64
--- /dev/null
+++ b/docs/participate/community-groups/index.html
@@ -0,0 +1,108 @@
+---
+layout: default
+title: W3C WoT – Community Groups
+group: 'navigation'
+---
+
+
+ {% include breadcrumbs.html %}
+
W3C WoT – Related Community Groups
+
The following Community Groups support the WoT activities
+
+
+
+
+
+
Web of Things Community Group
+
+
+
+ The aim of the Web of Things Community Group (CG) is to accelerate the adoption of Web technologies as a
+ basis for enabling services for the combination of the Internet of Things with rich descriptions of things
+ and the context in which they are used.
+
The mission of the Web of Things Japanese Community Group includes the following:
+
+
+ to facilitate focused discussion in Japanese on the Web of Things specifications and related
+ specifications;
+
+
to gather comments and questions in Japanese about those specifications;
+
+ to collect information about specific use cases in Japanese for technologies defined in those
+ specifications; and
+
+
+ to report the results of its activities as a group back to the Web of Things Working Group/Interest Group,
+ the W3C membership, and the Web community.
+
+ The mission of this group is to define a common protocol for communicating with connected devices over the
+ web, to enable ad-hoc interoperability on the Web of Things.
+
+
Deliverables of the group may include use cases, requirements and specifications.
+ This community group focuses on the design of Web-based Multi-Agent Systems (MAS) for deploying world-wide
+ hybrid communities of people and artificial agents. It aims to develop a new class of 'Hypermedia MAS'
+ (hMAS) aligned with Web Architecture, utilizing Linked Data and Semantic Web standards to enable uniform
+ interaction among heterogeneous entities like people, devices, digital services, and knowledge repositories.
+
+
Chairs: Andrei Ciortea, Rem Collier, Antoine Zimmermann, Ege Korkan
diff --git a/docs/cg/template.html b/docs/participate/community-groups/template.html
similarity index 100%
rename from docs/cg/template.html
rename to docs/participate/community-groups/template.html
diff --git a/docs/participate/index.html b/docs/participate/index.html
new file mode 100644
index 0000000..a1c1b03
--- /dev/null
+++ b/docs/participate/index.html
@@ -0,0 +1,76 @@
+---
+layout: default
+title: Participate
+group: 'navigation'
+---
+
+
+
Participate in the W3C Web of Things
+
+ The W3C Web of Things (WoT) is defined and refined by experts worldwide. Get involved by joining the
+ Working Group to drive standards, or the Community Groups to discuss with adopters and incubate ideas.
+
+ The Web of Things (WoT) groups meet during the W3C's annual Technical Plenary week and additional face-to-face
+ meetings are scheduled by the participants that happen 2 times a year. Moreover, the work items are prototyped and
+ tested in WoT IG PlugFests that are scheduled for the weekend or week before the face-to-face meetings.
+
diff --git a/docs/participate/working-group/index.html b/docs/participate/working-group/index.html
new file mode 100644
index 0000000..6445a6b
--- /dev/null
+++ b/docs/participate/working-group/index.html
@@ -0,0 +1,165 @@
+---
+layout: default
+title: Working Group
+group: "navigation"
+---
+
+
+ {% include breadcrumbs.html %}
+
W3C WoT – Working Group
+
+ The W3C WoT Working Group (WG) is tasked to create standards-track specifications and test suites. To ensure
+ royalty-free Web standards, participants must be W3C and WoT WG Members and acknowledge the W3C Patent Policy.
+
+ The W3C WoT Interest Group (IG) plays a complementary role to the Working Group. The IG organizes and runs PlugFests
+ to evaluate the current working assumptions, reaches out and collaborates with interested organizations, vendors,
+ and communities, and explores new areas to identify work that is ready for transfer to the W3C Recommendation Track
+ (i.e., any W3C Working Group).
+
+ The Web of Things (WoT) Interest Group (IG) conducts some of its work via the following task forces.
+ See each task force page for details about specific work.
+
diff --git a/docs/participate/working-group/interest-group/task-forces/tf-marketing/index.html b/docs/participate/working-group/interest-group/task-forces/tf-marketing/index.html
new file mode 100644
index 0000000..03e4dcf
--- /dev/null
+++ b/docs/participate/working-group/interest-group/task-forces/tf-marketing/index.html
@@ -0,0 +1,69 @@
+---
+layout: default
+title: Marketing Task Force
+group: "navigation"
+---
+
+ {% include breadcrumbs.html %}
+
W3C WoT – Marketing Task Force
+
The WoT Marketing task force is responsible for reaching out and collaborating with the community to increase the
+ adoption of the WoT. The Marketing Task Force works on promoting the W3C Web of Things in different ways such
+ as Web presence, Social Media presence, and more.
+
+
Status: Active
+
+
People
+
+
TF-Lead:
+
+ Ege Korkan (Siemens AG)
+
+
+
+
+
Tasks
+
+ The Marketing Task Force aims to reach out and support the wide Web of Things community.
+ Our charter contains the goals for a certain period of time.
+ The overall tasks of the task force are:
+
+
Maintaining the web page
+
Creating visual materials such as:
+
+
Powerpoint templates
+
Figures
+
Animation
+
Videos
+
+
+
Establishing the representation of WoT like a brand identity at:
+
+
WoT Repositories
+
WoT Web Page
+
WoT Wiki Pages
+
WoT Twitter account and other possible social channels
+
+
+
Reaching out to the wide community through:
+
+
Social Media
+
Web Pages
+
Blog Posts
+
Promotional Text and Videos
+
Explainer Text and Videos
+
Tutorial Text and Videos
+
+
+
Assuring consistent style for all the points above
\ No newline at end of file
diff --git a/docs/activities/task-forces/tf-plugfest/index.html b/docs/participate/working-group/interest-group/task-forces/tf-plugfest/index.html
similarity index 96%
rename from docs/activities/task-forces/tf-plugfest/index.html
rename to docs/participate/working-group/interest-group/task-forces/tf-plugfest/index.html
index ff2c86b..fccf567 100644
--- a/docs/activities/task-forces/tf-plugfest/index.html
+++ b/docs/participate/working-group/interest-group/task-forces/tf-plugfest/index.html
@@ -5,6 +5,7 @@
---
+ {% include breadcrumbs.html %}
W3C WoT – Plugfest/Testing Task Force
The WoT Plugfest/Testing task force is responsible for organizing the Web of Things (WoT) Plugfests and also for
diff --git a/docs/participate/working-group/interest-group/task-forces/tf-usecases/index.html b/docs/participate/working-group/interest-group/task-forces/tf-usecases/index.html
new file mode 100644
index 0000000..cf5f8f8
--- /dev/null
+++ b/docs/participate/working-group/interest-group/task-forces/tf-usecases/index.html
@@ -0,0 +1,51 @@
+---
+layout: default
+title: Use Case Task Force
+group: 'navigation'
+---
+
+
+ {% include breadcrumbs.html %}
+
W3C WoT – Use Case Task Force
+
The WoT Use Case task force is responsible for
+ collecting use cases for WoT and extracting requirements.
+ Use cases can include both specific vertical applications
+ as well as relevant horizontal technologies or other horizontal usage patterns.
+ Guests who are not WoT members but who have an interest in
+ specific vertical application domains, technologies, or usage patterns
+ are explicitly invited to engage with this task force to provide input.
+
+
Status: Active
+
+
WoT Use Cases and Requirements
+
+ The WoT Use Cases and Requirements document includes a catalog and taxonomy of use cases and a set of general
+ requirements extracted from an analysis of these use cases. These requirements are then used to drive the
+ development of other normative WoT specifications.
+
+
+
+
+
People
+
+
TF-Leads:
+
Tomoaki Mizushima (Internet Research Institute, Inc.), Michael McCool (Intel Corp.),
+
WoT Use Cases Co-Editors:
+
+ Michael McCool (Intel Corp.), Luca Barbato (Luminem Srl), Ege Korkan (Siemens AG), Tomoaki Mizushima (Internet
+ Research Institute, Inc.)
+
+
Previous Editors:
+
Michael Lagally (Oracle Corp.), Ryuichi Matsukura (Fujitsu Ltd.)
diff --git a/docs/participate/working-group/meetings/index.html b/docs/participate/working-group/meetings/index.html
new file mode 100644
index 0000000..efe1b29
--- /dev/null
+++ b/docs/participate/working-group/meetings/index.html
@@ -0,0 +1,73 @@
+---
+layout: default
+title: Web Conference Meetings
+group: 'navigation'
+---
+
+
+ {% include breadcrumbs.html %}
+
W3C WoT – Web Conference Meetings
+
+
+
+
+ We have grouped our weekly meetings in the table below. We also recommend you to use
+ the W3C calendar system
+ in order to download ICS files for all our meetings.
+
+ The Web of Things (WoT) Working Group conducts some of its work via task forces and uses a main wiki & call to provide an opportunity to
+ summarize and coordinate the activities of the various task forces. See each task force page for details about
+ specific work.
+
diff --git a/docs/participate/working-group/task-forces/tf-architecture/index.html b/docs/participate/working-group/task-forces/tf-architecture/index.html
new file mode 100644
index 0000000..227d3b8
--- /dev/null
+++ b/docs/participate/working-group/task-forces/tf-architecture/index.html
@@ -0,0 +1,46 @@
+---
+layout: default
+title: Architecture Task Force
+group: 'navigation'
+---
+
+
+ {% include breadcrumbs.html %}
+
W3C WoT – Architecture Task Force
+
The WoT Architecture task force is responsible for the
+ abstract architecture for the Web of Things.
+
+
Status: Suspended
+
+
WoT Architecture
+
+ The WoT Architecture specification describes the abstract architecture for the W3C Web of Things. It defines the
+ terminology that is used by all other WoT building blocks. The specification defines a conceptual framework that
+ can be mapped onto a variety of concrete deployment scenarios.
+
+
+
+
+
People
+
+
TF-Leads:
+
Michael Lagally (Oracle Corp.) and Michael McCool (Intel Corp.)
+
WoT Architecture Co-Editors:
+
+ Michael Lagally (Oracle Corp.), Ryuichi Matsukura (Fujitsu Ltd.), Michael McCool (Intel Corp.), and Kunihiko
+ Toumura (Hitachi, Ltd.)
+
diff --git a/docs/participate/working-group/task-forces/tf-discovery/index.html b/docs/participate/working-group/task-forces/tf-discovery/index.html
new file mode 100644
index 0000000..cb8e771
--- /dev/null
+++ b/docs/participate/working-group/task-forces/tf-discovery/index.html
@@ -0,0 +1,51 @@
+---
+layout: default
+title: Discovery Task Force
+group: 'navigation'
+---
+
+
+ {% include breadcrumbs.html %}
+
W3C WoT – Discovery Task Force
+
The WoT Discovery task force is responsible for
+ defining a distribution mechanism for WoT Thing Descriptions
+ that can be used to facilitate access to WoT Things and services
+ while supporting security and privacy.
+
+
Status: Suspended
+
+
WoT Discovery
+
+ The WoT Discovery specification defines a mechanism to provide access to WoT Thing Descriptions in both local
+ and global contexts. It uses a two-phase approach to take advantage of existing discovery mechanisms for "first
+ contact" but provides for authenticated web services to actually provide metadata in order to support security
+ and privacy goals. WoT Thing Descriptions can be retrieved from services running either on a Thing itself (that
+ is, directly from self-describing objects), or from a directory service that provides a searchable database of
+ WoT Thing Descriptions.
+
+
+
+
+
People
+
+
TF-Lead:
+
Michael McCool (Intel Corp.)
+
WoT Discovery Co-Editors:
+
+ Andrea Cimmino (Universidad Politécnica de Madrid), Michael McCool (Intel Corp.), Farshid Tavakolizadeh
+ (Fraunhofer-Gesellschaft), and Kunihiko Toumura (Hitachi, Ltd.)
+
diff --git a/docs/participate/working-group/task-forces/tf-profiles/index.html b/docs/participate/working-group/task-forces/tf-profiles/index.html
new file mode 100644
index 0000000..2d01002
--- /dev/null
+++ b/docs/participate/working-group/task-forces/tf-profiles/index.html
@@ -0,0 +1,45 @@
+---
+layout: default
+title: Profiles Task Force
+group: 'navigation'
+---
+
+
+ {% include breadcrumbs.html %}
+
W3C WoT – Profiles Task Force
+
The WoT Profiles task force is responsible for interoperability profiles for the Web of Things.
+
+
Status: Active
+
+
WoT Profiles
+
+ The WoT Profiles Specification defines a Profiling Mechanism and a set of WoT Profiles which enables out of the
+ box interoperability among things and devices. Out of the box interoperability implies that devices can be
+ integrated into various application scenarios without deep level adaptations. Typically only minor configuration
+ operations are necessary (such as entering a network key or IP address) to use the device in a certain scenario.
+ These actions can be done by anyone without specific training.
+
+
+
+
+
People
+
+
TF-Leads:
+
Luca Barbato (Invited Expert) and Ben Francis (Invited Expert)
+
WoT Profiles Co-Editors:
+
+ Michael Lagally (Oracle Corp.), Ben Francis (Invited Expert) Michael McCool (Intel Corp.), Ryuichi Matsukura
+ (Fujitsu Ltd.), Sebastian Kaebisch (Siemens AG), and Tomoaki Mizushima (Internet Research Institute, Inc.)
+
diff --git a/docs/participate/working-group/task-forces/tf-scripting/index.html b/docs/participate/working-group/task-forces/tf-scripting/index.html
new file mode 100644
index 0000000..93595ea
--- /dev/null
+++ b/docs/participate/working-group/task-forces/tf-scripting/index.html
@@ -0,0 +1,48 @@
+---
+layout: default
+title: Scripting API Task Force
+group: 'navigation'
+---
+
+
+ {% include breadcrumbs.html %}
+
W3C WoT – Scripting API Task Force
+
+ The WoT Scripting API task force is responsible for
+ specifying an application programming interface (API) representing
+ the WoT Interface that allows scripts to discover, invoke interactions with Things,
+ and expose interactions for locally defined Things.
+
+
Status: Active
+
+
Informative Deliverables
+
The WoT Scripting API TF has its own informative deliverable.
+
+
+
Web of Things (WoT) Scripting API
+
Scripting is an optional building block in WoT and it is typically used in gateways, hubs, or browsers
+ that are able to run a WoT Runtime and script management, providing a convenient way to define the
+ behavior of exposed Things, extend WoT support to new types of endpoints, orchestrate interactions among
+ multiple Things, and implement WoT applications.
+
+
+
+
+
People
+
+
TF-Lead:
+
Daniel Peintner (Siemens AG) and Cristiano Aguzzi (Invited Expert)
+
WoT Scripting API Co-Editors:
+
Zoltan Kis (Intel Corp.), Daniel Peintner (Siemens AG), and Cristiano Aguzzi (Invited Expert)
diff --git a/docs/participate/working-group/task-forces/tf-security/index.html b/docs/participate/working-group/task-forces/tf-security/index.html
new file mode 100644
index 0000000..2d6b75b
--- /dev/null
+++ b/docs/participate/working-group/task-forces/tf-security/index.html
@@ -0,0 +1,42 @@
+---
+layout: default
+title: Security Task Force
+group: 'navigation'
+---
+
+
+ {% include breadcrumbs.html %}
+
W3C WoT – Security Task Force
+
The WoT Security task force is responsible for
+ identifying and analyzing the security and privacy considerations of the
+ WoT and providing recommendations to support appropriate security technologies and
+ to mitigate security and privacy risks.
+
+
+
WoT Security and Privacy Guidelines
+
+ The WoT Security and Privacy Guidelines document defines general security and privacy concepts and terminology
+ for the W3C Web of Things, catalogs stakeholders and threats, and provides general guidance on best practices to
+ mitigate these threats.
+
+
+
+
+
People
+
+
TF-Lead:
+
Michael McCool (Intel Corp.)
+
WoT Security and Privacy Guidelines Co-Editors:
+
Elena Reshetova (Intel Corp.) and Michael McCool (Intel Corp.)
The WoT Thing Description task force is responsible for
+ defining the information model for WoT Thing metadata, its interpretation, and its
+ common representation. In addition, the task force covers WoT Binding Templates
+ topics to define the mapping from the abstract interaction model
+ used in the Thing Description metadata to concrete IoT protocols and payload encodings.
+
+
Status: Active
+
+
Normative Deliverable
+
+
WoT Thing Description 1.1
+
This document describes a superset of the features defined for Thing Description 1.0.
+ In general, this document describes the formal model of a Thing and its common representation in JSON-LD
+ 1.1.
+ It introduces a simple interaction model with Properties, Actions, and Events
+ to describe the capabilities of a Thing, including its data model,
+ communication protocols used, security mechanisms,
+ and other semantic metadata.
+ A WoT Thing Description defines a specific instance of a Thing.
+ The WoT Thing Description 1.1 also formally introduces the Thing Model concept that
+ describes sets of Things.
+ It has fewer restrictions than the Thing Description
+ and does not contain any instance-specific information.
+
+
+
Informative Deliverable
+
+
WoT Binding Templates
+
This document describes a set of vocabulary extensions to
+ the WoT Thing Description that make up the Binding Templates. Binding
+ Templates enable a Thing Description to be adapted to specific protocol
+ or data payload usages across different standards. This is done through additional
+ descriptive vocabulary that is used in the Thing Description.
+
+
+
+
+
People
+
+
TF-Lead:
+
+ Ege Korkan (Siemens AG) and
+ Michael Koster (Invited Expert)
+
+
WoT Thing Description Co-Editors:
+
+ Sebastian Kaebisch (Siemens AG),
+ Michael McCool (Intel Corp.),
+ Ege Korkan (Siemens AG)
+
+
WoT Binding Templates:
+
+ Michael Koster (Invited Expert),
+ Ege Korkan (Siemens AG)
+
diff --git a/docs/wg/index.html b/docs/wg/index.html
index 92e0b26..4b3aa5e 100644
--- a/docs/wg/index.html
+++ b/docs/wg/index.html
@@ -1,256 +1,15 @@
---
-layout: default
-title: W3C WoT – Working Group
-group: 'navigation'
+layout: null
---
-
-
W3C WoT – Working Group
-
- The W3C WoT Working Group (WG) is tasked to create standards-track specifications and test suites. To ensure
- royalty-free Web standards, participants must be W3C and WoT WG Members and acknowledge the
- W3C Patent Policy.
-
- The Web of Things (WoT) Working Group (WG) conducts some of its work via the following task forces.
- See each task force page for details about specific work.
-
- 
- 
- @wot@w3c.social
- 
+ 
- 
- 
- 
- 
+ 
-