[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xri] phone number in XRD?
I know I'm late to this thread, but I just wanted to amplify what Peter said. I've always thought a sensible approach is for public XRDS documents to advertise publicly available SEPs, and for private attributes (including private SEPs) to be available through those public SEPs that support authentication and authorization of the requesting party. As Peter says, a Liberty Alliance personal profile service, or a SAML authority, would be two such protocols that could be used. The other obvious one is XDI, using the XDI link contract mechanism. The basic flow in the XDI use case would be: 1) RP does XRDS discovery on the XRI to find a public XDI SEP for the User. 2) RP requests a link contract (if it doesn't already have one) from the XDI SEP for access to private attribute(s). (It's interesting to note how similar this is to OAuth step of the OAuth Consumer requesting an access token from the OAuth Service Provider.) 3) User approves link contract and XDI SEP returns it to RP. 4) RP requests the private attributes using the link contract. =Drummond > -----Original Message----- > From: Peter Davis [mailto:email@example.com] > Sent: Thursday, December 13, 2007 12:18 PM > To: Chasen, Les > Cc: Markus Sabadello; OASIS XRI TC > Subject: Re: [xri] phone number in XRD? > > what you definitely do not want to do is use the XRDS to communicate > attribute values... rather, it should identify a service endpoint, > from which attributes can be derived. For example, a Liberty Alliance > style personal profile service, or a SAML authority which may be able > to make attribute statements about the subject. > > =peterd > > > > On Dec 13, 2007, at 2:57 PM, Chasen, Les wrote: > > > I think that would be a very cool step forward. If an iphone > > understands the sip (or tel) and mailto uri schemes then this > > should be easy. The downside is that this publishes an important > > identifier publicly. I do agree with all the commentary about the > > use of services that enable communication and data sharing while > > maintaining privacy. There are lots of folks out there working on > > ways to crack that nut. > > > > contact: =les > > voice: =les/(+phone) > > chat: =les/skype/chat > > pibb me =les/+pibb > > > > > > > > > > From: firstname.lastname@example.org > > [mailto:email@example.com] On Behalf Of Markus Sabadello > > Sent: Thursday, December 13, 2007 2:47 PM > > To: Chasen, Les > > Cc: OASIS XRI TC > > Subject: Re: [xri] phone number in XRD? > > > > Woah, =les definitely has the biggest XRD I've ever seen. 13 SEPs! > > > > The reason I was asking is that I received feedback for xriPhone in > > which people suggested that there should be a button for -calling- > > the i-name you enter. And another button which would pop up the > > email client. > > > > Markus > > On Dec 13, 2007 11:34 AM, Chasen, Les <firstname.lastname@example.org> wrote: > > We don't have standardized service types for various services. I > > think that is supposed to be a part of the up coming dictionary (+) > > spec. We should start standardizing these. > > > > > > > > =les/+phone used to use a sip uri to launch a sip client. I > > Changed that to use jaxtr at some point. I think I have also used > > mailto in the past for +email. > > > > > > > > contact: =les > > > > voice : =les/(+phone) > > > > chat: =les/skype/chat > > > > pibb me =les/+pibb > > > > > > > > > > > > > > > > > > > > From: email@example.com > > [mailto:firstname.lastname@example.org] On Behalf Of Markus Sabadello > > Sent: Thursday, December 13, 2007 11:25 AM > > To: OASIS XRI TC > > Subject: [xri] phone number in XRD? > > > > > > > > What would a SEP look like that has a phone number as an endpoint? > > And an e-mail address? Do we have service types for this? > > > > Does anyone know an i-name that has such SEPs? > > > > Markus > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and all your TCs in > OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php