Initial Notes

From Umuse

This is a forum to help facilitate and unify the discourse on how to evolve existing web technologies to deliver the promise of user-centric identity. As identity standards begin to coalesce we must consider the implications for existing systems and services. By attempting to implement identity standards as they evolve and by considering the potential they unleash we can better inform their standardization process. However, the focus here isn't simply about adapting technologies to enable identity interoperability, it's more about creating a collaborative environment to coordinate how these technologies should evolve within a user-centric environment.

Enabling identity interoperability provides the ability to create:

  • Mechanisms which offer people more autonomous control over their content.
  • More seamless relationships between people and between their content amongst disparate environments (federated identity)

By considering real-world scenarios for user-centric identity within the context of existing content-management systems and web services the hope is that we can develop a more cohesive roadmap for evolving these systems and services.

Part of the reason for trying to unify the conversation and resources in this arena is to help prevent reinventing the wheel. If there are cases where wheels are being reinvented or even if the purpose of this website seems to be trying to reinvent the wheel, please document and explain on the Reinventing Wheels page.

Contents

[edit]

Proposed Approach

  • Well coordinated baby-steps
  • Coordinating very simple proof of concepts like using OpenID for commenting in Wordpress and Textpattern and allowing for something like http://www.cocomment.com/, shared comments/posts between blogs (like trackbacks + reblog)
  • Documenting:
    • The distintion between different layers: Authentication and identity management, APIs for user-generated content, etc
    • Existing patterns and implementations for existing projects
    • What works, what doesn't, and ease of implementation
    • What makes sense for the "average user" in various contexts
    • What makes sense for developers
  • Share many of the principles of the approach to microformats, especially "Pave the cow paths"


[edit]

Some concepts to sketch out:

  • Foster nuanced, nichefied functionality amongst existing projects within a highly interoperable paradigm.
  • act as part of a larger incubator to ideate and present models to more established standardization bodies, open source initiatives, and large corporations alike.
  • Facebook API, facebook "notes" (these notes were original taken with Google Notebook)
  • API Design patterns, http://www.sourcelabs.com/blogs/ajb/2006/08/how_to_provide_a_web_api.html
  • Google Video, post to blog option - let's you login right there.
  • preventing lock-in, "mouse traps"
  • Parallel ideation process with browser innovations like Flock and Live Clipboard
  • should there be a project categorized as "social networking" on opensourceCMS.com?
  • federated identities, federated content networks
  • ubuntu, democratized process, global social web of interdependence.
  • What will the networked world have to offer generations of the One Laptop Per Child?
  • http://www.cocomment.com/, shared comments/posts between blogs (or like trackbacks + reblog)
  • trackbacks, blogbacks, blogments, etc - cross between trackbacks and reblog - also plugaid. After claiming your website URL using something like OpenID, an API could interact with the OpenID login to catch logins used to add comments on other sites and automatically reblog or recognize a trackback for that comment.


[edit]

User Experience / UI:

[edit]

OpenID login

[edit]

For Consideration:

[edit]

Some Recent Shared sentiments:


Retrieved from "http://wiki.umuse.org/Initial_Notes"