RE: ISSUE-13: Gathering requirements [Messaging API]

Considering the WG focus on the ubiquitous web it may initially help to
frame Messaging API requirements according to the messaging system(s) in
scope for this API.

For example, which particular systems should be addressed by this API
(IM? SMS? MMS? Email? ...Twitter? etc)...or should (and could) the
Messaging API be agnostic to the underlying messaging system(s) in use?

Any thoughts welcome of course. I'm unclear at the moment as to which
messaging system this API will address.

br/ Richard

> -----Original Message-----
> From: public-device-apis-request@w3.org 
> [mailto:public-device-apis-request@w3.org] On Behalf Of 
> Device APIs and Policy Working Group Issue Tracker
> Sent: 25 August 2009 14:29
> To: public-device-apis@w3.org
> Subject: ISSUE-13: Gathering requirements [Messaging API]
> 
> 
> ISSUE-13: Gathering requirements [Messaging API]
> 
> http://www.w3.org/2009/dap/track/issues/13
> 
> Raised by: Robin Berjon
> On product: Messaging API
> 
> 
> 
> 
> 
>

Received on Wednesday, 16 September 2009 16:33:13 UTC