<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I think this is covered in http negotiation. <div><br></div><div>If the OP knows the users language preference from there profile they can fetch the correct one for the user and display it.</div><div><br></div><div>Can google stop changing my language pregrence to Spanish? </div><div><br></div><div>I think a single URI for each policy and letting http deal with the language issue is best.</div><div><br></div><div>For process we could have it written up in the XRI TC as a profile for XRDS (Breno/George?), or attempt to spin up a OIDF WG. </div><div><br></div><div>I don't think it would be more than a page ether way.</div><div><br></div><div>The other alternative is to agree on it as a community and RP's just start publishing it.</div><div><br></div><div>It isn't like we haven't done that in the past. SREG was never adopted as a standard.</div><div><br></div><div>John B.</div><div><br><div><div>On 2-Jun-09, at 2:28 PM, <a href="mailto:specs-request@openid.net">specs-request@openid.net</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="color: rgb(0, 0, 0); font-family: -webkit-monospace; font-size: 10px; ">Date: Tue, 2 Jun 2009 11:27:44 -0700<br>From: Andrew Arnott <<a href="mailto:andrewarnott@gmail.com">andrewarnott@gmail.com</a>><br>Subject: Re: SREG's Privacy Policy URL<br>To: Johannes Ernst <<a href="mailto:jernst+openid.net@netmesh.us">jernst+openid.net@netmesh.us</a>><br>Cc: OpenID Specs Mailing List <<a href="mailto:specs@openid.net">specs@openid.net</a>><br>Message-ID:<br><span class="Apple-tab-span" style="white-space: pre; "> </span><<a href="mailto:216e54900906021127r11597727t965b1e8ecad57cd5@mail.gmail.com">216e54900906021127r11597727t965b1e8ecad57cd5@mail.gmail.com</a>><br>Content-Type: multipart/alternative;<br><span class="Apple-tab-span" style="white-space: pre; "> </span>boundary=001e680f11ec14b6d2046b61b46c<br><br>--001e680f11ec14b6d2046b61b46c<br>Content-Type: text/plain; charset=windows-1252<br>Content-Transfer-Encoding: quoted-printable<br><br>Would internationalizing entail the OP getting the URL for the RP's privacy<br>policy in the right language?<br><br>If so, why not just have one URL and let the RP detect the user agent's<br>preferred language? (Yes, I know the UI extension has this for the reason<br>that the user agent isn't properly configured, so it's an interesting<br>point...)<br>--<br>Andrew Arnott<br>"I [may] not agree with what you have to say, but I'll defend to the death<br>your right to say it." - S. G. Tallentyre<br><br></span></blockquote></div><br></div></body></html>