[OpenID] inconsistent "openid." prefix

Manger, James H James.H.Manger at team.telstra.com
Mon Dec 18 02:41:04 UTC 2006


OpenID Authentication 2.0 predraft 11 uses the "openid." prefix inconsistently.  For instance, §5.2.3 has dot-points for “openid.mode”, “openid.error”, “openid.contact”…, whereas §5.1.2.2 has dot-points for “error”, “contact”….
The data format example (§4.1.3) uses “mode” and “error” keys in the Key-Value Form encoding, but “openid.mode” and “openid.error” in the x-www-urlencoded example in the very next paragraph.  I assume it should be “openid.mode” and “openid.error” everywhere.
Text such as
  Value: "associate"
or
  Default: "HMAC-SHA1"
appears throughout the spec.  A assume the quotes do NOT appear in the protocol.  A sentence to this effect in §4.1 Protocol Messages would help, as would more comprehensive examples.
Add this sentence to §4.1:
“Specific values are shown in double quotes within this specification (eg Value: "associate") but the quotes do not appear in the protocol messages (eg openid.mode=associate).”


More information about the specs mailing list