PROPOSAL: OpenID Form Clarification (A.4)

[Jonathan Daugherty]

# Why SHOULD rather then MUST? [1]
# 
# What valid reason is there for an RP to not have that field name?

The simple reason is that one can't enforce a MUST in this case.  (And
even if one ammends the spec to make the field name a prerequisite for
OpenID, I question whether that is a good design choice.)

I agree that it would be extremely useful to have a consistent form
field name for just the reasons you cited, and the current spec
reflects that.  If the spec is the place one would put preferences,
then they should be RECOMMENDEDs or SHOULDs: not MUSTs.

-- 
  Jonathan Daugherty
  JanRain, Inc.