W3C home > Mailing lists > Public > www-international@w3.org > October to December 2015

Re: i18n-ISSUE-492: Honor the HTTP Accept-Language header for selecting the consent language

From: Steven Atkin <atkin@us.ibm.com>
Date: Fri, 9 Oct 2015 08:36:11 -0400
Hi David,

We certainly understand the desire to stay out of user interface issues.
With that being said we do want to make sure that the spec does not do
anything that prevents user agents from being able to obtain consents in
other languages. Additionally, it may be worthwhile to point out that user
agents may request consents in other languages and that implementers of
this spec should be prepared to handle that. We can leave out how the
discussion related to how they actually do this, e.g., HTTP Accept-Language
setting.

Thanks,


Steven Atkin, Ph.D.
STSM - Chief Globalization Architect
IBM Globalization Center of Competency
atkin@us.ibm.com
http://www-3.ibm.com/software/globalization/index.jsp




From:	David Singer <singer@apple.com>
To:	Steven Atkin/Austin/IBM@IBMUS
Cc:	public-tracking-comments@w3.org, international@w3.org
Date:	10/01/2015 04:22 PM
Subject:	Re: i18n-ISSUE-492: Honor the HTTP Accept-Language header for
            selecting the  consent language
Sent by:	singer@apple.com



Hi Steven

we tried very hard to stay out of user interface in the TPE specification.
In section 4, we merely say that you have to get the user’s informed
consent to do things that are otherwise proscribed. The way you get that
consent is out of scope, as is any UI.


> On Oct 1, 2015, at 7:34 , Steven Atkin <atkin@us.ibm.com> wrote:
>
> 4 Consent
>
http://www.w3.org/TR/2015/WD-tracking-compliance-20150714/#user-granted-exceptions


>
> When a consent is displayed to the end-user the consent should be
displayed according to the HTTP Accept-Language setting. Additionally, a
list of all available languages that the consent is available in should be
displayed to the end-user in the event that the end-user wishes to see the
consent in a different language.
>
>
> Steven Atkin, Ph.D.
> STSM - Chief Globalization Architect
> IBM Globalization Center of Competency
> atkin@us.ibm.com
> http://www-3.ibm.com/software/globalization/index.jsp


David Singer
Manager, Software Standards, Apple Inc.




z{S}ĝxjǺ
z{mʗ{٥r
z{Ch+bx)<html><body><p>Hi David,<br><br>We certainly understand the desire to stay out of user interface issues. With that being said we do want to make sure that the spec does not do anything that prevents user agents from being able to obtain consents in other languages. Additionally, it may be worthwhile to point out that user agents may request consents in other languages and that implementers of this spec should be prepared to handle that. We can leave out how the discussion related to how they actually do this, e.g., HTTP Accept-Language setting.<br><br>Thanks,<br><br><br>Steven Atkin, Ph.D.<br>STSM - Chief Globalization Architect<br>IBM Globalization Center of Competency<br>atkin@us.ibm.com<br><a href="http://www-3.ibm.com/software/globalization/index.jsp">http://www-3.ibm.com/software/globalization/index.jsp</a><br><br><img width="16" height="16" src="cid:1__=0ABBF44ADFD746F68f9e8a93df938690918c0AB@" border="0" alt="Inactive hide details for David Singer ---10/01/2015 04:22:31 PM---Hi Steven we tried very hard to stay out of user interface i"><font color="#424282">David Singer ---10/01/2015 04:22:31 PM---Hi Steven we tried very hard to stay out of user interface in the TPE specification.  In section 4,</font><br><br><font size="2" color="#5F5F5F">From:        </font><font size="2">David Singer &lt;singer@apple.com&gt;</font><br><font size="2" color="#5F5F5F">To:        </font><font size="2">Steven Atkin/Austin/IBM@IBMUS</font><br><font size="2" color="#5F5F5F">Cc:        </font><font size="2">public-tracking-comments@w3.org, international@w3.org</font><br><font size="2" color="#5F5F5F">Date:        </font><font size="2">10/01/2015 04:22 PM</font><br><font size="2" color="#5F5F5F">Subject:        </font><font size="2">Re: i18n-ISSUE-492: Honor the HTTP Accept-Language header for selecting the  consent language</font><br><font size="2" color="#5F5F5F">Sent by:        </font><font size="2">singer@apple.com</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt>Hi Steven<br><br>we tried very hard to stay out of user interface in the TPE specification. &nbsp;In section 4, we merely say that you have to get the user’s informed consent to do things that are otherwise proscribed. The way you get that consent is out of scope, as is any UI.<br><br><br>&gt; On Oct 1, 2015, at 7:34 , Steven Atkin &lt;atkin@us.ibm.com&gt; wrote:<br>&gt; <br>&gt; 4 Consent <br>&gt; </tt><tt><a href="http://www.w3.org/TR/2015/WD-tracking-compliance-20150714/#user-granted-exceptions">http://www.w3.org/TR/2015/WD-tracking-compliance-20150714/#user-granted-exceptions</a></tt><tt><br>&gt; <br>&gt; When a consent is displayed to the end-user the consent should be displayed according to the HTTP Accept-Language setting. Additionally, a list of all available languages that the consent is available in should be displayed to the end-user in the event that the end-user wishes to see the consent in a different language.<br>&gt; <br>&gt; <br>&gt; Steven Atkin, Ph.D.<br>&gt; STSM - Chief Globalization Architect<br>&gt; IBM Globalization Center of Competency<br>&gt; atkin@us.ibm.com<br>&gt; </tt><tt><a href="http://www-3.ibm.com/software/globalization/index.jsp">http://www-3.ibm.com/software/globalization/index.jsp</a></tt><tt><br><br>David Singer<br>Manager, Software Standards, Apple Inc.<br><br></tt><br><br><BR>
</body></html>

z{mʗ
z{Ch+bx)~)^
z{H
z{S}ĝxjǺGIF89aeglHI
Received on Friday, 9 October 2015 12:37:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:09 UTC