I think this is covered in http negotiation.If the OP knows the users language preference from there profile they can fetch the correct one for the user and display it.
Can google stop changing my language pregrence to Spanish?I think a single URI for each policy and letting http deal with the language issue is best.
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.
I don't think it would be more than a page ether way.The other alternative is to agree on it as a community and RP's just start publishing it.
It isn't like we haven't done that in the past. SREG was never adopted as a standard.
John B. On 2-Jun-09, at 2:28 PM, [email protected] wrote:
Date: Tue, 2 Jun 2009 11:27:44 -0700 From: Andrew Arnott <[email protected]> Subject: Re: SREG's Privacy Policy URL To: Johannes Ernst <[email protected]> Cc: OpenID Specs Mailing List <[email protected]> Message-ID: <[email protected]> Content-Type: multipart/alternative; boundary=001e680f11ec14b6d2046b61b46c --001e680f11ec14b6d2046b61b46c Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printableWould internationalizing entail the OP getting the URL for the RP's privacypolicy in the right language?If so, why not just have one URL and let the RP detect the user agent's preferred language? (Yes, I know the UI extension has this for the reasonthat the user agent isn't properly configured, so it's an interesting point...) -- Andrew Arnott"I [may] not agree with what you have to say, but I'll defend to the deathyour right to say it." - S. G. Tallentyre
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ specs mailing list [email protected] http://openid.net/mailman/listinfo/specs
