W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2013

RE: [discovery-api] Adding user opt-in UI non-normatively to the spec

From: Igarashi, Tatsuya <Tatsuya.Igarashi@jp.sony.com>
Date: Wed, 6 Nov 2013 18:35:54 +0900
To: Rich Tibbett <richt@opera.com>, Device APIs Working Group <public-device-apis@w3.org>
Message-ID: <DAB1CC3FAB54D3438F667F8E7B7599A20217C92A3408@JPTKYXMS218.jp.sony.com>
Hi Rich,

Is the UI of the two png images are when the promise of NSD is invoked? 

If yes, it must be confusing for users the UI depends on user-agents. A user-agent shows the device list as your UI, another does the service list, other shows service-types.  The popup UI by user-agent would also impact on how an author of web application desigs its UI. 

I think UI design is completely informative, but how information should be shown at the promise of NSD should be normative.

-***---***---***---***---***---***---***---***---***--***---***---***-
Tatsuya Igarashi (Tatsuya.Igarashi@jp.sony.com) 
Information Technology Development Div, R&D Platform
Sony Corporation




-----Original Message-----
From: Rich Tibbett [mailto:richt@opera.com] 
Sent: Tuesday, November 05, 2013 6:44 PM
To: Device APIs Working Group
Subject: [discovery-api] Adding user opt-in UI non-normatively to the spec

Hi,

Whenever discussion of the Network Services Discovery API comes up outside this group it is usually followed by some level of confusion on how 'user authorization opt-in' UI is intended to be implemented (i.e. how users ultimately choose the network services to share with a web page).

While it is generally a good idea for W3C specs not to dive too deeply in to UI specifics within specifications it may still be a good idea to add a basic opt-in UI/UX example to the spec in a non-normative annex.

The UI/UX suggestion that I'm proposing to add to the spec is:

http://people.opera.com/richt/release/specs/discovery/tpac2011_servicediscovery_ui_1.png

http://people.opera.com/richt/release/specs/discovery/tpac2011_servicediscovery_ui_2.png


These mock-ups can be updated as necessary.

Are there any objections to adding this as a non-normative annex?
Alternatively, anyone else have alternative UI/UX proposals we should include instead here?

Best regards,

Rich


Received on Wednesday, 6 November 2013 09:36:35 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:01 UTC