Re: SREG 1.1 Request parameters

2008-02-22 Thread Martin Atkins
Enis Soztutar wrote: As far as I understand, the distinction between sreg.required and sreg.optional is entirely in the responsibility of the consumer and there is not reason for the protocol to include this arbitrary division. An OP implementation will just merge the two fields and try

Re: SREG 1.1 Request parameters

2008-02-22 Thread Enis Soztutar
Well, I have not thought about the OP to ask the user to pass the data to the RP leveraging required/optional fields information. Thanks for the clarification. Martin Atkins wrote: Enis Soztutar wrote: As far as I understand, the distinction between sreg.required and sreg.optional is

Re: SREG 1.1 Request parameters

2008-02-21 Thread James Henstridge
On 21/02/2008, Enis Soztutar [EMAIL PROTECTED] wrote: Hi, As far as I understand, the distinction between sreg.required and sreg.optional is entirely in the responsibility of the consumer and there is not reason for the protocol to include this arbitrary division. An OP implementation