- From: Tran, Dzung D <dzung.d.tran@intel.com>
- Date: Fri, 20 Nov 2009 08:58:32 -0800
- To: Nick Lothian <nlothian@educationau.edu.au>, "public-device-apis@w3.org" <public-device-apis@w3.org>
We are looking at Gears as one of the model to follow. We will definitely look at the streaming model. We are currently reworking the requirements and use cases. We will send it out for comments in the next week. Thanks Dzung Tran, -----Original Message----- From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of Nick Lothian Sent: Thursday, November 19, 2009 06:21 PM To: public-device-apis@w3.org Subject: Camera API requirements Hi All, I've been following with some interest the work on the Camera APIs, and I'm slightly concerned that you may be missing a class of user of that API who have their own requirements which don't appear to be met by some of the proposals so far. I'm interested in doing augmented reality type applications in HTML5, similar to how FLARKit works in Flash (http://www.libspark.org/wiki/saqoosha/FLARToolKit/en). Presently I'm working using VLC streaming and a proxy, which isn't really an option for most end users. I believe the best way to do this is to have access to the video output of the camera. This requirement appears to be met by the Google Gears proposed spec (http://code.google.com/p/gears/wiki/CameraAPI), but doesn't seem to be a priority in the "upload"-type proposals. Having said that, I think that approach (1b) in http://lists.w3.org/Archives/Public/public-device-apis/2009Nov/0132.html could possibly work for me, but in my case I'm not at all interested in the upload capabilities. I suspect the browser UI for that ("Upload an image or video") would be somewhat unsuitable. The general approach proposed as (2) in the above link would be much more suitable for my requirements. Anyway, I realize this is early in the process, and perhaps this feedback is premature. I hope that it can be of some use anyway. Regards Nick Lothian IMPORTANT: This e-mail, including any attachments, may contain private or confidential information. If you think you may not be the intended recipient, or if you have received this e-mail in error, please contact the sender immediately and delete all copies of this e-mail. If you are not the intended recipient, you must not reproduce any part of this e-mail or disclose its contents to any other party. This email represents the views of the individual sender, which do not necessarily reflect those of Education.au except where the sender expressly states otherwise. It is your responsibility to scan this email and any files transmitted with it for viruses or any other defects. education.au limited will not be liable for any loss, damage or consequence caused directly or indirectly by this email.
Received on Friday, 20 November 2009 16:59:41 UTC