Re: WoT device HW id

> On 3 Oct 2016, at 10:00, Robert Gallas <gallas.robert@gmail.com> wrote:
> 
> Hi all
> 
> One of the use case for platform developers will be to match discovered WoT device with its real world counterpart to build physical topologies. For example deployment of hundreds of temperature sensors. What is the recommended way to pair physical WoT server with discovered device? 
> 
> Should solution for this usecase be dependent on https://schema.org/serialNumber <https://schema.org/serialNumber> only, or is there a plan to include hw device id to TD structure as a unique identifier?

Device identifiers are an interesting topic for discussion. The ability to securely configure and update the software for large numbers of identical sensors is an important use case. These sensors may be exposed as individual things, or as a composite thing. The former would be appropriate for say street lighting, where each light is connected to the cloud via a LPWAN.  The latter could be appropriate when the devices form a peer to peer sensor network that is connected to the cloud via a single gateway, where the data from the collection of sensors is multiplexed before being streamed.  Different kinds of devices may necessitate different kinds of device ID, so the Web of things should be agnostic as to the details of how device IDs are defined and managed.  There are further challenges relating to knowing the software environment so that updates can be checked for their compatibility.   The ability to check for compatibility is also an issue when matching suppliers and consumers of services, e.g. on an open market of services.

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