MediaMosa and Open Webservices API

AS Inhoudelijke Verdieping
Utrecht, 25 Oktober 2010
MediaMosa and
Open Webservices / Open API
`
Frans Ward
Technical Product Manager
SURFnet Advanced Services
Frans.Ward@surfnet.nl
Monday, October 25, 2010

MEDIAMOSA AND OPEN WEBSERVICES/API
WHAT IS OPEN?
• Open Source (MediaMosa, FFmpeg)
• Open Codecs (h.264, theora,VP8)
• Open Media Formats (Mpeg4, ogg,WebM)
• Open Standards (HTML 5)
• OpenTechnology (Open API)
• Open Content (Creative Commons)
• Open Principles (OpenVideo Alliance)
• Open License (Royalty Free vs ‘Forever Free’)
Inhoudelijke Verdieping ‘MediaMosa en Open webservices’ - Utrecht, 25 Oktober 2010
SURFnet. We make innovation work

MEDIAMOSA AND OPEN WEBSERVICES/API
WHAT IS OPEN?
• Open Source (MediaMosa, FFmpeg)
• Open Codecs (h.264, theora,VP8)
• Open Media Formats (Mpeg4, ogg,WebM)
• Open Standards (HTML 5)
• Open Technology (Open API)
• Open Content (Creative Commons)
• Open Principles (OpenVideo Alliance)
• Open License (Royalty Free vs ‘Forever Free’)

OPENVIDEO PRINCIPLES
OPENVIDEO ALLIANCE
1. Authorship andViewing
2. Open Standards forVideo
3. Open Distribution
4. A Rich, Participatory Culture
5. Civil Liberties and Basic Rights

OPENVIDEO ALLIANCE
Het creëren, bewerken en afspelen van video zou gemakkelijk
en toegankelijk moeten zijn, middels gratis en open source
toepassingen.

OPENVIDEO ALLIANCE
Videostandaarden zouden open, uitwisselbaar en
vrij van patenten en royalties moeten zijn.

OPENVIDEO ALLIANCE
Videoplatformen zouden neutraal moeten opereren en open
standaarden en licenties moeten ondersteunen.

OPENVIDEO ALLIANCE
Wetgeving mag participatiecultuur niet ontmoedigen.
Videomateriaal zou beschikbaar en toegankelijk moeten zijn zonder
technologische restricties of andere beperkingen.

OPENVIDEO ALLIANCE
Mensen hebben het recht op deelname in een democratie, privacy,
vrijheid van meningsuiting en distributie van eigen creaties vrij van
censuur of beperkende gebruiksvoorwaarden.

OPENVIDEO CONTENT
CREATIVE COMMONS
The user / owner / uploader needs to
determine if and which type of CC-license

MEDIAMOSA AND OPEN WEBSERVICES
OPEN API
A new API for MediaMosa
MediaMosa Technology Scouts

OPEN API
MediaMosa Architecture

OPEN API
Why build new webservices?
We already have them!

OPEN API
Indeed, we need to build
additional functionalities!

OPEN API
•Compare Architectures
•Build on layer 4
because there the Web Apps and Mashups
connect to...
New functionalities, because...?

OPEN API
It’s all about functionalities....
Compare this with an End User Application with some
special characteristics:
• this EUA only has an API interface
• this EGA can access all data (like the admin interface),
but is open
• In combination with oAuth also for not open data

OPEN API
!"#$"%&'("$)
*+,-+."./".)
01/1) 01/1)
2"0'12+$1)
34.(5+.16'/"'/".)
-%"$"./15")
789)
:11;)<)
:11;)=)
:11;)>)
:11;)?)
:11;)@)
MediaMosa now

OPEN API
!"#$"%&'("$)
*+,-+."./".)
01/1) 01/1)
2"0'12+$1)
34.(5+.16'/"'/".)
-%"$"./15")
789)
:11;)<)
:11;)=)
:11;)>)
:11;)?)
:11;)@)
A-".)9-')
MediaMosa in the future

OPEN API
!"#$"%&'("$)
*+,-+."./".)
01/1) 01/1)
2"0'12+$1)
34.(5+.16'/"'/".)
-%"$"./15")
789)
:11;)<)
:11;)=)
:11;)>)
:11;)?)
:11;)@)
A-".)9-')
MediaMosa in the future
The MediaMosa Open API can be compared
to an end user application (EUA) with some
speciﬁc features:
• The Open API will give you easy access to
data stored in MediaMosa.
• The Open API has a webinterface only
and no user interface.
• The Open API delivers results in a generic
format (ATOM / Json) to make it easy to
use in an learning environment or mashup
platform.

OPEN API
Which API (TS: OW1)?
• Making content available
‣ Search API
‣ Feed API
• Generic presentation
‣ Atom
Atom Format: http://www.rfc-editor.org/rfc/rfc4287.txt
Publishing protocol: http://www.rfc-editor.org/rfc/rfc5023.txt
‣ Json
• Examples
Google data API: http://code.google.com/intl/nl/apis/gdata/
Twitter: http://apiwiki.twitter.com/Twitter-API-Documentation

OPEN API
Mashup Platform (TS: OW2)?
• Additional data to enrich video
‣ Wikipedia
‣ Twitter
‣ Flickr
‣ …
• Mashup Examples
Mashup platforms: http://blogs.zdnet.com/
Hinchcliffe/?p=111
Dapper: http://www.dapper.net/dapperDemo/
• Build your own web apps or
widgets
‣ needs further investigation....

OPEN API
Communicatie via Atom API (option 1)
EGA
Let the Atom API’s communicate with each other.

OPEN API
Communicatie via Mashup (option 2)
EGA
or use a mashup site to combine (MediaMosa) data

TS ‘Content in the Cloud’
Goal:
1. to provide an open
interface for sharing data
stored in an MediaMosa
environment or
MediaMosa Cloud
2. to consume data from
other open platforms
and to integrate this in
MediaMosa

A Mashup cluster that utilizes the Open API’s
of a MediaMosa cloud.
Need to have knowledge about other MediaMosa instances!

An Open API cluster where a central
MediaMosa repository knows what other
MediaMosa instances are around.

!"#$%!&'%(
)%*%(
+,%(
-(
)%*%(
+,%(
.(
+,%(-(
/01(
/2"3(
041(
'2"5$%6"(
5&66"57"(
Open Content per EUA
Open API comparable with OAI
No need for access rules

!"#$%!&'%(
)%*%(
+,%(
-(
)%*%(
+,%(
.(
+,%(-(
/01(
/2"3(
041(
'2"5$%6"(
5&66"57"(
Special Content Collections
(Academia)
Need access rules

!"#$%!&'%(
)%*%(
+,%(
-(
)%*%(
+,%(
.(
+,%(-(
/01(
/2"3(
041(
'2"5$%6"(
5&66"57"(
Open API for all open
content
Needs to know which
data is open

OPEN CONTENTVS ENDUSER-APPLICATION CONTENT
MediaMosa content can
always be presented using the
enduser application
➡ Additional using an Open
API
➡ Open content: most likely
content which is freely
available (not protected)
➡ If protected: use oAuth to
supply content using the
Open API

OAUTH
• OAuth is an open authorization
standard for APIs that does away with
logins and passwords to grant
authorization to a third-party.
OAuth is an open protocol to allow
secure API authorization in a simple and
standard method from desktop and web
applications.
http://oauth.net/
OAuth uses three parties:
client uses web service at server on behalf of user
client = mashup, server = MediaMosa open API, user = owner of video
...and a forth party: SURFfederation (authentication infrastructure)

OPEN API
API (REST)
-> video/save
-> video/list
-> video/x/update
-> video/x/delete
=> Which specs to use here?
CMIS... very heavy for video only?
=>There is no open standard for handling video this way.
Compare the OpenSocial specs. which is a common standard.
= > CAN WE USETHE OPENSOCIAL SPECS FORVIDEO?
Protocol = HTTP
(when not only open content then
use oAuth for screened/protected
content in addition.)
Data format = AtomPub
=> <XML>

<Title>....</>

...

...

<extention>

..

</extention>
</XML>

THE OPEN API IN RELATION WITHTS MEDIAMOSA-
MATTERHORN

THETECHNOLOGY SCOUTING PROJECT
!

THETECHNOLOGY SCOUTING PROJECT
!
WORK IN PROGRESS

PROOF OF CONCEPTS
DEMO:
http://api.mediamosa.surfnet.nl/

MediaMosa and Open Webservices API

Recomendados

Recomendados

Más contenido relacionado

Destacado

Destacado (16)

Similar a MediaMosa and Open Webservices API

Similar a MediaMosa and Open Webservices API (20)

Más de MediaMosa

Más de MediaMosa (20)

Último

Último (20)

MediaMosa and Open Webservices API