W3C has published a new Web Standard (HTML5) involving the first draft of online privacy. It establishes a mechanism used by the browser to broadcast the formal specification of the privacy preference Website "do not track" (DNT. This draft was written by W3C, a new tracking Protection Working Group, and can be approved as a formal standard by year.
Earlier this year, Mozilla first introduced DNT settings in Firefox 4 (Firefox. It is a simple HTTP header flag that can be switched over through the browser preference dialog box. This sign tells website operators and advertisers that the rise of user intrusion tracking and other similar practices and behavior advertisements has become a common choice.
Of course, this mechanism only indicates preference and does not actively stop tracking activities. DNT is successful on the premise of voluntary compliance, from the Internet advertising, there will be measures to implement support for this function.
Although head ads will take some effort, it is not an insurmountable obstacle. The mainstream advertising industry has an individual record of self-discipline and respect for exit initiatives.
There is an existing exit mechanism that has been widely supported by advertisers. For example, the online advertising initiative is supported by major Internet advertising companies and provides a simple web-based tool to help users configure exit cookies. Cookie-based methods. If the user clears the cookies of the browser, they lose the right to exit.
Mozilla DNT starts and proposes it as a more practical cookie Method for a long term. This idea has produced a lot of discussions, but it did not initially attract support from advertisers. Mozilla decided to launch the DNT feature, the main release of Firefox 4, even if it does not do anything, but due to lack of AD support, it is hoped that this will encourage adoption.
Defining a formal DNT standard seems to be another really good step to help encourage more extensive feature support between advertising customers. Ideally, this specification will provide clear and consistent DNT support and guidance on how to implement it on servers and browsers.
This specification goes beyond just defining how the header should be disseminated. It is designed to address many other issues, such as defining a standardized well-known Uri, where the server can respond to indicate whether they respect DNT protocols. The draft is still in its early stages of development, but it still has to be done with many placeholders.
Cooperation between 15 companies and organizations was conducted through the W3C Working Group draft. These include all major browser vendors, several major network companies (including Facebook), and advocacy groups, such as consumer supervision and Electronic Frontier foundations. The US Federal Trade Commission (FTC) has previously expressed interest in seeing broad DNT support and is also a member of a working group.
DNT standardization seems to be a constructive undertaking and is on the right track. Both DNT specifications and DNT compliance drafts come from W3C websites.
Source: http://www.tizenchina.com/article-8-1.html