Gregory Engels Entwicklercamp 2013

More documents

Recommendations

Info

• allow simple interactions• For example : approval, rejection,simple selection, simplecommenting, upload, share etc.• simple enough interaction, so youwould not lose your current browsercontext, and return quickly to yourstream once done
Consume• A general list• The activity stream can be consumedeasily and presented within anotherapplication in order to ensure that anyuser using that application still sees theircurrent stream.• This may be useful where there is aspecific application in which users tent to'live' so that they are unlikely to be payingattention to their stream otherwise.
Page 1 and 2: Going with the Flow -Activity Strea
Page 3: Gregory Engels• Geek• Entrepren
Page 6 and 7: Actor Verb Object Target
Page 8 and 9: Person started following a person
Page 10 and 11: • http://activitystrea.ms/
Page 12 and 13: Why is the Activity Streamimportant
Page 14 and 15: User Model• Inform a user• Send
Page 16 and 17: User Model• Inform a Community•
Page 20 and 21: Consume• An application specific
Page 22 and 23: Tools - REST Client
Page 24 and 25: Tools - Java• Abdera (as an aside
Page 26 and 27: Authentication options• Anonymous
Page 28 and 29: Authentication options• Basic Aut
Page 30 and 31: Authorization• /connections/opens
Page 32 and 33: • OAuth is a open Protocol forAut
Page 36 and 37: Social Business Toolkit• SDK http
Page 38 and 39: . . . add some code . . .
Page 40 and 41: Posting an event{"actor": {"id": "@
Page 42 and 43: Title, Content, Object SummaryIf ti
Page 44 and 45: Registering your application• App
Page 46: Thank You!• Contact: Gregory.Enge

Gregory Engels Entwicklercamp 2013

Create successful ePaper yourself

Delete template?

Save as template?