Re: Presentation API and non-screen devices

Hi Francois,

I agree with keeping the focus on the screens for now. Supporting
application specific content (I think you refer to DIAL and similar cases,
for instance) already raises many questions that are not completely
answered yet (e.g. screen filtering, unified messaging protocol, etc).
Extending the API to support significantly different types of devices at
this point feels too early.

Thanks,
Anton.

On Thu, Sep 25, 2014 at 4:50 PM, Francois Daoust <fd@w3.org> wrote:

> Hi again,
>
> Several people I talked to raised the fact that the Presentation API could
> easily address devices without "screen". A similar comment came up during
> the Advisory Committee review.
>
> The fact is that the notion of screen is not a precise one. In the 2UA
> case, nothing really mandates the presence of a real screen attached to the
> second user agent. This is even more the case for application-specific
> content (provided the controlling browser supports it), where the second
> device may not support HTML. To that extent, the Presentation API already
> supports devices without screens.
>
> The group has been focusing on scenarios that involve screens and I think
> that it is a Good Thing. Extending the scope to cover other types of
> devices could introduce additional requirements that could be hard to
> address, at least in this iteration of the spec (e.g. the possible need to
> specify the "type" of device being targeted). So I would rather stick to
> "screens" to start with. If successful, the working group could always
> re-charter to extend its scope.
>
> I'd like to get your views on the topic though. Is this the general
> feeling or do you have other views?
>
> Thanks,
> Francois.
>
>