W3C home > Mailing lists > Public > public-sysapps@w3.org > December 2012

Re: [Messaging API based on webinos]

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 31 Dec 2012 15:45:05 -0800
Message-ID: <CA+c2ei-0rhM=ORcXrqUpWxg4aHJwbHWjddkU3Hog6RwOBp+JCw@mail.gmail.com>
To: "Nilsson, Claes1" <Claes1.Nilsson@sonymobile.com>
Cc: "public-sysapps@w3.org" <public-sysapps@w3.org>, "webinos-wp8-ml@fokus.fraunhofer.de" <webinos-wp8-ml@fokus.fraunhofer.de>, Christian Fuhrhop <christian.fuhrhop@fokus.fraunhofer.de>, Vercelli Stefano <stefano.vercelli@telecomitalia.it>
With both this proposal, and the proposal from Intel, I'm wondering what
type of applications is the target.

As far as I can see, the email support in this API isn't enough to build
for example a full-fledged email application. For that, you need IMAP
support which means ability to enumerate the folder hierarchy and to query
metadata about folders. You also need things like control over downloading
attachments.

You likely also need integration with server-side synchronization such as
ActiveSync. I don't know exactly what this entails, but at least I would
imagine it requires ability to query server-side metadata similar to IMAP.

I also notice that there is no account configuration support in this API.
This could be completely fine since that can be handled in a settings
application on the device, separate from the email application. However I
was wondering if this is something that you guys had looked into? It also
seems like there needs to be some minimal amount of account management in
an email API since you need to be able to enumerate which accounts are
configured and be able to create UI which allows the user to choose which
account to send an email with and which account to query when doing
searching.

I think a lot of the same questions apply to the IM. I.e. what are the
target applications for this API. It doesn't seem like there is enough
there to build a chat client that integrates with for example gtalk, irc,
jabber or facebook messaging as backends.

/ Jonas


On Mon, Dec 24, 2012 at 2:45 AM, Nilsson, Claes1 <
Claes1.Nilsson@sonymobile.com> wrote:

> Hi,****
>
> ** **
>
> I have submitted an example of a Messaging API,
> http://sysapps.github.com/sysapps//proposals/Messaging_webinos/Messaging.HTML<http://sysapps.github.com/sysapps/proposals/Messaging_webinos/Messaging.HTML>,
> that supports SMS, MMS, E-mail and IM based on the current Webinos
> Messaging API, which originally was based on the WAC Messaging API. ****
>
> ** **
>
> This API has been implemented for SMS in the Android Webinos platform.****
>
> ** **
>
> Notes:****
>
> **        **There has been a discussion, starting here
> http://lists.w3.org/Archives/Public/public-sysapps/2012Oct/0040.html,  on
> whether SysApps  only should specify an SMS/MMS API and leave support for
> the other messaging technologies to JS libraries that use the Raw Socket
> API. I am not taking a specific position here. The purpose with this
> submission is to give an example of an API that directly provides high
> level support for several Messaging technologies. This example can be
> beneficial in further discussions on the approach on whether E-mail/IM
> should be supported directly by a standardized API or by JS libraries that
> leverage the Raw Socket API.
>
> ****
>
> **        **There has also been a discussion about filtering. The
> webinos proposal contains a MessageFilter dictionary that defines specific
> filtering attributes. However, a general approach to data models and
> filtering has been proposed, starting at
> http://lists.w3.org/Archives/Public/public-sysapps/2012Nov/0022.html, and
> we should probably follow such an approach for Messaging as well.
>
> ****
>
> **        **In this proposal traditional callback function references is
> used in method definitions, which differs from the style in other API
> proposals submitted to SysApps. They use a return type that is an interface
> that represents an ongoing operation. There is no specific reason for this
> difference in the Webinos Messaging API. If the WG decides to base the
> Messaging API on the Webinos example then style could be adapted to the
> style of the other SysApps APIs.
>
> ****
>
> **        **We have included a cancel() method allowing applications
> cancel an ongoing sendMessage or findMessage operation. This might be
> controversial and this kind of method is generally not included in W3C APIs
> and implementability is probably an issue. One exception is the File reader
> API, which allows read operations to be aborted. So there are situations
> where an ongoing asynchronous operation may need have to be aborted. Need
> to be discussed.****
>
> ** **
>
> Best regards****
>
>   Claes****
>
> [image: cid:3333625383_1036728]
>
> *Claes Nilsson M.Sc.E.E*
> Master Engineer, Research
> Technology Research - Advanced Application Lab
> *
> Sony Mobile Communications*
>  Phone:  +46 10 80 15178
> Mobile: +46 705 56 68 78
> Switchboard: +46 10 80 00000
> E-Mail:* **mailto:claes1.nilsson@sonymobile.com*<claes1.nilsson@sonyericsson.com>
> Visiting Address; Nya Vattentornet
> SE-221 88 LUND,
> Sweden ****
>
> *Disclaimer:
> *The information in this e-mail is confidential and may be legally
> privileged. It is intended solely for the named recipient(s) and access to
> this e-mail by anyone else is unauthorized. The views are those of the
> sender and not necessarily the views of Sony Ericsson and Sony Ericsson
> accepts no responsibility or liability whatsoever or howsoever arising in
> connection with this e-mail.Any attachment(s) to this message has been
> checked for viruses, but please rely on your own virus checker and
> procedures. If you contact us by e-mail, we will store your name and
> address to facilitate communications. If you are not the intended
> recipient, please inform the sender by replying this transmission and
> delete the e-mail and any copies of it without disclosing it.****
>
> ** **
>


image001.gif
(image/gif attachment: image001.gif)

Received on Monday, 31 December 2012 23:46:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 31 December 2012 23:46:04 GMT