http://www.openconnections.net/docs/ 2012-02-05T18:24:48-05:00 http://www.openconnections.net/docs/ http://www.openconnections.net/docs/lib/images/favicon.ico text/html 2010-06-21T23:27:14-05:00 Todd Lucas http://www.openconnections.net/docs/protocol?rev=1277177234&do=diff Messaging The most important protocol element of a social network, beyond connection establishment, is messaging. Messages can be sent between profiles with a single sender and multiple recipients, just like with email. A great advantage to using social networks for messaging is that it eliminates spam. There is no way to send a message unless the sender's profile is authenticated against the recipient profile. text/html 2010-06-08T22:09:47-05:00 Todd Lucas http://www.openconnections.net/docs/profile?rev=1276049387&do=diff Each user in OConn has a profile. This profile represents a user's presence on the Internet. It can also be used in the context of one or more social networks or to interact with applications and games. A profile has a unique address. Because the profile is machine readable and because people typically interact with web pages, they may also use the addresses of these web pages in place of their profile address. Thus, there are many ways to get to that address. text/html 2010-06-06T20:09:01-05:00 Todd Lucas http://www.openconnections.net/docs/start?rev=1275869341&do=diff Open Connections (OConn) is a protocol and REST based API for managing profiles and relationships in a distributed fashion. It is built using standard protocols, including OAuth 2.0. OConn is under active development. As such, the content of this wiki is a work in progress. text/html 2010-06-06T20:07:03-05:00 Todd Lucas http://www.openconnections.net/docs/authentication?rev=1275869223&do=diff OConn is built using OAuth 2.0. This draft standard is currently in development and appears close to being finalized. A user's profile provider is their hub for interacting with all other profiles and OConn-enabled web sites. It is their profile data repository and means of managing privacy settings. As such, when a user connects with another person's or organization's profile, or when they sign up with a new OConn website, they trust their profile provider to limit access to their data. OAuth 2… text/html 2010-06-06T19:58:22-05:00 Todd Lucas http://www.openconnections.net/docs/applications?rev=1275868702&do=diff What is an application in OConn? It's simply a web site or web application that interacts with users. OConn makes it possible to enable web sites to be “installed” into a user's profile with the click of a button. The user gets a simple experience and the application gains an instant profile. text/html 2010-06-02T02:52:47-05:00 Todd Lucas http://www.openconnections.net/docs/api?rev=1275461567&do=diff OConn is a REST API consisting of a canonical set of URLs and multiple response formats. Because simplicity is a primary goal, there may be certain constraints or limitations in the first version. Overview The initial goals for the API are to provide support for the following: text/html 2010-05-22T15:23:25-05:00 Todd Lucas http://www.openconnections.net/docs/method%3Bapp%3Binstall?rev=1274556205&do=diff << Back to API Documentation An application issues an install request to this method. The user will be shown a confirmation message. NOTE: The method path app/install is nominal; the actual path is defined by the profile endpoint metadata. HTTP Method * GET