Re: [presentation-api] list of displays: should it address display name, language, etc.?

I believe that the specification is silent on purpose here, to let 
implementers adjust their chrome and user experience as they see fit. 
For instance, a controlling user agent could choose to list displays 
that the user previously interacted with first, or sort displays it 
finds by proximity, or filter out displays that it deems not 
trustworthy, etc. In other words, the expectation is not that two 
controlling user agents will display the same list of available 
displays, and that they will appear in the same order.

The amount of information that the controlling user agent has on the 
available displays also depends on the discovery mechanism used under 
the hoods, which is out of scope of this specification. The user agent
 may be able to learn about all sorts of capabilities that the display
 supports, including locale support. Or it may not know much on top of
 the display name.

The spec could perhaps include some guidance about possible 
localization issues. I'm not clear how the display name could affect 
the actual implementation though. Do you have examples of issues that 
could arise, @aphillips ? For instance, is the problem that the user 
agent may not be able to render the name if the display name uses 
characters that are not supported by the user agent?

Side note: the list of displays is not identified using URLs. Each 
presentation display is associated with a list of URLs that it is 
compatible with, but it is not an identifier for the display. How the 
display gets identified is up to the implementation. It will probably 
be based on its IP address (possibly its MAC address on the LAN), or 
on some identifier exposed by the display itself.

-- 
GitHub Notification of comment by tidoust
Please view or discuss this issue at 
https://github.com/w3c/presentation-api/issues/315#issuecomment-225901496
 using your GitHub account

Received on Tuesday, 14 June 2016 14:36:19 UTC