MediaMosa and webservices

755 views
691 views

Published on

Presentation by Herman van Dompseler at the MediaMosa Community day november 25th at SURFnet

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
755
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

MediaMosa and webservices

  1. 1. MediaMosa and Webservices<br />easy access to MediaMosa content<br />Expertise seminar MediaMosa – 25 november 2010 - Herman van Dompseler<br />&<br />Connect<br />Communicate<br />
  2. 2. Back in 2007<br />SURFnet videoservices basedon a Service OrientedArchitecture<br />Currentresult:<br />Frontend: SURFmedia + End User Applications<br />Backend: MediaMosa<br />
  3. 3. Big roleforwebservices<br />Webservices are the onlymeans of communicationbetweenMediaMosa and End User Applications<br />That’s a goodthing, <br />seperation of concerns<br />Frontend is concerned<br />withpresentation<br />Backend is concerned<br />with data<br />
  4. 4. How do theyconnect?<br />Trust relation<br />End User Applicationsapplyfor a key to useMediaMosa. <br />End User Applicationsauthenticateusingthiskey and DBUS authentication<br />End User Applications have access to their part of MediaMosa data <br />
  5. 5. How do theycommunicate?<br />Webservice request<br />REST url<br />GET /asset (with a lot of parameters)<br />http://www.mediamosa.org/node/218114<br />Webservice response<br />MediaMosa XML format<br />
  6. 6. MediaMosa XML<br />Example: /asset<br />
  7. 7. and itworks<br />that’swhy we are heretoday<br />
  8. 8. And itworks NOT likethis<br />But…<br />End usersdo notcommunicatedirectlywithMediaMosa<br />All communications is doneusing End User Applications<br />There is nopublic entranceto MediaMosa (entrance is basedon the trust relation)<br />There is nostandard XML response format<br />
  9. 9. Now in 2010<br />Technology scouting ‘Open Webservices’<br />Goal:<br /> “to provide an open interface forsharing data stored in anMediaMosa environment”<br /> “to consume data from other open platforms and to integratethis in MediaMosa”<br />Side effects:<br />New target audience: end users<br />Public entrancewith easy access<br />Standard XML response<br />
  10. 10. What is needed?<br />Open API<br />
  11. 11. There is input and output<br />Content goestwoways<br />Use the Open API to retrieve data fromMediaMosa<br />This is the easy part<br />Use the Open API to update data in MediaMosa.<br />This is more difficult<br />
  12. 12. How to connectto Open API?<br />Public Access<br />The Open API is public withanurllike:<br />api.mediamosa.org<br />
  13. 13. How to communicatewith Open API?<br />Webservice request<br />REST url<br />GET /search with standaard parameters like query, limit, order.<br />Webservice response<br />Standard XML format<br />RSS<br />Atom<br />Json<br />
  14. 14. Atom<br />Example: /search<br />
  15. 15. MediaMosa XML vs. Atom<br />What’s the<br />difference?<br />
  16. 16. How to connectfor updates?<br />The more difficult part<br />Same public url:<br />api.mediamosa.org<br />Need user management<br />NeedOauthfor user authentication<br />Needapplicationkeyfortrackingapplication and ratelimiting (notforauthorization)<br />
  17. 17. How to communicatefor updates?<br />Webservice request<br />REST url<br />POST /user/[ID]/uploadfor a ‘new’ entry.<br />PUT /user/[ID]/upload/[ID2] for updating an entry<br />DELETE /user/[ID]/upload/[ID2] fordeletingan entry<br />Content is in Atomformat, calledAtomPub.<br />Webservice response<br />Standard XML format<br />Atom<br />
  18. 18. Finally… demo’s<br />for end users & developers<br />http://api.mediamosa.surfnet.nl/<br />
  19. 19. A couple of examples<br />Have younoticedthis?<br />The difference in XML response<br />MediaMosa XML: http://api.mediamosa.surfnet.nl/displayXML<br />Atom XML: http://api.mediamosa.surfnet.nl/search?query=html5<br />ComparewithYouTube XML<br />http://gdata.youtube.com/feeds/api/videos?q=html5&max-results=10&v=2<br />End users<br />UseAtomfeed in iGoogle<br />http://www.google.nl/ig<br />Developers<br />Createmashups<br />http://api.mediamosa.surfnet.nl/cockpit?query=html5<br />
  20. 20. Next: Content in the cloud<br />
  21. 21. Next: MediaMosa & Opencast<br />
  22. 22. Wrap up<br />The current status<br />Open Webservices givenewfunctionality to MediaMosa<br />Public entrance<br />Standard XML response<br />Open webservices introducenewaudiences:<br />End users<br />(Mashup) developers<br />The Proof Of Concept shows thatitcanbedone. <br />It’s nothereyet, but we keep youposted.<br />
  23. 23. Is itrocketscience?<br />We use open standards, likeothers do<br />YouTube: Atomfeed<br />http://code.google.com/intl/nl/apis/youtube/2.0/developers_guide_protocol_understanding_video_feeds.html<br />Twitter: Oauthexample<br />http://dev.twitter.com/pages/auth<br />75 more Video API’s<br />http://www.programmableweb.com/apis/directory/1?apicat=Video<br />
  24. 24. Easy access to MediaMosa Content<br />What’s in itfor me?<br />End user<br />direct access to <br />MediaMosa content<br />Developer<br />easy integration of <br />MediaMosa content<br /> in website, ELO, etc.<br />
  25. 25. Questions ?<br />Asknow.<br />Orask later.<br />Herman van Dompseler<br />herman@dompseler.nl<br />

×