FAQ
From Sxip.org
Contents |
General FAQs
What is sxip.org?
Sponsored by Sxip Identity, the sxip.org open source community provides developers with resources and tools for integrating SXIP 2.0 into their websites.
With SXIP 2.0, websites can benefit from increased access to identity data -- with more, better, and richer data.
Why SXIP 2.0?
With SXIP, users are able to store their identity data at a Homesite and release data in response to requests from Membersites.
This provides users with a high degree of confidence regarding their Internet interactions, and allows sites that consume identity data to provide enhanced services to users.
To learn more about the design motivations behind the SXIP 2.0 protocol, visit sxip.net.
Sxip, SXIP, sxip and sxore. Huh?
"Sxip" is the informal name for Sxip Identity, a company that builds simple, secure and open Identity 2.0 solutions for the Web.
"SXIP" stands for the Simple eXtensible Identity Protocol, an extension of the DIX (Digital Identity Exchange) protocol, which is currently under discussion at the IETF.
When presented in lower case, "sxip" refers to the identity architecture and components based on the SXIP 2.0 protocol.
Finally, "sxore" is an identity and reputation system for blogs that uses the sxip identity architecture for user account management.
What is a Membersite?
Membersites are typically websites that consume identity data by sending SXIP 2.0 requests for user data to Homesites, websites that store user identity data. All SXIP requests are sent via the user's browser, and data is only released upon user consent.
SXIP improves Membersite Conversion Ratios, by automating the movement, release, and update of identity data, resulting in increased access to identity data: with more data, better data, and richer data.
What is a Homesite?
Homesites are websites or applications that facilitate the exchange of identity data between users and sites that request user data.
By adding Homesite functionality, a website can provide the following services: authenticate and identify users, assign identitifiers to a user's persona, provide a repository for identity data, and release that data, upon user consent, to other sites via the user's browser.
By providing these services to users, Homesites are able to establish deeper relationships with their customers and benefit from access to richer data.
Membersite developer guidelines
Where can I see a sample of a Membersite?
The test.sxip.org/membersite is a demo implementation of a sxip Membersite that developers can use to test their sxip implementations. To see how SXIP works, click [sxip in] at test.sxip.org/membersite.
sxore, an identity and reputation system for blog authors, readers and commenters, is also a working implementation of a SXIP Membersite. Sxip Identity uses sxore to moderate comments on its news-blog.
You can also set up your own Membersite by downloading the available SXIP 2.0 Membersite Development Kits (MDKs).
Check our community page for a current list of SXIP 2.0 Membersites.
What if the user does not release the requested data?
How your website processes incomplete responses depends on the policy of your organization.
The SXIP 2.0 protocol provides request parameters for indicating specific requests for each piece of identity data (called sxip properties).
For example, a Membersite can flag a requested property as required, as shown in the following example:
dix:/required=fname
fname= dix://sxip.net/contact/name/first
For more information about request parameters, see the DIX protocol at dixs.org.
For more information about the properties that are currently supported by the SXIP protocol, see the SXIP 2.0 Properties (PDF).
What if I included a required parameter in the request?
The required parameter is provided to indicate that the information you are requesting is required to complete the transaction.
Users do not have to release requested data that is marked required.
The required parameter allows websites to provide a visual cue that informs users about the nature of a request.
By indicating that the data is required (typically with an asterisk), this notifies the user of the possibility that the transaction will not be completed.
It is up to your website to establish policy on how to handle responses that do not contain data that was indicated as required in the request.
Homesite developer guidelines
Where can I see a sample of a Homesite?
homesite.sxore.com is a sxip Homesite implementation operated by sxore, a comment managing service for bloggers.
The test.sxip.org Homesite is a demo implementation of a sxip Homesite that developers can use to test their sxip implementations.
You can also set up your own Homesite by downloading the available Homesite packages.
Check our community page for a current list of sxip Homesites.
How do I handle users who don't have a website?
As most people probably don't have their own website, we recommend that Homesite developers provide a boilerplate persona URL for each of their users in lieu of requiring them to maintain their own.