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

RE: Contacts API typical use cases and privacy considerations

From: <richard.tibbett@orange-ftgroup.com>
Date: Tue, 23 Feb 2010 11:54:08 +0100
Message-ID: <4524_1266922451_4B83B3D3_4524_4199_1_355A518BC0575547B2A3D6773AAF8EEF9502F5@ftrdmel1>
To: <maxfro@opera.com>, <dom@w3.org>, <public-device-apis@w3.org>
Hi Max,

On Feb 23, 2010 at 09:53, Max Froumentin [maxfro@opera.com] wrote:
> 
> On 19/02/2010 18:59, richard.tibbett@orange-ftgroup.com wrote:
> >
> >> Perhaps we need to be more formal on this approach in the methods 
> >> and/or 'Security and Privacy Considerations'? My initial 
> reaction is 
> >> that we don't.
> 
> I think we do need to be more formal, on the contrary, since 
> user interaction experts will have different opinions and 
> browser vendors will want to differentiate their product.
> 
> So instead I think it's better being formal in the 
> specification, with statements such as "The broker MUST offer 
> to restrict the a subset of the contacts to share", etc.
> 

I will work on some more requirements to this effect and update the
mailing list when complete.

I'd really like to ultimately move towards testable assertions in the
recommendation.

Thanks,

Richard

*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************
Received on Tuesday, 23 February 2010 10:54:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:17 UTC