W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2010

RE: CfC: Messaging FPWD

From: Niklas Widell <niklas.widell@ericsson.com>
Date: Mon, 15 Mar 2010 16:16:29 +0100
Message-ID: <D96608909E170042B40D538BEB20B569049DE0CF@esealmw121.eemea.ericsson.se>
To: "Marcin Hanclik" <Marcin.Hanclik@access-company.com>, "David Rogers" <david.rogers@omtp.org>, "Kai Hendry" <hendry@aplix.co.jp>
Cc: "Robin Berjon" <robin@berjon.com>, <public-device-apis@w3.org>
Hi Marcin, 
Oops, sigh, the intro text was not meant to be there (in this release at
least) ;-)

Question to WG: Should we also include message storage API in this
version of Messaging API?

---
Proposed (rough) starting point for message storage API (additions to
current API):

Message
  PendingOp remove(SuccessCB, ErrorCB);
  PendingOp save(folder, SuccessCB, ErrorCB)
  
MessagingManager
  PendingOp getAccounts(MessageType, SuccessCB, ErrorCB) // ==>
sequence<DOMString>
  PendingOp getTopFolder(account, SuccessCB, ErrorCB) // ==>
MessageFolder
  // need notion of default account/messaging type. account==serviceId
  
MessageFolder
  PendingOp getMessages(MessageFilter, SuccessCB, ErrorCB) // ==>
sequence<Message>
  PendingOp getFolders(SuccessCB, ErrorCB)   // ==>
sequence<MessageFolder>
  PendingOp remove(SuccessCB, ErrorCB);      // removes folder and
content
  PendingOp create(DOMString folderName, SuccessCB, ErrorCB) // create
new folder in folder 
  DRAFTS // consts for system provided folders per account
  INBOX
  OUTBOX
  SENT
  // DELETED, ARCHIVE ?
  
MessageFilter:MessageProperties 
  unsigned short limit // page size
  unsigned short page  // offset
 

Best regards,
Niklas

> -----Original Message-----
> From: Marcin Hanclik [mailto:Marcin.Hanclik@access-company.com] 
> Sent: den 15 mars 2010 12:15
> To: Niklas Widell; David Rogers; Kai Hendry
> Cc: Robin Berjon; public-device-apis@w3.org
> Subject: RE: CfC: Messaging FPWD
> 
> Hi Niklas,
> 
> The draft says
> "It includes APIs ... to inspect and manipulate the folders 
> where the messages are kept."
> although it is not in the requirements section, but in the 
> introduction.
> 
> The DAP charter foresees CRUD APIs, it seems to be essential 
> for a variety of APIs, including also Calendar/PIM APIs. So 
> maybe it could be done in the similar manner, i.e. with save 
> and remove methods?
> 
> Thanks,
> Marcin
> 
> [1] 
> http://dev.w3.org/cvsweb/~checkout~/2009/dap/messaging/Overvie
w.html?rev=1.3&content-type=text/html;%20charset=iso-8859-1
> 
> Marcin Hanclik
> ACCESS Systems Germany GmbH
> Tel: +49-208-8290-6452  |  Fax: +49-208-8290-6465
> Mobile: +49-163-8290-646
> E-Mail: marcin.hanclik@access-company.com
> 
> -----Original Message-----
> From: public-device-apis-request@w3.org 
> [mailto:public-device-apis-request@w3.org] On Behalf Of Niklas Widell
> Sent: Monday, March 15, 2010 10:56 AM
> To: David Rogers; Kai Hendry
> Cc: Robin Berjon; public-device-apis@w3.org
> Subject: RE: CfC: Messaging FPWD
> 
> Hi,
> Yes, adding folder access would be useful. However, we are 
> getting awfully close to "file system access API", since we 
> would nee to be able to navigate inside message storage 
> folders, with all the related security issues.
> 
> I was thinking of a "message picker UI" that the browser 
> could provide for navigation, but perhaps having an api that 
> allows displaying the content of a folder is needed as well.
> 
> Note that Message folder access is not on the current list of 
> requirements (I mistakenly thought so myself until quite 
> recently) (1).
> 
> I'm open for suggestions on how to approach message storage 
> (need/no need/ etc)
> 
> Best regards,
> Niklas
> 
> (1) http://dev.w3.org/2009/dap/messaging/#requirements
> 
> > -----Original Message-----
> > From: public-device-apis-request@w3.org 
> > [mailto:public-device-apis-request@w3.org] On Behalf Of David Rogers
> > Sent: den 10 mars 2010 18:01
> > To: Kai Hendry
> > Cc: Robin Berjon; public-device-apis@w3.org
> > Subject: RE: CfC: Messaging FPWD
> >
> > I think that needs to be addressed then - lots of messaging systems 
> > (remember we're creating device APIs) such as SMS and MMS 
> have a draft 
> > folder that you may want to use as a developer. If you don't define 
> > the interface to that then you won't get access.
> >
> > Cheers,
> >
> >
> > David.
> >
> > -----Original Message-----
> > From: kai.hendry@gmail.com [mailto:kai.hendry@gmail.com] On 
> Behalf Of 
> > Kai Hendry
> > Sent: 10 March 2010 16:40
> > To: David Rogers
> > Cc: Robin Berjon; public-device-apis@w3.org
> > Subject: Re: CfC: Messaging FPWD
> >
> > On 10 March 2010 16:37, David Rogers <david.rogers@omtp.org> wrote:
> > > What if you wanted to save a draft though?
> >
> > How do you do that in this API 
> http://dev.w3.org/2009/dap/messaging/?
> >
> > Anyway, you don't need an API to save a draft of a message.
> > Any Web developer can easily do that.
> >
> 
> 
> ________________________________________
> 
> Access Systems Germany GmbH
> Essener Strasse 5  |  D-46047 Oberhausen HRB 13548 
> Amtsgericht Duisburg
> Geschaeftsfuehrer: Kiyoyasu Oishi, Tomonori Watanabe, Yusuke Kanda
> 
> www.access-company.com
> 
> CONFIDENTIALITY NOTICE
> This e-mail and any attachments hereto may contain 
> information that is privileged or confidential, and is 
> intended for use only by the individual or entity to which it 
> is addressed. Any disclosure, copying or distribution of the 
> information by anyone else is strictly prohibited.
> If you have received this document in error, please notify us 
> promptly by responding to this e-mail. Thank you.
> 
Received on Monday, 15 March 2010 15:17:03 GMT

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