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

Re: updated draft charter

From: Dave Raggett <dsr@w3.org>
Date: Sat, 16 Jun 2012 09:55:15 +0100
Message-ID: <4FDC49F3.4010505@w3.org>
To: "SULLIVAN, BRYAN L" <bs3131@att.com>
CC: W3C SysApps <public-sysapps@w3.org>
Thanks, I've updated the text to:

> An API to manage the system's settings (e.g. time/clock settings,
> and personal preferences including privacy settings).

On 14/06/12 22:38, SULLIVAN, BRYAN L wrote:
> OK, if "An API to manage the system's settings (including notably
> time/clock settings and personal preferences)" implicitly includes
> the ability to manage preferences related to privacy, and the ability
> for apps to provide relevant privacy-related info that is needed by
> the user in managing those preferences. But I would prefer that this
> was explicit, to avoid having to rely later on this email thread in
> support for these objectives in the system settings API.
> Thanks,
> Bryan Sullivan 
> -----Original Message-----
> From: Dave Raggett [mailto:dsr@w3.org] 
> Sent: Friday, June 08, 2012 3:36 AM
> To: W3C SysApps
> Subject: Re: updated draft charter
> What changes in wording are needed if any?
> For instance, do we need to make explicit that system settings includes
> personal preferences for devices used by multiple people?
> Do we need to make it explicit that preferences include privacy and
> security settings?
> I suspect this isn't necessary as it would lead to having to be very
> explicit about the kinds of settings we will/won't cover.
> Is the following wording sufficient:
> System Settings API
> An API to manage the system's settings (including notably time/clock
> settings and personal preferences).

Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett
Received on Saturday, 16 June 2012 08:55:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:09 UTC