RE: Use <friendlyName> as a human-readable title for UPnP service

I realized that this issue about NSD was already filed. Also, the same proposal was submitted in past.

ISSUE-148: NetworkService.name definition in 8.2.2.4 incoherent with definition in 7.1 (a human-readable title for the service)
http://www.w3.org/2009/dap/track/issues/148

-***---***---***---***---***---***---***---***---***--***---***---***-
Tatsuya Igarashi　(Tatsuya.Igarashi@jp.sony.com<mailto:Tatsuya.Igarashi@jp.sony.com>)
Information Technology Development Div, R&D Platform
Sony Corporation



From: Igarashi, Tatsuya [mailto:Tatsuya.Igarashi@jp.sony.com]
Sent: Wednesday, September 18, 2013 8:49 AM
To: public-device-apis@w3.org
Subject: Use <friendlyName> as a human-readable title for UPnP service

Hi,

The latest editor’s draft describes that in the case of UPnP service the <serviceId> is set to the network service record's name property. But, the <serviceId>, e.g. “urn:schemas-upnp-org:service:RenderingControl”, is just to provide machines with the information to identify an instance of multiple UPnP services within a UPnP device. It does not provide human users with any information to recognize where the service is located in the local network.

Set network service record's name property to the string value of the first occurrence of the advertised service's <serviceId> sub-element.

I suggest to use the <friendyName> instead of the <serviceId>. As per definition of the name attribute of network service record, it enables users to select a target UPnP service from a menu list. e.g. a list of physical devices.

The name attribute represents a human-readable title for the service.

Thank you.

-***---***---***---***---***---***---***---***---***--***---***---***-
Tatsuya Igarashi　(Tatsuya.Igarashi@jp.sony.com<mailto:Tatsuya.Igarashi@jp.sony.com>)
Information Technology Development Div, R&D Platform
Sony Corporation