XRDSP Use Cases

From I-names Development Wiki

Jump to: navigation, search

Contents

About

This page provides the basis use cases for the XRDSP protocol.

Overall Goal

XRDSP addresses the issues of interoperability between XRDS providers and third-party service providers (XRDS Consumers) that will enable a smooth, user-centric, experience for individuals who have identifiers that are resolvable to XRDS documents.

Players

  • Jane - an individual who has an OpenID URL provided by abc.com. Her openID is jane.abc.com.
  • Fred – an individual who has an OpenID i-name provisioned at brokerX. His i-name is =fred. Fred also has an OpenID URL openid.bol.com/fred.
  • BrokerX – an XDI.org accredited i-broker who sells i-names.
  • ABC.Com – a free provider of OpenID URLS.. just give an email address and you can have an OpenID.
  • BOL – An online service that gives an OpenID URL to all of it's paying customers.
  • AServ – a service that wants to sign-up people with XRDSs to use their service. In order to function correctly Aserv must add 2 SEPs to its members XRDS document.

XRDS Providers

BrokerX, ABC.COM and BOL are all XRDS Providers. XRDS Providers are the entities that have the ability to change the contents of an XRDS or grant permission for edits to take place. Service Provider to XRDS Provider Scenarios

  1. Fred and Jane both arrive at Aserv and want to signup for the service. They both need 2 SEPs added to their XRDS documents.
  2. Aserv has a change to their service offering and need to add a new SEP to the XRDS documents of all of their users.
  3. Fred stopped paying his Aserv bill and Aserv deactivates Fred's service, would like to remove the SEPs from Fred's XRDS Document.
  4. Aserv changes one of their services and wants to change the SEPs in the XRDS Documents of all their users XRDS Documents.

XRDS Provider to XRDS Provider Scenarios

  1. Fred wants to add an eqivID relationship between his BOL and BrokerX identifiers.
  2. Having signed up for Aserv with his =fred identifier Fred wants to add a SEP ref to his BOL XRDS to that he can use the Aserv service with his BOL account.
  3. While purchasing his global i-name BrokerX asks Fred if he wants =fred to be his 'primary' identifier. Fred says, yes, so BrokerX asks Fred for his other OpenIDs and adds 'default' SEP refs that point to the =fred XRDS document.

XRDSP Requirements

Retrieved from "http://dev.inames.net/wiki/XRDSP_Use_Cases"