W3C home > Mailing lists > Public > public-device-apis@w3.org > January 2011

RE: Action updates needed - ACTION-231 (Web Introducer prototyping)

From: Nilsson, Claes1 <Claes1.Nilsson@sonyericsson.com>
Date: Mon, 24 Jan 2011 17:24:14 +0100
To: "Frederick.Hirsch@nokia.com" <Frederick.Hirsch@nokia.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>, "tyler.close@gmail.com" <tyler.close@gmail.com>
Message-ID: <6DFA1B20D858A14488A66D6EEDF26AA34D487E0C7F@seldmbx03.corpusers.net>
Hi,

I have updated my simple prototype to include the possibility to access the device camera through a local web server. This works for Android v 2.2 or later. My Customer page is here: http://semccustomer.appspot.com/.

For more details see my post on the Web Introducer discussion page: http://groups.google.com/group/introducer/browse_thread/thread/f9db6a698e89b65c

This fulfills my ACTION-231.

Best regards
  Claes


> -----Original Message-----
> From: Nilsson, Claes1
> Sent: den 10 januari 2011 17:41
> To: 'Frederick.Hirsch@nokia.com'; public-device-apis@w3.org;
> 'tyler.close@gmail.com'
> Subject: RE: Action updates needed - ACTION-231
> 
> Hi,
> 
> Referring to mail from Tyler Close on January 5
> (http://lists.w3.org/Archives/Public/public-device-
> apis/2011Jan/0016.html) I have started some prototyping related to the
> Web Introducer.
> 
> Tyler has created an API/datatype specification and implementation for
> enabling a Customer to share a single hyperlink with a user-selected
> Provider, "The Bookmark Introducer".
> 
> I am trying the opposite, i.e. allowing a Web Application, "Customer",
> to receive from a Provider a link to data selected by the user. My
> intention is also to evaluate the web introducer concept for
> discovering and authorizing access to data from local device resources
> through local providers that connects to device HW resources.
> 
> My very simple prototype for allowing the user select an image to
> provide to a Customer is here: http://semccustomer.appspot.com/.
> Unfortunately I haven't yet had time to fix the local camera access yet
> so the current "local camera provider" is just a "dummy".
> 
> I suggest that Action-231 is kept open until local camera access
> through the Web Introducer is in place.
> 
> Regards
>   Claes
> 
> > -----Original Message-----
> > From: public-device-apis-request@w3.org [mailto:public-device-apis-
> > request@w3.org] On Behalf Of Frederick.Hirsch@nokia.com
> > Sent: den 4 januari 2011 22:54
> > To: public-device-apis@w3.org
> > Cc: Frederick.Hirsch@nokia.com;
> david.rogers@wholesaleappcommunity.com;
> > paddy@aplix.co.jp; BS3131@att.com; Laura.Arribas@vodafone.com;
> > tlr@w3.org; dzung.d.tran@intel.com
> > Subject: Action updates needed
> >
> > (a) The following open policy framework actions can probably be
> closed,
> > given  WG decisions regarding the policy framework [1]. Please
> indicate
> > any disagreement, hearing nothing I suggest we close them before next
> > week's call.
> >
> > ACTION-104	Add use case related to Domain spoofing and trust in
> the
> > network layer (ISSUE-37)	David Rogers	2010-03-17
> > 	securityUseCases
> >
> > ACTION-145	Provide an architectural flow for Policy Reqs	Bryan
> > Sullivan	2010-03-25	Policy Framework Requirements
> >
> > ACTION-188	Propose clarification language around prompting,
> involving
> > Paddy and James as needed	Laura Arribas	2010-06-16	Policy
> > Framework Requirements
> >
> > ACTION-200	Provide clarifications to framework document as well
> as to
> > address concerns raised by Suresh
> > http://lists.w3.org/Archives/Public/public-device-
> > apis/2010Jun/0235.html	Paddy Byers	2010-06-30	Policy Framework
> >
> > ACTION-218 Provide proposal for feature architecture text regarding
> web
> > and widgets cases for feature document	Paddy Byers	2010-07-21
> > 	Policy Framework
> >
> > ACTION-295	to outline social engineering threat, API entry
> hurdles to
> > websites	David Rogers	2010-11-11	Policy Framework
> >
> > (b) Should the following action be reassigned or closed (if moot)
> given
> > that Max is  not in DAP any more?
> >
> > ACTION-132		 look at messaging subscribe with filtering and
> > events	Max Froumentin	2010-03-25	messagingSubscribeFilter
> >
> > (c) Are the following very old actions completed or moot?
> >
> > ACTION-148		Compare user interaction input with what
> already
> > available in HTML5 / WebApps	Bryan Sullivan	2010-03-25	User
> > Interaction API
> >
> > ACTION-173		Implement privacy changes noted by alissa, see
> > http://lists.w3.org/Archives/Public/public-device-
> > apis/2010May/0072.html	Dzung Tran	2010-05-26	hidingIsHard
> >
> > ACTION-214		Request IETF community review of sysinfo API
> Last
> > Call WD through W3C/IETF liaison channel	Thomas Roessler	2010-
> 01-31
> > 	System Information and Events API
> >
> > (d) Is an update on our investigation related to REST possible, in
> > particular with respect to the following actions?
> >
> > ACTION-231		Look into what he can share re javascript-based
> > android prototype of PowerBox	Claes Nilsson	2010-07-22
> 	restfulAPIs
> >
> > ACTION-232		Coordinate with Tyler on exposing Contacts
> through
> > Powerbox	Robin Berjon	2010-08-05	restfulAPIs
> >
> > We may want to look at any more recent updates or thoughts on
> Powerbox.
> >
> > regards, Frederick
> >
> > Frederick Hirsch, Nokia
> > Co-Chair, W3C DAP Working Group
> >
> > [1] http://lists.w3.org/Archives/Public/public-device-
> apis/2010Nov/att-
> > 0047/minutes-2010-11-04.html#item08 (at end of section)
> >
> >
> >
Received on Monday, 24 January 2011 16:25:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:16 GMT