W3C home > Mailing lists > Public > public-device-apis@w3.org > August 2012

RE: Retrieve device information in Network Service Discovery draft

From: Jan Lindquist <jan.lindquist@ericsson.com>
Date: Tue, 28 Aug 2012 15:06:35 +0200
To: Rich Tibbett <richt@opera.com>
CC: "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <82276AE38FD87A4C9CF6C820AC5276EA3870AC569C@ESESSCMS0362.eemea.ericsson.se>
Hi Rich,

When I saw that service.config attribute I assumed it was related to the service descriptor and not the device descriptor. It was not in the example so I did not see how the models were identified.


-----Original Message-----
From: Rich Tibbett [mailto:richt@opera.com] 
Sent: den 28 augusti 2012 14:45
To: Jan Lindquist
Cc: public-device-apis@w3.org
Subject: Re: Retrieve device information in Network Service Discovery draft

Hi Jan,

Jan Lindquist wrote:
> Hello Rich,
> I enjoyed reviewing the latest draft "Network Service Discovery and 
> Messaging". My interpretation of the API is that it is strictly list 
> of services provided without details of the device or "device descriptor"
> in UPnP terms. In the last example there is an example of how a drop 
> down list of model can be used to select different devices. It is not 
> clear how this is achieved with the given API since first attribute it 
> simply "type".

The user interface aspects of this proposal are intended to be handled by the browser. When you request a service type the browser knows all of the details about which devices implement that service and can provide a UI to allow users to select a share a subset of those devices - displaying the device name, icon, etc - with the requesting web page.

> My recommendation is to add a means to list the equivalent of UPnP 
> device descriptor which includes information like friendly name, 
> manufacturer, model name, model information, etc.

This is already supported via NetworkService.config. This returns the full device descriptor for the currently authorized network service. We are unsure if this is a strictly necessary attribute to expose on NetworkServices. It is certainly not necessary for device communication but it does provide some meta context (i.e. friendly name, manufacturer, model name, model information, etc as you requested above) to the service that has been provided.

> Best regards,
> JanL
Received on Tuesday, 28 August 2012 13:07:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:41 UTC