W3C home > Mailing lists > Public > public-tracking@w3.org > October 2012

RE: ACTION-265

From: Shane Wiley <wileys@yahoo-inc.com>
Date: Wed, 17 Oct 2012 11:45:26 -0700
To: John Simpson <john@consumerwatchdog.org>
CC: "public-tracking@w3.org" <public-tracking@w3.org>
Message-ID: <63294A1959410048A33AEE161379C8027480CCDA94@SP2-EX07VS02.ds.corp.yahoo.com>
Depends on the scale and nature of the problem - each company would need to be able to defend their reaction time, approach, priority, and effort to rectify the situation.  If it's a very small problem, then I would expect the response to be swift (days/weeks).  If it's a larger problem, it may make more time to address the situation (new code release, data clean up cycles).  The important items are that the issue has been identified and the company has committed to rectifying the situation.

- Shane

From: John Simpson [mailto:john@consumerwatchdog.org]
Sent: Wednesday, October 17, 2012 11:18 AM
To: Shane Wiley
Cc: public-tracking@w3.org
Subject: Re: ACTION-265

Shane,

A clarifying question:  Could you please give a rough idea of how long a "commercially reasonable time" would be?

Thanks,
John

----------
John M. Simpson
Consumer Advocate
Consumer Watchdog
2701 Ocean Park Blvd., Suite 112
Santa Monica, CA,90405
Tel: 310-392-7041
Cell: 310-292-1902
www.ConsumerWatchdog.org<http://www.ConsumerWatchdog.org>
john@consumerwatchdog.org<mailto:john@consumerwatchdog.org>

On Oct 16, 2012, at 9:58 PM, Shane Wiley wrote:


Updated text per our discussions in Amsterdam.

Tracking Compliance and Scope
Section 3.8.1

It may happen that a party claiming compliance with this standard will retain or use data without awareness that it is doing so contrary to its intended party position with respect to the standard. In such a case, the party must bring its practices and prior collected data into compliance with the standard within a commercially reasonable time after it learns of such non-compliant activity.
Received on Wednesday, 17 October 2012 18:46:30 UTC

This archive was generated by hypermail 2.3.1 : Friday, 21 June 2013 10:11:36 UTC