W3C home > Mailing lists > Public > public-device-apis@w3.org > September 2012

RE: CfC: remove search from Pick Contacts Web Intent - please respond by 25 Sept 2012

From: Jungkee Song <jungkee.song@samsung.com>
Date: Thu, 20 Sep 2012 20:45:44 +0900
To: "'SULLIVAN, BRYAN L'" <bs3131@att.com>, Frederick.Hirsch@nokia.com
Cc: public-device-apis@w3.org, Frederick.Hirsch@nokia.com
Message-id: <011d01cd9725$77b46e70$671d4b50$%song@samsung.com>
> From: SULLIVAN, BRYAN L [mailto:bs3131@att.com]
> Sent: Thursday, September 20, 2012 10:19 AM
> I have a concern though that the UX will suffer because the app cannot
> give a hint to the Intent as to which contact it is interested in, forcing
> the use to re-enter the search terms. Is there an alternate approach under
> this proposal, through which the app can optimize the UX by providing
> search hints?

Other than the "ContactIntentExtras" dictionary, we don't have any such
options. However, the more I am mulling it over, the more I am leaning to
removing it. I feel like optimizing the UX with previous user action is
something that should be achieved by Web Intents semantic rather than
application level optional information. [1]

My original concern was there should be some way for users to restrict the
fields that they expect to retrieve mainly due to privacy reason. However,
it seems fine if the service page that the user selected would provide all
the search and filtering options in its UX. In principle, based on the
nature of Web Intents, it would be better not putting additional constraints
on both client and service.

As the CFC is due on 25th, let me think it over before I raise my hand. ;)
Please share your opinions!

[1] http://lists.w3.org/Archives/Public/public-web-intents/2012Sep/0023.html


> Thanks,
> Bryan Sullivan
> On Sep 20, 2012, at 2:32 AM, "Frederick.Hirsch@nokia.com"
> <Frederick.Hirsch@nokia.com> wrote:
> On today's DAP teleconference  [1] we discussed removing search from the
> Pick Contacts Intent draft [2].  Our discussion included a number of
> reasons, including the fact that service providers may be better
> positioned to offer integration of search with a meaningful and familiar
> user interface, that matching depends on semantics that may not be
> immediately obvious and may be coupled to the service, and a general
> desire to simplify the specification.
> Specifically this would mean removing the ContactIntentExtras dictionary
> definition (4.1.1) and its use case (and would also require an update to
> Example 1).
> This is a Call for Consensus (CfC) to remove this search functionality
> from the Pick Contacts Intent draft.  Support with a +1 to the list is
> preferred, silence will be considered agreement, concern should be
> expressed to the list.  Please respond by 25 Sept 2012.
> Thanks
> regards, Frederick
> Frederick Hirsch, Nokia
> Chair, W3C DAP Working Group
> [1] http://lists.w3.org/Archives/Public/public-device-apis/2012Sep/att-
> 0096/minutes-2012-09-19.html#item03
> [2] updated editors draft, http://dvcs.w3.org/hg/dap/raw-
> file/tip/contacts/Overview.html
> For tracker this completes ACTION-576
Received on Thursday, 20 September 2012 11:46:18 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:55 UTC