You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Becky Gibson <gi...@gmail.com> on 2013/01/18 22:20:04 UTC
Media APIs - some research and discussion
I was looking at the open issues for iOS and found some related to
capture/camera and media so I decided to see what the state of the latest
W3C APIs are for these things. It wasn't a pleasant journey!
There seem to be three apis that cover our camera/capture and media. Note
that the referenced URLs are to the latest published draft although many
have updated editor's drafts.
- Pick Media Intent ( http://www.w3.org/TR/gallery/) Pick stored Media
(images, audio, video) from various sources.
- HTML Media Capture (http://www.w3.org/TR/html-media-capture/) - HTML
form extension to allow user access to capture media from the device's via
still camera, video, microphone via the File upload control. Appears to
have replaced the Media Capture API (
http://www.w3.org/TR/2010/WD-capture-api-20100401/) since all links on
that page to Latest Published Draft and Latest Editor's Draft refer the the
HTML Media Capture spec and there is no longer any reference to the Media
Capture API on the Device API working group page (
http://www.w3.org/2009/dap/)
- Media Capture and Streams (http://www.w3.org/2009/dap/) Access to
multi media streams (video camera, microphone, stored media) from a device.
Thus, it seems that the Pick Media Intent would replace the Camera apis for
selecting existing images and video. It would add the ability to pick from
existing audio. Perhaps it is time to dive into the Web Intents spec and
consider implementation ....
HTML Media Capture allows capturing media but it is tied to the input
element. It also provides for uploading the captured data. This seems to
have replaced the Media Capture API that we implemented. I'm not sure how
we can incorporate this into Cordova as there are no real apis, just
attributes on the input element for the browser to implement and provide
the UI. Although this seems to be the only W3C mechanism for accessing
the still camera to capture an image!
The Media Capture and Streams could replace our Media and Capture Video
apis, but this is much more complicated. It also, in my opinion, doesn't
seem all that well baked at the moment with a fair amount of open issues
for defining some of the constants.
Thus, I was a bit overwhelmed at how to address some of the Media and
camera issues! I did discuss this briefly with Simon and was relieved
that he was considering the HTML apis for media as our solution for Media (
http://www.position-absolute.com/articles/introduction-to-the-html5-audio-tag-javascript-manipulation/).
Perhaps the best way to tackle our media is to normalize our media apis
around the HTML Media apis.
The point of this email? To capture my foray into the W3C Capture Apis
and perhaps start a discussion on the next steps for Camera, Capture and
Media apis.
My next foray is into the changes to Contacts - this is now a Web Intent as
well.
Re: Media APIs - some research and discussion
Posted by Simon MacDonald <si...@gmail.com>.
I guess someone forgot to tell the W3C. Sigh. I actually like how the
WebIntent lines up with Android's Intents.
Simon Mac Donald
http://hi.im/simonmacdonald
On Tue, Jan 22, 2013 at 5:20 AM, Plaquette, Paul
<pa...@intel.com> wrote:
> I think Google is going away from WebIntents.
>
>
> On Mon, Jan 21, 2013 at 3:01 PM, Brian LeRoux <b...@brian.io> wrote:
>
>> I think that spec is defunct and the functionality was removed from
>> Chrome recently.
>>
>> =.(
>>
>> On Sun, Jan 20, 2013 at 10:29 PM, Simon MacDonald
>> <si...@gmail.com> wrote:
>> > Just reading everything over and looking at the way things are going it
>> > seems like we should get the Web Intents API implemented. Looks like
>> there
>> > is already a shim implemented here:
>> >
>> > https://github.com/PaulKinlan/WebIntents
>> >
>> > with an APL license.
>> >
>> >
>> > Simon Mac Donald
>> > http://hi.im/simonmacdonald
>> >
>> >
>> > On Fri, Jan 18, 2013 at 4:20 PM, Becky Gibson <gibson.becky@gmail.com
>> >wrote:
>> >
>> >> I was looking at the open issues for iOS and found some related to
>> >> capture/camera and media so I decided to see what the state of the
>> latest
>> >> W3C APIs are for these things. It wasn't a pleasant journey!
>> >>
>> >> There seem to be three apis that cover our camera/capture and media.
>> Note
>> >> that the referenced URLs are to the latest published draft although many
>> >> have updated editor's drafts.
>> >>
>> >>
>> >> - Pick Media Intent ( http://www.w3.org/TR/gallery/) Pick stored
>> Media
>> >> (images, audio, video) from various sources.
>> >> - HTML Media Capture (http://www.w3.org/TR/html-media-capture/) -
>> HTML
>> >> form extension to allow user access to capture media from the
>> device's
>> >> via
>> >> still camera, video, microphone via the File upload control.
>> Appears to
>> >> have replaced the Media Capture API (
>> >> http://www.w3.org/TR/2010/WD-capture-api-20100401/) since all links
>> on
>> >> that page to Latest Published Draft and Latest Editor's Draft refer
>> the
>> >> the
>> >> HTML Media Capture spec and there is no longer any reference to the
>> >> Media
>> >> Capture API on the Device API working group page (
>> >> http://www.w3.org/2009/dap/)
>> >> - Media Capture and Streams (http://www.w3.org/2009/dap/) Access to
>> >> multi media streams (video camera, microphone, stored media) from a
>> >> device.
>> >>
>> >>
>> >> Thus, it seems that the Pick Media Intent would replace the Camera apis
>> for
>> >> selecting existing images and video. It would add the ability to pick
>> from
>> >> existing audio. Perhaps it is time to dive into the Web Intents spec
>> and
>> >> consider implementation ....
>> >>
>> >> HTML Media Capture allows capturing media but it is tied to the input
>> >> element. It also provides for uploading the captured data. This
>> seems to
>> >> have replaced the Media Capture API that we implemented. I'm not sure
>> how
>> >> we can incorporate this into Cordova as there are no real apis, just
>> >> attributes on the input element for the browser to implement and provide
>> >> the UI. Although this seems to be the only W3C mechanism for accessing
>> >> the still camera to capture an image!
>> >>
>> >> The Media Capture and Streams could replace our Media and Capture Video
>> >> apis, but this is much more complicated. It also, in my opinion,
>> doesn't
>> >> seem all that well baked at the moment with a fair amount of open issues
>> >> for defining some of the constants.
>> >>
>> >> Thus, I was a bit overwhelmed at how to address some of the Media and
>> >> camera issues! I did discuss this briefly with Simon and was relieved
>> >> that he was considering the HTML apis for media as our solution for
>> Media (
>> >>
>> >>
>> http://www.position-absolute.com/articles/introduction-to-the-html5-audio-tag-javascript-manipulation/
>> >> ).
>> >> Perhaps the best way to tackle our media is to normalize our media
>> apis
>> >> around the HTML Media apis.
>> >>
>> >> The point of this email? To capture my foray into the W3C Capture Apis
>> >> and perhaps start a discussion on the next steps for Camera, Capture and
>> >> Media apis.
>> >>
>> >> My next foray is into the changes to Contacts - this is now a Web
>> Intent as
>> >> well.
>> >>
>> ---------------------------------------------------------------------
>> Intel Corporation SAS (French simplified joint stock company)
>> Registered headquarters: "Les Montalets"- 2, rue de Paris,
>> 92196 Meudon Cedex, France
>> Registration Number: 302 456 199 R.C.S. NANTERRE
>> Capital: 4,572,000 Euros
>>
>> This e-mail and any attachments may contain confidential material for
>> the sole use of the intended recipient(s). Any review or distribution
>> by others is strictly prohibited. If you are not the intended
>> recipient, please contact the sender and delete all copies.
>>
>>
>
>
> --
> ____________________________
>
> Paul Plaquette,
> Senior Software Engineer
> Intel Corporation SAS
> Open source Technology Center - OTC
> France, Montpellier
Re: Media APIs - some research and discussion
Posted by "Plaquette, Paul" <pa...@intel.com>.
I think Google is going away from WebIntents.
On Mon, Jan 21, 2013 at 3:01 PM, Brian LeRoux <b...@brian.io> wrote:
> I think that spec is defunct and the functionality was removed from
> Chrome recently.
>
> =.(
>
> On Sun, Jan 20, 2013 at 10:29 PM, Simon MacDonald
> <si...@gmail.com> wrote:
> > Just reading everything over and looking at the way things are going it
> > seems like we should get the Web Intents API implemented. Looks like
> there
> > is already a shim implemented here:
> >
> > https://github.com/PaulKinlan/WebIntents
> >
> > with an APL license.
> >
> >
> > Simon Mac Donald
> > http://hi.im/simonmacdonald
> >
> >
> > On Fri, Jan 18, 2013 at 4:20 PM, Becky Gibson <gibson.becky@gmail.com
> >wrote:
> >
> >> I was looking at the open issues for iOS and found some related to
> >> capture/camera and media so I decided to see what the state of the
> latest
> >> W3C APIs are for these things. It wasn't a pleasant journey!
> >>
> >> There seem to be three apis that cover our camera/capture and media.
> Note
> >> that the referenced URLs are to the latest published draft although many
> >> have updated editor's drafts.
> >>
> >>
> >> - Pick Media Intent ( http://www.w3.org/TR/gallery/) Pick stored
> Media
> >> (images, audio, video) from various sources.
> >> - HTML Media Capture (http://www.w3.org/TR/html-media-capture/) -
> HTML
> >> form extension to allow user access to capture media from the
> device's
> >> via
> >> still camera, video, microphone via the File upload control.
> Appears to
> >> have replaced the Media Capture API (
> >> http://www.w3.org/TR/2010/WD-capture-api-20100401/) since all links
> on
> >> that page to Latest Published Draft and Latest Editor's Draft refer
> the
> >> the
> >> HTML Media Capture spec and there is no longer any reference to the
> >> Media
> >> Capture API on the Device API working group page (
> >> http://www.w3.org/2009/dap/)
> >> - Media Capture and Streams (http://www.w3.org/2009/dap/) Access to
> >> multi media streams (video camera, microphone, stored media) from a
> >> device.
> >>
> >>
> >> Thus, it seems that the Pick Media Intent would replace the Camera apis
> for
> >> selecting existing images and video. It would add the ability to pick
> from
> >> existing audio. Perhaps it is time to dive into the Web Intents spec
> and
> >> consider implementation ....
> >>
> >> HTML Media Capture allows capturing media but it is tied to the input
> >> element. It also provides for uploading the captured data. This
> seems to
> >> have replaced the Media Capture API that we implemented. I'm not sure
> how
> >> we can incorporate this into Cordova as there are no real apis, just
> >> attributes on the input element for the browser to implement and provide
> >> the UI. Although this seems to be the only W3C mechanism for accessing
> >> the still camera to capture an image!
> >>
> >> The Media Capture and Streams could replace our Media and Capture Video
> >> apis, but this is much more complicated. It also, in my opinion,
> doesn't
> >> seem all that well baked at the moment with a fair amount of open issues
> >> for defining some of the constants.
> >>
> >> Thus, I was a bit overwhelmed at how to address some of the Media and
> >> camera issues! I did discuss this briefly with Simon and was relieved
> >> that he was considering the HTML apis for media as our solution for
> Media (
> >>
> >>
> http://www.position-absolute.com/articles/introduction-to-the-html5-audio-tag-javascript-manipulation/
> >> ).
> >> Perhaps the best way to tackle our media is to normalize our media
> apis
> >> around the HTML Media apis.
> >>
> >> The point of this email? To capture my foray into the W3C Capture Apis
> >> and perhaps start a discussion on the next steps for Camera, Capture and
> >> Media apis.
> >>
> >> My next foray is into the changes to Contacts - this is now a Web
> Intent as
> >> well.
> >>
> ---------------------------------------------------------------------
> Intel Corporation SAS (French simplified joint stock company)
> Registered headquarters: "Les Montalets"- 2, rue de Paris,
> 92196 Meudon Cedex, France
> Registration Number: 302 456 199 R.C.S. NANTERRE
> Capital: 4,572,000 Euros
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
>
--
____________________________
Paul Plaquette,
Senior Software Engineer
Intel Corporation SAS
Open source Technology Center - OTC
France, Montpellier
Re: Media APIs - some research and discussion
Posted by Becky Gibson <gi...@gmail.com>.
Interesting. The latest Editor's draft of the Web Intents spec (
https://dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview-respec.html)
is dated today. However, looking at the page source that could be an
auto-generated date??
The Pick Content Intent editor's draft has a date of Jan. 18, 2013 (
http://w3c-test.org/dap/contacts/). Go Figure!
On Mon, Jan 21, 2013 at 10:39 AM, Andrew Grieve <ag...@chromium.org>wrote:
> Yeah, I believe that's the case as well. I'm not sure what the replacement
> is though :(
>
>
> On Mon, Jan 21, 2013 at 9:01 AM, Brian LeRoux <b...@brian.io> wrote:
>
> > I think that spec is defunct and the functionality was removed from
> > Chrome recently.
> >
> > =.(
> >
> > On Sun, Jan 20, 2013 at 10:29 PM, Simon MacDonald
> > <si...@gmail.com> wrote:
> > > Just reading everything over and looking at the way things are going it
> > > seems like we should get the Web Intents API implemented. Looks like
> > there
> > > is already a shim implemented here:
> > >
> > > https://github.com/PaulKinlan/WebIntents
> > >
> > > with an APL license.
> > >
> > >
> > > Simon Mac Donald
> > > http://hi.im/simonmacdonald
> > >
> > >
> > > On Fri, Jan 18, 2013 at 4:20 PM, Becky Gibson <gibson.becky@gmail.com
> > >wrote:
> > >
> > >> I was looking at the open issues for iOS and found some related to
> > >> capture/camera and media so I decided to see what the state of the
> > latest
> > >> W3C APIs are for these things. It wasn't a pleasant journey!
> > >>
> > >> There seem to be three apis that cover our camera/capture and media.
> > Note
> > >> that the referenced URLs are to the latest published draft although
> many
> > >> have updated editor's drafts.
> > >>
> > >>
> > >> - Pick Media Intent ( http://www.w3.org/TR/gallery/) Pick stored
> > Media
> > >> (images, audio, video) from various sources.
> > >> - HTML Media Capture (http://www.w3.org/TR/html-media-capture/) -
> > HTML
> > >> form extension to allow user access to capture media from the
> > device's
> > >> via
> > >> still camera, video, microphone via the File upload control.
> > Appears to
> > >> have replaced the Media Capture API (
> > >> http://www.w3.org/TR/2010/WD-capture-api-20100401/) since all
> links
> > on
> > >> that page to Latest Published Draft and Latest Editor's Draft refer
> > the
> > >> the
> > >> HTML Media Capture spec and there is no longer any reference to the
> > >> Media
> > >> Capture API on the Device API working group page (
> > >> http://www.w3.org/2009/dap/)
> > >> - Media Capture and Streams (http://www.w3.org/2009/dap/) Access
> to
> > >> multi media streams (video camera, microphone, stored media) from a
> > >> device.
> > >>
> > >>
> > >> Thus, it seems that the Pick Media Intent would replace the Camera
> apis
> > for
> > >> selecting existing images and video. It would add the ability to pick
> > from
> > >> existing audio. Perhaps it is time to dive into the Web Intents spec
> > and
> > >> consider implementation ....
> > >>
> > >> HTML Media Capture allows capturing media but it is tied to the input
> > >> element. It also provides for uploading the captured data. This
> > seems to
> > >> have replaced the Media Capture API that we implemented. I'm not
> sure
> > how
> > >> we can incorporate this into Cordova as there are no real apis, just
> > >> attributes on the input element for the browser to implement and
> provide
> > >> the UI. Although this seems to be the only W3C mechanism for
> accessing
> > >> the still camera to capture an image!
> > >>
> > >> The Media Capture and Streams could replace our Media and Capture
> Video
> > >> apis, but this is much more complicated. It also, in my opinion,
> > doesn't
> > >> seem all that well baked at the moment with a fair amount of open
> issues
> > >> for defining some of the constants.
> > >>
> > >> Thus, I was a bit overwhelmed at how to address some of the Media and
> > >> camera issues! I did discuss this briefly with Simon and was
> relieved
> > >> that he was considering the HTML apis for media as our solution for
> > Media (
> > >>
> > >>
> >
> http://www.position-absolute.com/articles/introduction-to-the-html5-audio-tag-javascript-manipulation/
> > >> ).
> > >> Perhaps the best way to tackle our media is to normalize our media
> > apis
> > >> around the HTML Media apis.
> > >>
> > >> The point of this email? To capture my foray into the W3C Capture
> Apis
> > >> and perhaps start a discussion on the next steps for Camera, Capture
> and
> > >> Media apis.
> > >>
> > >> My next foray is into the changes to Contacts - this is now a Web
> > Intent as
> > >> well.
> > >>
> >
>
Re: Media APIs - some research and discussion
Posted by Andrew Grieve <ag...@chromium.org>.
Yeah, I believe that's the case as well. I'm not sure what the replacement
is though :(
On Mon, Jan 21, 2013 at 9:01 AM, Brian LeRoux <b...@brian.io> wrote:
> I think that spec is defunct and the functionality was removed from
> Chrome recently.
>
> =.(
>
> On Sun, Jan 20, 2013 at 10:29 PM, Simon MacDonald
> <si...@gmail.com> wrote:
> > Just reading everything over and looking at the way things are going it
> > seems like we should get the Web Intents API implemented. Looks like
> there
> > is already a shim implemented here:
> >
> > https://github.com/PaulKinlan/WebIntents
> >
> > with an APL license.
> >
> >
> > Simon Mac Donald
> > http://hi.im/simonmacdonald
> >
> >
> > On Fri, Jan 18, 2013 at 4:20 PM, Becky Gibson <gibson.becky@gmail.com
> >wrote:
> >
> >> I was looking at the open issues for iOS and found some related to
> >> capture/camera and media so I decided to see what the state of the
> latest
> >> W3C APIs are for these things. It wasn't a pleasant journey!
> >>
> >> There seem to be three apis that cover our camera/capture and media.
> Note
> >> that the referenced URLs are to the latest published draft although many
> >> have updated editor's drafts.
> >>
> >>
> >> - Pick Media Intent ( http://www.w3.org/TR/gallery/) Pick stored
> Media
> >> (images, audio, video) from various sources.
> >> - HTML Media Capture (http://www.w3.org/TR/html-media-capture/) -
> HTML
> >> form extension to allow user access to capture media from the
> device's
> >> via
> >> still camera, video, microphone via the File upload control.
> Appears to
> >> have replaced the Media Capture API (
> >> http://www.w3.org/TR/2010/WD-capture-api-20100401/) since all links
> on
> >> that page to Latest Published Draft and Latest Editor's Draft refer
> the
> >> the
> >> HTML Media Capture spec and there is no longer any reference to the
> >> Media
> >> Capture API on the Device API working group page (
> >> http://www.w3.org/2009/dap/)
> >> - Media Capture and Streams (http://www.w3.org/2009/dap/) Access to
> >> multi media streams (video camera, microphone, stored media) from a
> >> device.
> >>
> >>
> >> Thus, it seems that the Pick Media Intent would replace the Camera apis
> for
> >> selecting existing images and video. It would add the ability to pick
> from
> >> existing audio. Perhaps it is time to dive into the Web Intents spec
> and
> >> consider implementation ....
> >>
> >> HTML Media Capture allows capturing media but it is tied to the input
> >> element. It also provides for uploading the captured data. This
> seems to
> >> have replaced the Media Capture API that we implemented. I'm not sure
> how
> >> we can incorporate this into Cordova as there are no real apis, just
> >> attributes on the input element for the browser to implement and provide
> >> the UI. Although this seems to be the only W3C mechanism for accessing
> >> the still camera to capture an image!
> >>
> >> The Media Capture and Streams could replace our Media and Capture Video
> >> apis, but this is much more complicated. It also, in my opinion,
> doesn't
> >> seem all that well baked at the moment with a fair amount of open issues
> >> for defining some of the constants.
> >>
> >> Thus, I was a bit overwhelmed at how to address some of the Media and
> >> camera issues! I did discuss this briefly with Simon and was relieved
> >> that he was considering the HTML apis for media as our solution for
> Media (
> >>
> >>
> http://www.position-absolute.com/articles/introduction-to-the-html5-audio-tag-javascript-manipulation/
> >> ).
> >> Perhaps the best way to tackle our media is to normalize our media
> apis
> >> around the HTML Media apis.
> >>
> >> The point of this email? To capture my foray into the W3C Capture Apis
> >> and perhaps start a discussion on the next steps for Camera, Capture and
> >> Media apis.
> >>
> >> My next foray is into the changes to Contacts - this is now a Web
> Intent as
> >> well.
> >>
>
Re: Media APIs - some research and discussion
Posted by Brian LeRoux <b...@brian.io>.
I think that spec is defunct and the functionality was removed from
Chrome recently.
=.(
On Sun, Jan 20, 2013 at 10:29 PM, Simon MacDonald
<si...@gmail.com> wrote:
> Just reading everything over and looking at the way things are going it
> seems like we should get the Web Intents API implemented. Looks like there
> is already a shim implemented here:
>
> https://github.com/PaulKinlan/WebIntents
>
> with an APL license.
>
>
> Simon Mac Donald
> http://hi.im/simonmacdonald
>
>
> On Fri, Jan 18, 2013 at 4:20 PM, Becky Gibson <gi...@gmail.com>wrote:
>
>> I was looking at the open issues for iOS and found some related to
>> capture/camera and media so I decided to see what the state of the latest
>> W3C APIs are for these things. It wasn't a pleasant journey!
>>
>> There seem to be three apis that cover our camera/capture and media. Note
>> that the referenced URLs are to the latest published draft although many
>> have updated editor's drafts.
>>
>>
>> - Pick Media Intent ( http://www.w3.org/TR/gallery/) Pick stored Media
>> (images, audio, video) from various sources.
>> - HTML Media Capture (http://www.w3.org/TR/html-media-capture/) - HTML
>> form extension to allow user access to capture media from the device's
>> via
>> still camera, video, microphone via the File upload control. Appears to
>> have replaced the Media Capture API (
>> http://www.w3.org/TR/2010/WD-capture-api-20100401/) since all links on
>> that page to Latest Published Draft and Latest Editor's Draft refer the
>> the
>> HTML Media Capture spec and there is no longer any reference to the
>> Media
>> Capture API on the Device API working group page (
>> http://www.w3.org/2009/dap/)
>> - Media Capture and Streams (http://www.w3.org/2009/dap/) Access to
>> multi media streams (video camera, microphone, stored media) from a
>> device.
>>
>>
>> Thus, it seems that the Pick Media Intent would replace the Camera apis for
>> selecting existing images and video. It would add the ability to pick from
>> existing audio. Perhaps it is time to dive into the Web Intents spec and
>> consider implementation ....
>>
>> HTML Media Capture allows capturing media but it is tied to the input
>> element. It also provides for uploading the captured data. This seems to
>> have replaced the Media Capture API that we implemented. I'm not sure how
>> we can incorporate this into Cordova as there are no real apis, just
>> attributes on the input element for the browser to implement and provide
>> the UI. Although this seems to be the only W3C mechanism for accessing
>> the still camera to capture an image!
>>
>> The Media Capture and Streams could replace our Media and Capture Video
>> apis, but this is much more complicated. It also, in my opinion, doesn't
>> seem all that well baked at the moment with a fair amount of open issues
>> for defining some of the constants.
>>
>> Thus, I was a bit overwhelmed at how to address some of the Media and
>> camera issues! I did discuss this briefly with Simon and was relieved
>> that he was considering the HTML apis for media as our solution for Media (
>>
>> http://www.position-absolute.com/articles/introduction-to-the-html5-audio-tag-javascript-manipulation/
>> ).
>> Perhaps the best way to tackle our media is to normalize our media apis
>> around the HTML Media apis.
>>
>> The point of this email? To capture my foray into the W3C Capture Apis
>> and perhaps start a discussion on the next steps for Camera, Capture and
>> Media apis.
>>
>> My next foray is into the changes to Contacts - this is now a Web Intent as
>> well.
>>
Re: Media APIs - some research and discussion
Posted by Simon MacDonald <si...@gmail.com>.
Just reading everything over and looking at the way things are going it
seems like we should get the Web Intents API implemented. Looks like there
is already a shim implemented here:
https://github.com/PaulKinlan/WebIntents
with an APL license.
Simon Mac Donald
http://hi.im/simonmacdonald
On Fri, Jan 18, 2013 at 4:20 PM, Becky Gibson <gi...@gmail.com>wrote:
> I was looking at the open issues for iOS and found some related to
> capture/camera and media so I decided to see what the state of the latest
> W3C APIs are for these things. It wasn't a pleasant journey!
>
> There seem to be three apis that cover our camera/capture and media. Note
> that the referenced URLs are to the latest published draft although many
> have updated editor's drafts.
>
>
> - Pick Media Intent ( http://www.w3.org/TR/gallery/) Pick stored Media
> (images, audio, video) from various sources.
> - HTML Media Capture (http://www.w3.org/TR/html-media-capture/) - HTML
> form extension to allow user access to capture media from the device's
> via
> still camera, video, microphone via the File upload control. Appears to
> have replaced the Media Capture API (
> http://www.w3.org/TR/2010/WD-capture-api-20100401/) since all links on
> that page to Latest Published Draft and Latest Editor's Draft refer the
> the
> HTML Media Capture spec and there is no longer any reference to the
> Media
> Capture API on the Device API working group page (
> http://www.w3.org/2009/dap/)
> - Media Capture and Streams (http://www.w3.org/2009/dap/) Access to
> multi media streams (video camera, microphone, stored media) from a
> device.
>
>
> Thus, it seems that the Pick Media Intent would replace the Camera apis for
> selecting existing images and video. It would add the ability to pick from
> existing audio. Perhaps it is time to dive into the Web Intents spec and
> consider implementation ....
>
> HTML Media Capture allows capturing media but it is tied to the input
> element. It also provides for uploading the captured data. This seems to
> have replaced the Media Capture API that we implemented. I'm not sure how
> we can incorporate this into Cordova as there are no real apis, just
> attributes on the input element for the browser to implement and provide
> the UI. Although this seems to be the only W3C mechanism for accessing
> the still camera to capture an image!
>
> The Media Capture and Streams could replace our Media and Capture Video
> apis, but this is much more complicated. It also, in my opinion, doesn't
> seem all that well baked at the moment with a fair amount of open issues
> for defining some of the constants.
>
> Thus, I was a bit overwhelmed at how to address some of the Media and
> camera issues! I did discuss this briefly with Simon and was relieved
> that he was considering the HTML apis for media as our solution for Media (
>
> http://www.position-absolute.com/articles/introduction-to-the-html5-audio-tag-javascript-manipulation/
> ).
> Perhaps the best way to tackle our media is to normalize our media apis
> around the HTML Media apis.
>
> The point of this email? To capture my foray into the W3C Capture Apis
> and perhaps start a discussion on the next steps for Camera, Capture and
> Media apis.
>
> My next foray is into the changes to Contacts - this is now a Web Intent as
> well.
>