DSS 1 Problems, Offerings, Solutions
From Data Sharing Summit
For the opening of Data Sharing Summit we asked everyone who came to share what they saw as the biggest issue/problem that we were trying to solve along with what they had to offer to the group gathered (it did not have to be solution to the problem they articulated as most important). The range of answers to this inquiry is quite informative because of the range of issues that surface.
Contents |
Convergence Why not?
- Strong Authentication
- OpenID?
- Shared & Open
- Securing/trust rating
- What does it mean to "run your own identity provider"? Will relying parties be able to 'trust' it? for what kinds of claims?
Social Network Layers and Trust - User communities and sharing
- How do we delegate rights between services in the Internet environment (eg OpenID - style interactions)?
Privacy
- prevent linking (correlation)
- 'user auth (control) where expected
- Sharing friend data & intellegence
- key threat matrix
Strong Enrolement
- leverage existing authoritative sources?
What IDMs don't require a browser?
Scope of Identity Mgmt?
- Can it exist w/o dealing with questions like delegation?
- How does reputation exist? is it portable.
- How can Different Federation Interact in a Trusted Way?
- What's the open-source cardspace?
- Problem: Convergence of specs is more important than interop between specs.
- Problem: Convincing users/companies to adopt Open social graph API's + concepts etc.
- Willingness to Figure out what Yahoo! can do to be part of an open exchange system that can share our information to allow gamers to live their online lives the way they wan to and need to.
- Problem: Data Addressing Sepc HTTP based permission implicit
- Biggest Problem: Personal Data Management
- Problem: Large Scale User Adoption
- Problem: How to get conesnsus/buzz such that open graph data formats for social networking sites "required" as RSS/Attom in blog world
- Need: Easy & granular access control to date-of-birth mm/dd - mm/dd/yyyy - Age mm/dd/yyyy + hh:mm +place Permission to use & display
- Problem: we need identity rights agreements
- Identity Rights Agreement Standard
- A fresh voice to add people that been thinking about these issues more deeply than I have been on not tech perspective (eg regular web people) to a tech-heavy crowd
- Solution: oAuth API Authentication Protocol
- What did I bring An OPEN MIND to absorb the discussions & opportunities into our portal + champion to others
- The Desire to help do Interop Testing
- Offering: social Network Infrastructure - Jay Laney & Tony Stubblebine - Crowdvine
- Offer: Distribution & Integration Platform for Gaming and MMO networks
- Solution: We're building a site and are interested in fully embracing/contributing to new standards
- The Problem: Going from high-level agreements to existence proof of user-controlled interop between three or more social apps.
- I'm bringing a strong willingness to build solutions
- Problem - protect data - integrity of data *confront level and trust to promote adoption *the social side rather then the technical
- Solutions: to strive to *ease of use/simplify and expeand use *goal - collaboration in real world
- Platforms ready to adopt proposed standards (elgg, explode tba...) Ideas (simple=key) development resource
- Problem: Selling interop to both vendors ... and users! (and then import/export formats)
- Problem: Prevent graph being used for spam
- I bring AIM
- What I Brought - a poster-sized version of the "Bill of Rights" and Plaxso's Social graph
- Problem: What are you expecting from social API providers? What would an open social API look like? Needs to solve technical, legal and business model issues.
- Offer: Orkukt, gmail, google apps, igoogle
- Offer: +polydata fine grained, permission based addressing
- A "solution" or what I brought to this group: I brought the ears of the Yahoo! social platform tactical team, advising CEO - Jerry Yang on his 100day openness strategy
- Biggest problem? What are we trying to solve?
- Problem: We're moving towards opening up and democratizing information access people's lives/networks so they can do everything in one place BUT new social networks which are repetitive slightly similar clones of each other seems to be doing the opposite. Everyone is trying to sort of steal was from each other.
- Problem: Integrating people/orgs who don't choose to participate into maps/graphs/nets.
- Problem: Who owns the relationship?
- Users are Afraid
- Problem: Tension between traditional Business models & opennes & sharing is barrier. good intentions may not be enough
- A Problem: Reconciling data sharing Issues between the idealistic "bill of rights" view and the real world of TOS and International Law.
- Waht did I bring to help? Resources to direct @ people, code, t-shirts, etc. (Ability to talk louder than Marc as needed!)
- Pownce UI for claiming other URLS + Django-psn (open source)
USABILITY
- Problem: Heterogeneous social networking sites/technologies
- Problem: Every technology uses different identifiers
- Offering: Community Dictionary Service
- Offering: Demo application of Higgins IdAS
- Big Issue: Keeping the user in control of their data and privacy. And educating the community online privacy/safety.
- Solution: looking beyond destination and data silos for measures of attention and user engagement
- Solutions: We, Doostang, look to offer not another social network but a service that allows people to come to us from whenever, to get what they need-career information and leave.
- Problem: Lack of definition of "friend"
- What I offer: Accessable history of open standards & apis of what worked and what didn't, use cases and why individuals should care and do care
- Solution: Commitment to Openness & Allowing users to own * export their data.
- Solution: Clearspring provides experience integrating with Blogs, social networks, start pages, and mobile devices. We will implement any common APIs for the social graph across sites
- Problem: requiring users to recreate their social graph, profile etc and sites not sharing what should be info owned by users
- Problem: wfhat are the use cases?
- understanding and agreeing on the problems and goals
- Problem: Lack of standard APIs for (widgets) distributed appliatoins to leverage social network context. I want to learn about practical formats for users, relationships and attributes.
- The biggest problem is that multiple schemas will exist and we'll need a mapping service
- Solving: The distributed schema mapping problem
- Bring AX
- Problem Cross organizational data transfer which preserves privacy constraints and enables the user to determine the data model appropriate to their interest in how they are represented.
- Problem: Beyond the social grpah: how do we export content (status updates, photos, etc) out of the networks we populate?
- To Offer: Opinions on what information should be avaliable in an open centralized repository, and what information should not.
- What I want: Ubiquitous sharing of calendar data under control of individuals as a compelling use case of datasharing.
- There are still way to many ids/person
- The agression, management, and exchange of an individual's various personas
- Really Simple Solutions
- What we bring: A financial system that works on all credit card readers, and a growing ecosystem of consumers merchants, and communities using it.
- Offering: A community Dictionary Service
- Solution: Aggregation of data from social networks. Already have read API, working on write API - looking for common formats
- Ruby XRI - (RXRIPR)
- OS Ruby XRI Proxy resolver
- Agreement on what metadata set should be in the dictionary
- Contribution: An approach for specifying identity schema's in a computer and human readable format based on RDFs (RDF in XHTML) by which organizations an individuals who create or maintain schemas can make the schema metadata available by placing a XHTML document on the web. This approach is intended for use by OpenID AX attributes, InfoCard claim types, LDAP attributes and SAML attributes, adn for standardization in ID Commons.
- Problem: Poorly defined OPML format for sharing feeds
- Hopeing for: The "people's guidestar" an open universal service for identifying, rating, and donating to non-profits, domestic + international
- We have APIs
- Solution: Cloudtripper toolkit for portable SN+identity data
- Solution: We have a OPML validator we want to open source
- Friend Discovery + Social Network Choices
- Bringing: Real world neighborhood/community social network tools/techniques/concepts
- Bringing: 1)open mind + divers experience 2) ability/time to take best ideas and execute
- Lots of thinking & an open mind
Conflicting Interests
- offer:strong interested in Openess - international perspective & experience
- Problem: Convergence and international aspects of attribute exchange + financial and quality aspects between end user/relying party/IDP
- Solution: Practice SSO + Attri exc.
- Problem: Ensuring openID remains decentralized and owned by the entire community of users + international law
- Thoughts on APIs and data formats
- Offering: API + data format strawmen for social network portability & syncing, etc
- Problem maybe not the central problem not a key problem
- Privacy issues in a shared social grpah (personal privacy / not commercial interests)
- Problem: pretext graph being used for spam
- Problem: Selling Interop to both vendors and users (and then, import export fromats)
