[OpenID] openid and hcard

[Martin Atkins]

tom wrote:
>>   
> Not that I know of and this creates another small headache. The consumer 
> can request both SREG and AX and at the consumer end you can bin SREG 
> data if you receive AX data, however at the OP end the person is now 
> presented with a request for AX:email and SREG:email, hence to the eye 
> it looks like something has gone wrong because the person sees what 
> appears to be duplicate information requested.
> 

I would expect that an OP, when presented with that question, would 
"know" that those two fields are functionally equivalent and thus merge 
them into a single question in the UI.

Even if this is not necessarily true for AX, any OP that implements SREG 
must know the meaning of all of the field types and could potentially 
implement SREG's email field as a wrapper around the equivalent AX field 
if that OP supports AX.