Twitter API Annotations

21,902 views
21,306 views

Published on

A very preliminary look at @twitterapi annotations

Published in: Technology
4 Comments
37 Likes
Statistics
Notes
No Downloads
Views
Total views
21,902
On SlideShare
0
From Embeds
0
Number of Embeds
6,621
Actions
Shares
0
Downloads
215
Comments
4
Likes
37
Embeds 0
No embeds

No notes for slide



















  • Twitter API Annotations

    1. Annotations #twannotations @warblecamp @warblecamp TM May 8, 2010
    2. giving antalk on annotations at entitled giving a @ignite talk at @chirp @warblecamp "energy / tweet". about 2 minutes ago via mobile web from Kings Cross, London Fort Mason, San Francisco
    3. AFT DR
    4. What is ?
    5. What is ? ‣ Content distribution engine ‣ for people ‣ by people ‣ Has properties of ‣ fanout ‣ real-time ‣ Generalized messaging bus?
    6. What does do?
    7. Context is everything
    8. Context is everything ‣ #twannotations ‣ increases search & streaming ability ‣ “out of conversation” ‣ @warblecamp ‣ directs the message ‣ references an entity ‣ Kings Cross, London ‣ adds the first three dimensions
    9. What do annotations look “ like?
    10. AFT DR
    11. What do annotations look like? ‣ Every annotation has ‣ a “type” [{type1 => {attribute => ‣ type maps to attribute and 1 val1, attribute2 => val2, value pair ..., ‣ Types can be repeated but attributen => valn}}, attributes in each annotation {type2 => {attributen ... +1 }}, cannot be ... ] ‣ Store an array of annotations per tweet ‣ Same “visibility policy” as tweets
    12. What do we put in the annotation? ‣ Anything you want! ‣ will lead by example => val1, [{t ype1 => {a ttribute1 ‣ publish some guidelines attribute2 => val2, on how people could use ..., attributen => valn}}, them ...}}, {t ype2 => {a ttributen+1 ‣ No annotation “validation” ... on our side ] ‣ will publish usage and adoption statistics
    13. Watching “The Vampires of Venice” [{“tv episode”=>{“episode”=>“The Vampires of Venice”, “series”=>“Dr. Who”, “air date”=>“8 May 2010”}}]
    14. Use cases
    15. Use cases ‣ Explicit discovery for conversational content ‣ Extending the notion of @replies to generic entities ‣ Capturing structured actions and emotions (instead of inferring or parsing emoticons) ‣ IPC mechanism between applications
    16. Launch
    17. Launch ‣ APIs ‣ represented all through the REST API ‣ support in Streaming API ‣ track an annotation type ‣ track an annotation type and value ‣ possibly support in Search API ‣ Annotations “explorer” ‣ statistics of most used, most adopted, and trending annotations ‣ wiki page so developers can document their annotations ‣ Best practices document from
    18. Marcel Molina @noradio
    19. Questions? Follow me at twitter.com/raffi TM

    ×