W3C home > Mailing lists > Public > public-device-apis@w3.org > February 2010

RE: Contacts API typical use cases and privacy considerations

From: Dominique Hazael-Massieux <dom@w3.org>
Date: Fri, 19 Feb 2010 17:03:38 +0100
To: richard.tibbett@orange-ftgroup.com
Cc: public-device-apis@w3.org
Message-ID: <1266595418.3040.3154.camel@localhost>
Le vendredi 19 février 2010 à 16:33 +0100,
richard.tibbett@orange-ftgroup.com a écrit :
> We have a proposal to implement an <input type="file"> extension for
> Contacts [1] and I think we should move forward with this. There was
> little objection to the principal in that thread, only how it should
> actually be done technically. If you have objections please do reply to
> that thread. There is also a <device> placeholder in the HTML5 spec [2]
> and I think either tag could be suitable for the use cases you are
> suggesting.

I would distinguish the question on whether this needs to be
markup-based from the underlying browser-as-broker model.

(in other words, I think the objections that were raised were around the
proposed markup solution, but as you say, I don't think anybody brought
up objections to the brokering role of the browser in that context)

I actually think relying on a markup model for this case is likely to
create more difficulties than it solves in the short term (in particular
due to the need for a good fall-back model), and so I'm thinking that
providing an API entry point that would more or less replicate what we
expect from an <input type="contact"/> might be a better approach.

> Oh, and a final point is that this is only intended to cover the
> Contacts API initially. Other APIs should probably be assessed on a
> case-by-case basis...

Agreed, indeed.


> [1]
> http://lists.w3.org/Archives/Public/public-device-apis/2009Dec/0005.html
> [2]
> http://lists.w3.org/Archives/Public/public-device-apis/2009Dec/0217.html
Received on Friday, 19 February 2010 16:03:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:17 UTC