Re: Draft of Second Screen Presentation Working Group Charter available (was: Heads-Up: Plan for Working Group on Second Screen Presentation)

On Thu, May 15, 2014 at 11:02 AM, mark a. foltz <mfoltz@google.com> wrote:

> MarkW,
>
> Lines 234-236 read  "The user agent is responsible for determining which
> secondary displays are compatible with the content that is requested to be
> shown through the API" which I think addresses your first suggestion.
>

​Pretty much, yes, except in the very narrow sense that my concern is to be
clear that the availability of compatible displays can be discovered by the
web page *before* requesting that content be shown, so as to drive the
showing - or not - of the appropriate UI element.

You could satisfy the text in 234-236 by having the UA return an error when
a page tries to show incompatible content, but this would not be a great
user experience.

Anyway, I can live with the text as it stands for the proposed Charter​


> For the second suggestion, do you see this as something that must be
> addressed in the charter, or can it be addressed through the evolution of
> the API? (My assumption is that once the charter is agreed upon the
> currently proposed API will be re-examined to match the updated scope and
> deliverables.)
>

​No, that was not a comment against the charter, but just to make it clear
where the existing API proposal is missing a capability needed to address
the first point.

...Mark​



>
> If the former I welcome a pull request with what phrasing makes sense to
> you :)
>
> m.
>
>
>
>
> On Thu, May 15, 2014 at 8:42 AM, Mark Watson <watsonm@netflix.com> wrote:
>
>> Hi MarkF, all,
>>
>> In "API and associated specification", where we say "An API to allow a
>> web application to request display of web content on a connected display,
>> with a means to communicate with and control the web content from the
>> initiating page and other authorized pages", I think we should explicitly
>> add something like "and a means to discover when a display capable of
>> rendering the web content is available".
>>
>> This is the major requirement that is not presently supported by the API
>> draft: there is no way at present for the web page to determine whether it
>> should render the icon that shows the user a capable display is available
>> (and we have decided it should be the page that renders that icon, not the
>> UA).
>>
>> ...Mark
>>
>>
>> On Thu, May 15, 2014 at 1:09 AM, Rottsches, Dominik <
>> dominik.rottsches@intel.com> wrote:
>>
>>> Hi MarkF,
>>>
>>> On 14 May 2014, at 23:02, mark a. foltz <mfoltz@google.com> wrote:
>>>
>>> > I pushed two more commits addressing your comments, […]
>>>
>>> Thanks, the additional explanations on “authorised pages” look good to
>>> me. I’d leave it to Anssi to merge, but fine from my point of view.
>>>
>>> Dominik
>>>
>>>
>>>
>>
>
>
> --
> http://wiki/Main/OnlyCheckEmailTwiceADay
>