-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial version of the interoperability document #175
Conversation
…cussion in issue w3c#153.
# Assess interoperability of Presentation API implementations | ||
|
||
This document discusses the interoperability of potential Presentation API implementations in particular interoperability | ||
between user agents in case of [2-UA implementations][2ua] and between user agents and wireless/dump displays in case of [1-UA implementations][1ua]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/dump/dumb/s?
* Remove TODO (fixed in PR w3c#176)
* **Discovery**: to discover presentation devices, the controlling user agent should use the same technology as the presenting | ||
user agent uses to advertise itself. **Potential technologies**: SSDP, mDNS or BLE (BLE Beacon) | ||
* **Launch**: after discovery, the controlling user agent should know how to launch a new presentation or join an existing one. | ||
Common message formats should be also used. **Potential technologies**: DIAL (uses SSDP for discovery), Google Cast (part of it). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should specifically call out the HBBTv 2.0 spec (referencing GH Issue #67). User agents that support it will be able to present arbitrary URLs (not just pre-installed DIAL applications).
@louaybassbouss, thank you for drafting an initial version of the interoperability document. As I have some time now, I will merge this and make some of the suggested changes above. |
Initial version of the interoperability document
thx @mfoltzgoogle for your feedback completely agree with all your comments |
Initial version of the interoperability document according to the discussion in issue #153.