Social networking task force

Jeff Jaffe 14 May 2012

1 What we’ve done

• Tried to identify specific standards opportunities • Decided we first needed to create an architecture block diagram to show relationships • Made some progress • Liaison calls with Open Social • Initial ideas on next steps

2 Today

• Ann Bassetti: Block diagram, scenarios, narrative • Jeff Jaffe: Standardization possibilities • Steve Holbrook: Workshop opportunities • Discussion

3 Desired output

• Work plan for block diagram • With specific comments • Guidance on proposed standards activities • Consensus on workshop scoping

4 Ann Bassetti:

• Block diagram • Scenarios • Narratives • ...

5 DRAFT Social headlights Teams & Contributorstask force:

• Federated Social Web XGDIAGRAMS, / Community Group • Social Business Community Group • Social Headlights Task ForceSCENARIOS, ... Particular thanks to: Lloyd Fassett Virginie Galindo Rich Rogers Stéfane Fermigier David Robinson Evan Prodromou Alberto Manuel Ann SteveBassetti Holbrook Blaine Cook 14 May 2012Harry Halpin Ruinan Sun Jeff Jaffe Laurent Walter Goix ... apologies to anyone overlooked! 6 DRAFT Social headlights What we're askingtask force: & doing

Seeking to determine: DIAGRAMS, • Essential components ofSCENARIOS, "social networking" ... • Relationships between parts • Characteristic scenarios and narratives • Basis set and tests • What technologies and standards exist? • Where was that work done?Ann Bassetti • Is more needed? 14 May 2012 • Should W3C play a role?

7 DRAFT Social headlights Essential components?task force:

• A question covering suchDIAGRAMS, a large area… • Methodology SCENARIOS, ... • Criss-crossing the social web principles • Listing all the components • Classifying them • Into groups, by standardization body, by technology Ann Bassetti 14 May 2012  Here is the result …

8 What are essential components of "social networking" or "social web"?

Harry Halpin, Evan Prodromou based on work in Federated Social Web group

9 David Robinson additions

(annotations by Ann Bassetti)

" from here from "

Stteams moved "Activity "Activity moved

*NOTE: needs to be checked to make sure I found all additions and changes 10 Human interactions Ann Bassetti additions Key Sharing Messaging Group Dynamics Newsfeed Reactions (e.g., Community, Standardized at W3C Text E-mail like Data structures Comments Team) W3C Community Group • SMTP • Atom • Salmon Links Create • SIOC Standardized at another body • OExchange Text chat (includes • ActivityStreams Standardization candidate Re-share 1:1 and 1:multiple; Join / Un-join No standards body Images also includes "Live Subscription Known IP issues Chat" such as with End / Close • OStatus Like / rating Video Helpline person) •XMPP Membership list(s) Embedding Recommendations Audio •IRC • oEmbed Group list(s) • Embedded Tasks Voice chat Experience Tags • Jingle Distribution list(s) About the human * Events • STP Alerts / Notifications Identity Social Graph Profile Workflow Video chat •Routing •Given/family Contacts Profile page ?? name •Signatures Forward / reply • Portable Contacts • (might be part of Username(s) • FOAF Profile data Location others or part of •Assigned • vCard •hCard 'Sharing") Ubiquitous attributes number(s) (e.g., • XFN •vCard Bookmarks governmental) •ActivityStrea.ms •Threading Threaded • .... Groups •Portable Contacts Status discussions (e.g., •Sorting (by 'likes', 'most recent',...) •... •Presence bulletin board; •Hyperlinks Addressing Brands •Microblog includes "Idea •Variable device display •snail mail address Presence Generation / Jam") •Variable security settings •email address Access control ?? •... •URI Location

*Note: inside corporate firewall one has professional Skills Technical foundations profile, separate from one's personal profile.

Client Widgets Analytics Real-time Login credentials Data structures Notifications • OpenID • JSON (Activity Streams, Portable Contacts) JavaScript Embedded Engagement • OAuth • XML (Atom, XRD) • OpenSocial • OpenSocial Mobile • WebID • RDF (FOAF, SIOC) • WebIntents Scoring • Browser ID External Browser Content 'structures' REST Recommendations • Wiki • OpenSocial Discovery • Blog • ActivityPub Trends •, LRDD • HTML+ • •SWD •Open Graph • Microblog 11 Human interactions All contributions merged; no technologies

Sharing / Messaging Group Dynamics Collaboration / Reactions Collaboration (e.g., Community, Newsfeed E-mail like Comments Team) Text Data structures Text chat (includes Create Re-share Document 1:1 and 1:multiple; Subscription also includes "Live Join / Un-join Like / rating Links Chat" such as with Embedding Helpline person) End / Close Recommendations Images Alerts / Voice chat Membership list(s) Notifications Tags Video Video chat Group list(s) Audio Forward / reply Distribution list(s) Tasks (might be part of About the human * others or part of Events 'Sharing") Identity Social Graph Profile •Given/family Contacts Profile page ?? Workflow Connected objects name • Routing •User name(s) Groups Profile data •Signatures Mobile Ubiquitous attributes •Assigned • number(s) (e.g., Brands Presence Location Threading •Sorting (by 'likes', 'most recent',...) governmental) • Access control ?? Location Bookmarks •Hyperlinks .... •Variable device display Skills Status •Variable security settings Addressing •Presence •Search •snail mail address •Microblog •Biz/Mining Intelligence (??) •email address •... •URI

* Note: professional profile, inside corporate firewall, Technical foundations is separate from one's personal profile.

Client APIs Widgets Analytics Real-time Login credentials Data structures Content Notifications 'structures' JavaScript Embedded Engagement • Wiki Mobile Discovery • Blog REST External Scoring • HTML+ Browser • Microblog Recommendations Trends 12 Adding technologies, standards, and who is doing. (Not complete)

Human interactions Key Sharing / Messaging Group Dynamics Collaboration / Reactions Standardized at W3C Collaboration (e.g., Community, Newsfeed E-mail like Comments W3C Community Group Team) Text • SMTP Data structures • Salmon Standardized at another body Create • Atom Standardization candidate Document Text chat (includes • SIOC Re-share Independent standard group • CMIS 1:1 and 1:multiple; Join / Un-join • ActivityStreams also "Live Chat" • JRD (XRD, JSON) Public standard Links such as with End / Close Like / rating No standards body • OExchange Helpline person) Subscription •XMPP Known IP issues Membership list(s) • OStatus Recommendations Images •IRC Group list(s) Embedding Video Voice chat • oEmbed • Jingle Distribution list(s) • Embedded Audio • STP Experience

Tasks Video chat Alerts / Notifications Events Forward / reply (might be part of Workflow others or part of •Routing 'Sharing") •Signatures Threaded Location discussions (e.g., bulletin board; Bookmarks includes "Idea Generation / Jam") Status •Presence Connected objects •Microblog •Salmon

OMA MobSocNet Mobile •OMA Push

13 Adding technologies, standards, and who is doing. (Not complete)

Key Standardized at W3C W3C Community Group Standardized at another body Standardization candidate Independent standard group Public standard No standards body Known IP issues

About the human *

Identity Social Graph Profile •Given/family Contacts Profile page ?? name • Portable Contacts •User name(s) • FOAF Profile data •Assigned • vCard •hCard number(s) (e.g., • XFN •vCard governmental) •ActivityStreams • .... Groups •Portable Contacts •OpenSocial Addressing Brands •snail mail address Presence •email address Access control ?? •URI Location

*Note: inside corporate firewall one has professional Skills profile, separate from one's personal profile.

14 Adding technologies, standards, and who is doing. (Not complete)

Key Standardized at W3C W3C Community Group Standardized at another body Standardization candidate Independent standard group Public standard No standards body Known IP issues

Technical foundations

Client APIs Widgets Analytics Real-time Login credentials Data structures Content Notifications •JSON 'structures' JavaScript Embedded Engagement • OpenID • • Wiki Mobile • OAuth Activity Streams • • Blog REST External Scoring WebID •Portable Contacts • HTML+ Browser • Browser ID •XML • Microblog Recommendations •Atom Discovery •XRD Trends •Webfinger, LRDD •RDF •SWD •FOAF •Open Graph •SIOC •HTML5

15 Adding technologies, standards, and who is doing. (Not complete)

Key Standardized at W3C W3C Community Group Standardized at another body Standardization candidate Independent standard group Public standard No standards body Known IP issues

Ubiquitous attributes •Threading •Sorting (by 'likes', 'most recent',...) •Hyperlinks •Variable device display •Variable security settings •Search •Biz/Mining Intelligence (??) •...

16 "Mobile" equilibrium of specifications

Laurent Walter Goix contribution

OMA MobSocNet

OpenSocial OMA Push OStatus OExchange

ActivityStreams

WebFinger Portable Contacts OpenID

Key Standardized at W3C W3C Community Group Salmon Host- Standardized at another body Standardization candidate Independent standard group Public standard PubSubHubbub No standards body Known IP issues XRD/S 17 Layer view

Blaine Cook contribution (Not complete.)

18 Layer view, continued

19 DRAFT Social headlights Additional perspectivestask force:

• Having described the social web components by categories, making sureDIAGRAMS, everything is there… • Human interaction SCENARIOS, ... • About the human • Ubiquitous attributes • Technical foundations • We may want to organizeAnn items Bassetti in a different way • to identify relationships14 May 2012 • to identify the Basis Set • to identify essential tests 20

DRAFT Social headlights Scenarios & taskNarratives force:

• Scenarios are the activitiesDIAGRAMS, that drive the diagram. • What is the canonical set of social networking scenarios? Examples: SCENARIOS, ... • Update personal information • Explore a social graph • Share information • Provide a reaction • ... Ann Bassetti • Can we write narratives14 to May describe 2012 each scenario? • Samples: http://www.w3.org/wiki/SocialWebHeadlightsTaskForce 21 DRAFT Social headlights Basis set task force:

"Basis Set" = the irreducible list of 5-10 components that are the top-level description of the blockDIAGRAMS, diagram Example: in the OSI model,SCENARIOS, the basis set is 7 layers ... Initial proposed social networking basis set: 1. Identity and addressing (includes profile) 2. Data (text, documents, etc.) 3. Sharing infrastructure (events, location, status) 4. Linking to more information (posting, hyperlinks, search) 5. Group dynamics (create groups, membership lists, social graph) Ann Bassetti 14 May 2012 6. Transport / messaging 7. "Feeds" management 8. Reactions 22

DRAFT Social headlights Tests task force:

How to test if we have theDIAGRAMS, correct Basis Set: • If, every time we describeSCENARIOS, a scenario: ... o it uses the basis set; and o these technology categories are used in roughly the same way each time • ... then we have correctly described the underlying technology. Example: With data communications,Ann Bassetti every time a message is sent, it goes14 May through 2012 the 7 layers in approximately the same way

23 DRAFT Social headlights Current worktask summary force:

Multiple efforts on how to represent a complicated subject area, including: DIAGRAMS, o Component parts SCENARIOS, ... o Relationships o Scenarios o Tests o Standards to-date Ann Bassetti o Who's doing what 14 May 2012 ... toward answering "what, if anything, would best role of W3C?" 24 Jeff Jaffe:

•Standardization possibilities

25 Standardization possibilities

• Within the social space there are many potential areas for standardization • The block diagram helps clarify • Some are already underway elsewhere • Some have not started and could be opportunities for W3C • But we also ask whether there are unique opportunities for W3C • Here’s one!

26 Developers want common APIs to get at social data

• Sites who want to be part of a standardized social web can share social data in "near real-time" via server-to-server federation --- but many do not. • Today, several sites use OpenSocial • Other, significant sites open their APIs to developers, but do not use any standard • Developers are forced to customize applications to individual sites • But every social site sits on top of a browser • Browsers can get access to social data and provide a standard social view (APIs) to developers 27 How would this work?

• For example, users could download their profile data into their browser • Don’t they want to own their profile data? • A standard browser API could make this available uniformly across applications • Contact information • APIs to manage this information • Protocols to socialize this with other sites • Data formats • Candidate specs exist as starting points • This could be repeated for other information in the social world 28 Putting it all together

http://www.w3.org/Talks/Deck/identity/identity-hub-api.svg 29 Steve Holbrook:

•Workshop Opportunities

30 Discussion

• Questions?

• Reactions?

• Suggestions?

• Want to help?

31