- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Apr 2016 14:19:09 +0000
- To: public-secondscreen@w3.org
tidoust has just created a new issue for https://github.com/w3c/presentation-api: == Specify the algorithm for generating a presentation identifier == This idea has been raised a couple of times, including in: * #165 conflict description for uniquely identifying a presentation session, see https://github.com/w3c/presentation-api/issues/165#issuecomment-147452520 * #253 Have the receiving browsing context generate the presentation identifier? The presentation identifier needs to be unique across possible controlling and receiving browsing contexts that belong to the same local user environment. The best way to almost-guarantee the unicity of the presentation identifier is to specify the algorithm that the controlling user agent must follow to create an identifier. The usual reference for generating Universally Unique IDentifiers (UUID) seems to be RFC4122: https://tools.ietf.org/html/rfc4122 This may be overkill in our context. Nothing comes to mind but there may be other examples of specs that define a lightweight version of such an algorithm. Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/279 using your GitHub account
Received on Tuesday, 19 April 2016 14:19:13 UTC