W3C home > Mailing lists > Public > public-wot-wg@w3.org > July 2017

Re: Project Things by Mozilla and the Web Thing API

From: Kis, Zoltan <zoltan.kis@intel.com>
Date: Thu, 13 Jul 2017 13:10:08 +0300
Message-ID: <CANrNqUdXWj7qkM=TAjyhxAoXQ4MJV1h8VSb-bt6+DiOi+HdsKg@mail.gmail.com>
To: Benjamin Francis <bfrancis@mozilla.com>
Cc: public-wot-ig <public-wot-ig@w3.org>, "public-wot-wg@w3.org" <public-wot-wg@w3.org>
Hi Ben,

I agree with the goal of making TDs more Web-developer friendly, with core
vocabulary and then extensions.

Also, the gateway concept looks sound. However, I'd be interested in how
far can we go with protocol bindings. Packaged SW update is less of an
issue for a gateway, but it's probably more difficult for an end device
that needs re-flashing and it's already deployed.

Scripting is an optional building block for WoT, and IMHO it's not in
conflict with your goals about web interfaces and SW libraries. You could
consider it as an example, rather than _the_ way to do Things.

Implementations may differ, but the use cases and context stay the
same. Therefore,
IMHO it still makes sense to standardize a WoT Scripting API for
JavaScript/TypeScript. They do work against a web interface (the WoT

Also, it makes sense to work on and have examples on script deployment
(Manager Thing), related use cases, functionality, vocabulary etc.

Similarly, the WoT interface concepts can be applied to access to system
specific functionality. TD's can be defined for a wide range of

Security, privacy, access rights, policies, "manifests" (SW extensions),
etc are work in progress where Mozilla's input would be beneficial.

Best regards,
Received on Thursday, 13 July 2017 10:10:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:27:47 UTC