Attribute Exchange pre-draft 5

[Johnny Bufu]

I have uploaded changes proposed at the beginning of this thread into  
SVN; if you're up to reading the xml source, it can be viewed here:
<http://openid.net/svn/listing.php?repname=specifications&path=% 
2F&rev=0&sc=1>

To summarize the open issues:

a) ax.mode vs multiple URIs

b) No useful gain for the OP to signal why a (required) attribute was  
not supplied; the RP needs to do data validation anyhow and decide  
what to do next based on the values it has received.

c) How to encode an "unavailable attribute" in a fetch response:
	blank value (current)
		con: overloads possible legitimate blank values for attributes
		pro: unlikely an RP will be satisfied with a blank value for a  
required attribute
	omitted attribute
		con: RP may not be sure that the OP processed the request

Using the same reasoning as in b), I would say omitting an attribute  
in a response would be just as useful to the RP. Opinions?


Thanks,
Johnny