Added implication is that, by defining "sreg" class, we can effectively roll sreg into AX.
=nat On Thu, Dec 18, 2008 at 1:10 PM, Nat Sakimura <[email protected]> wrote: > P.S. I and Hide Nara was talking the other day that it probably would be > very useful for the AX to be able to define a "class" of attributes to > define a set of attributes. > > For example, "Creadit Card" class includes following paramters: > 1. FullName > 2. Card Number > 3. Expire Day > 4. Secure digits > > AX parameters like this: > openid.ns.ax = http://openid.net/srv/ax/2.0 > openid.ax.class.card = http://visa.com/netcard/1.0 > openid.ax.class.card.fullname="Bill Gate" > openid.ax.class.card.cardnumber = "4312 4324 5353 1111" > openid.ax.class.card.expire = "04/10" > openid.ax.class.card.secure="343" > > Without class paremeter: > openid.ns.ax = http://openid.net/srv/ax/2.0 > opneid.ax.type.fullname= http://visa.com/netcard/1.0/fullname > opneid.ax.type.cardnumber = http://visa.com/netcard/1.0/cardnumber > opneid.ax.type.expire = http://visa.com/netcard/1.0/expire > opneid.ax.type.code= http://visa.com/netcard/1.0/secure > openid.ax.value.fullname="Bill Gate" > openid.ax.value.cardnumber = "4312 4324 5353 1111" > openid.ax.value.expire = "04/10" > openid.ax.value.secure="343" > > With "class", the message will be shorter, and also will become easier to > extract a portion of the attributes in a semantically meaningful collection. > We can even go on and sign over only one class etc. > > Could we add something like this to the scope as well? > > =nat > > > > On Thu, Dec 18, 2008 at 1:00 PM, Nat Sakimura <[email protected]> wrote: > >> I am looking foward to it! >> >> >> On Thu, Dec 18, 2008 at 12:00 PM, Dick Hardt <[email protected]>wrote: >> >>> Breno, if you have time to update the proposal per our discussion that >>> would be fabulous! >>> >>> >>> On 17-Dec-08, at 5:07 PM, Breno de Medeiros wrote: >>> >>> We have made significant process in that in-person chat and we need to >>>> document this in proposal draft form. >>>> >>>> I could try and update the proposal for "validate request" which has >>>> tentatively been abandoned in terms of allowing meta-data to describe >>>> attributes in fetch/store requests. >>>> >>>> 2008/12/17 Dick Hardt <[email protected]>: >>>> >>>>> I've been busy with other things. :-) >>>>> I had an in person chat with Allen Tom, Eran and Breno about what they >>>>> were >>>>> thinking of. There was some discussion on the step2 list. >>>>> I have a work item to write up the scope so that we can get it started >>>>> -- >>>>> but have needed to deal with some time critical tasks before I could >>>>> start >>>>> on it -- sorry. >>>>> -- Dick >>>>> On 17-Dec-08, at 4:56 PM, Nat Sakimura wrote: >>>>> >>>>> I am very interested in it, but have not heard about it for sometime. >>>>> >>>>> What is the status right now? >>>>> >>>>> -- >>>>> Nat Sakimura (=nat) >>>>> http://www.sakimura.org/en/ >>>>> _______________________________________________ >>>>> specs mailing list >>>>> [email protected] >>>>> http://openid.net/mailman/listinfo/specs >>>>> >>>>> >>>>> _______________________________________________ >>>>> specs mailing list >>>>> [email protected] >>>>> http://openid.net/mailman/listinfo/specs >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> --Breno >>>> >>>> +1 (650) 214-1007 desk >>>> +1 (408) 212-0135 (Grand Central) >>>> MTV-41-3 : 383-A >>>> PST (GMT-8) / PDT(GMT-7) >>>> >>> >>> >> >> >> -- >> Nat Sakimura (=nat) >> http://www.sakimura.org/en/ >> > > > > -- > Nat Sakimura (=nat) > http://www.sakimura.org/en/ > -- Nat Sakimura (=nat) http://www.sakimura.org/en/
_______________________________________________ specs mailing list [email protected] http://openid.net/mailman/listinfo/specs
