[Network Service Discovery API] device type search

Hello,



Thank you for providing the Network Service Discovery API draft and its implementation.

We are reviewing Network Service Discovery API w/ the simple prototype. from the feedback of this prototype, we'd like to request the following functions into Network Service Discovery APIs.



- device type search and cross domain access

When we make a UPnP controller application, we believe that a controller typically searches by "deviceType" such as "urn:schemas-upnp-org:device:MediaRenderer:1" or "urn:schemas-upnp-org:device:MediaServer:1" at first rather than serviceType such as "urn:schemas-upnp-org:service:AVTransport".



This is because a controller tends to expose device list for user to select one to be controlled and presentation name, icon etc for the list belong to deviceType.



For the media renderer example, after locating a MediaRenderer deviceType to be controlled, a controller may use its AVTransport serviceType to control the media playback and also use the RenderingControl serviceType of the same device to control the rendering functions.



For this case, it will be better to be able to search by "deviceType" to ease a controller to get these two services from the device.



Likewise, other search target (ST) values alllowed in SSDP such as "ssdp:all", "upnp:rootdevice" and "uuid:<UUID>" should also be allowed in the Network Discovery API, shouldn't it?



We suppose all those are "service" in the sense of general term.

Therefore it seems natural to us that the Network Service Discovery API can discover UPnP deviceType.



If the above is a good idea, the cross domain should be allowed to access the UPnP device resources such as the device description page, the service description page, the device icon or etc in addition to than controlUrl written in the device description.



Thank you,



nao