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

RE: Contacts Saving feature (was RE: Draft minutes 2010-12-15)

From: Suresh Chitturi <schitturi@rim.com>
Date: Wed, 15 Dec 2010 17:02:56 -0600
Message-ID: <D37CC1B151BD57489F4F89609F168FE8080DBAFF@XCH01DFW.rim.net>
To: "Rich Tibbett" <rich.tibbett@gmail.com>
Cc: <Frederick.Hirsch@nokia.com>, <public-device-apis@w3.org>
Please see below.

 

Suresh

 

From: Rich Tibbett [mailto:rich.tibbett@gmail.com] 
Sent: Wednesday, December 15, 2010 4:12 PM
To: Suresh Chitturi
Cc: Frederick.Hirsch@nokia.com; public-device-apis@w3.org
Subject: Re: Contacts Saving feature (was RE: Draft minutes 2010-12-15)

 

Suresh Chitturi wrote:

I read from the minutes that a resolution was taken to eliminate the
contact write altogether. I don't quite agree with the resolution and
because you are essentially not providing a standardized way to
implement write back updated contact information and leaving it to the
implementations.

 

This resolution is the result of the email thread starting here: http://lists.w3.org/Archives/Public/public-device-apis/2010Dec/0009.html.


 

We have a standardized way to support write back with BlobBuilder (File Writer) and createObjectUrl (File Reader) with the user consenting to the save operation (by click a 'download' link) and the implementation handling the resulting MIME type, either automatically or manually at that point.

 

Suresh>> true, this is one way but I see two problems with this compared to a direct method 1) you are asking the implementation to create a URL and 2) the write back is handled by the browser application outside the JS environment. The JS approach is much more efficient and direct. 

 

	
	We talked about the option of contact.save() method that can be
	reasonably invoked with a user consent approach (check box, pop-up,
	etc). 

 

We (still) don't have any reasonable Javascript writeback paradigms for save operations. It would, however, be interesting to hearing about the check box or pop-up ideas if they have not yet been considered.

 

Suresh>> This is debatable,  there are number of ways UIs can present intuitively to represent “save/delete” operations (e.g. online mail boxes use, pop dialogs)..

 

	I understand you want to limit the APIs to read only version in
	the first phase but I would like to come back to the save discussions
	 and find a way to support it in a standardized way through JS APIs.

 

The proposed approach, which I'm due to write up in the Contact API spec will allow write back with the method detailed above.

 

Suresh>> do you mean with .save() method or file/blob write back approach?

 

- Rich 

 

	
	-----Original Message-----
	From: public-device-apis-request@w3.org
	[mailto:public-device-apis-request@w3.org] On Behalf Of
	Frederick.Hirsch@nokia.com
	Sent: Wednesday, December 15, 2010 10:05 AM
	To: public-device-apis@w3.org
	Cc: Frederick.Hirsch@nokia.com
	Subject: Draft minutes 2010-12-15
	
	Attached are draft minutes from today 2010-12-15. Thanks to Niklas for
	scribing. HTML follows text.
	
	regards, Frederick
	
	Frederick Hirsch
	Nokia
	
	
	
	---------------------------------------------------------------------
	This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

 


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Wednesday, 15 December 2010 23:04:12 GMT

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