Nicolas Pastorino - REST + recommendation, consume the right content, anywhere - IPC11

REST +
Recommendation:
consume the
right content,
anywhere

REST +
Recommendation:
consume the
right content,
anywhere
Nicolas Pastorino - nfrp@ez.no
Director Community - eZ Systems
@jeanvoye - http://share.ez.no

REST +
Recommendation:
consume the
right content,
anywhere
International PHP Conference 2011 - Mainz - October 10th

Nicolas Pastorino - nfrp@ez.no
#ipc11 Director Community - eZ Systems
@jeanvoye - http://share.ez.no

Our agenda :

Multichannel emotion

Our agenda :

REST

Our agenda :

REST
Extensible REST API

Our agenda :

REST
Extensible REST API
Content recommendation

Multichannel : emotion

3

Online content touches
you, it spurs emotions
anywhere, on any
device

You are consuming
content, all the time

Multichannel
content
distribution is
“emotions
anywhere”

Pre-requisites to multichannel distribution

Nicolas Pastorino - IPCse11 30/05/2011 8


Separation of layout
and content at the 1
content source level




Do not compromise on
user experience 2




“The Superman Effect” Aral Balkan, DPC11
user experience 2




user experience 2
“There is a lot of effort going into improving
customer experience. It is key to get
consistency across different channels so their
experience does not vary” Jim Daviesni




user experience 2
Have a single source experience does not vary” Jim Daviesni
of content 3




user experience 2
Have a single source experience does not vary” Jim Daviesni
of content 3
“Publishers usually can't afford a dedicated
editorial team per channel”


Are 3
rules of
thumb
enough
?

Are 3
rules of
thumb
enough
We’re
? hardly
off the
ground.

Let’s dig
further...

Single
Content
Source / CMS

Monetized
Content
Streams

Single
Content
Source / CMS

Monetized
Content
Streams
Mobile
Applications
Single

/
Smartphones, Tablets

Content
Source
CMS

Monetized
Content
Streams
Mobile
Applications
Single

/

Content
Source
CMS Push 3rd party
CRM, ERP
Content
Newsletters

Monetized
Content
Streams
Mobile
Applications
Single

/

Content
Source
CMS Push 3rd party
CRM, ERP
Content
Newsletters

Print
Legacy publication chains

Monetized
Content
Streams
Mobile
Applications
Single

/

Content
Source
CMS Push 3rd party
CRM, ERP
Content
Newsletters

Print
Legacy publication chains

Social Media

"Multichannel media consumers have higher levels
of engagement than those present in only one
channel.

The more one watches TV, listens to the radio,
spends time online, etc., the more advertising they
consume.

This shows that multichannel content
distribution will also have an important impact
on the publishers revenue structure. It will
evolve to become a competitive, critical, enabling
technology for marketing communications."

Having a
REST ?
:)

We are
not there
yet, let’s
dig further

“Media companies as well as consumer brands must
recognize that adding mobile to the multichannel mix
does not mean creating a mini-channel. Those
building mobile strategies should recognize that:

• Mobile is not just about shrinking the
desktop experience,

• The user environment is an element of the
(mobile) experience,

• Mobile users are not simply a subset of
online users – some are new.”

Least
Common
Denominator :
a REST API

Those were
the
functional
basics to
increase
your
REACH
through
multiple
channels

Those were
the
functional
basics to
increase
your
REACH Now
through come
the
multiple technical
channels bits

REpresentational
State
Transfer

REpresentational
State
Transfer
REST is a set of principles that define how Web standards, such as
HTTP and URIs, are supposed to be used.

• Give every “thing” an ID
• Link things together (“HATEOAS”) (cf David Zuelke’s keynote)
• Use standard methods
• Resources with multiple representations
• Communicate statelessly

REpresentational
State
Transfer
REST is a set of principles that define how Web standards, such as
HTTP and URIs, are supposed to be used.

• Give every “thing” an ID
• Link things together (“HATEOAS”) (cf David Zuelke’s keynote)
• Use standard methods
• Resources with multiple representations
• Communicate statelessly

h"p://www.infoq.com/ar4cles/rest-‐introduc4on
h"p://en.wikipedia.org/wiki/Representa4onal_State_Transfer

REpresentational
State
Transfer


REpresentational
State
Transfer
Key goals of REST include:

• Scalability of component interactions
• Generality of interfaces
• Independent deployment of components
• Intermediary components to reduce latency, enforce security and
encapsulate legacy systems


Extensible REST API
at the core of the eZ Publish CMS

19

At the core of the eZ Publish CMS
Extensible REST API

REST as a core feature


Extensible REST API

Dedicated front-controller


Extensible REST API

REST setup

REST
eZP
REST
request
FC

eZ
Publish
web-‐request


Extensible REST API

Mapping content into
resources


Extensible REST API

Makes data available


Extensible REST API

Makes data reusable


Extensible REST API

Content is essentially
liberated


Extensible REST API

URI pattern


Extensible REST API

Just a token to trigger your rewrite rule

Call +
GET Host / Preﬁx / Provider / Version / params

ezpRestPreﬁxFilterInterface


Extensible REST API

Preﬁx Just a token to trigger your rewrite rule

Provider


Version


Preﬁx ﬁlter

Current provider

Current parsed version value


Versioned API

class ezpRestRouter extends ezcMvcRouter
{
public function createRoutes()
{
// ezpRestApiProvider
$routes = array(
new ezcMvcRailsRoute( '/content/node/:nodeId/listAtom', 'ezpRestAtomController', 'collection' ),
new ezcMvcRailsRoute( '/content/node/:nodeId/list', 'ezpRestContentController', 'list' ),
new ezcMvcRailsRoute( '/content/node/:nodeId', 'ezpRestContentController', 'viewContent' ),
new ezcMvcRailsRoute( '/content/node/:nodeId/fields', 'ezpRestContentController',
'viewFields' ),
new ezcMvcRailsRoute( '/content/node/:nodeId/field/:fieldIdentifier',
'ezpRestContentController', 'viewField' ),
new ezcMvcRailsRoute( '/content/object/:objectId', 'ezpRestContentController', 'viewContent' ),
new ezcMvcRailsRoute( '/content/object/:objectId/fields', 'ezpRestContentController',
'viewFields' ),
new ezcMvcRailsRoute( '/content/object/:objectId/field/:fieldIdentifier',
'ezpRestContentController', 'viewField' ),

new ezpRestVersionedRoute( new ezcMvcRailsRoute( '/foo', 'myController', 'myActionOne' ), 1 ),
new ezpRestVersionedRoute( new ezcMvcRailsRoute( 'e/foo',
'myController2 or myControlerWhichExtendsmyController',
'myBetterAndScalingAction' ), 2 ),
);
return ezcMvcRouter::prefix( '/api', $routes );
}
} Nicolas Pastorino - IPCse11 30/05/2011 29

Versioned API

ezpRestVersionedRoute
Version

makes the notion version a
part of the routing decision

Extensible REST API

Build your own ﬂavor,
extend the interface(s)


Extending the interface

REST providers


Extending the interface

ezpRestProviderInterface


Overview of hooks
the places where you can go wild.

Route setup - Example
class ezpRestRouter extends ezcMvcRouter
{
public function createRoutes()
{
$providerRoutes = ezpRestProvider::getProvider
( ezpRestPrefixFilterInterface::getApiProviderName() )->getRoutes();

$routes = array(
new ezpMvcRailsRoute( '/fatal', 'ezpRestErrorController', 'show' ),
new ezpMvcRailsRoute( '/http-basic-auth', 'ezpRestAuthController', 'basicAuth' ),
new ezpMvcRailsRoute( '/login/oauth', 'ezpRestAuthController', 'oauthRequired' ),
new ezpMvcRailsRoute( '/oauth/token', 'ezpRestOauthTokenController', 'handleRequest'),

// ezpRestVersionedRoute( $route, $version )
// $version == 1 should be the same as if the only the $route had been present
new ezpRestVersionedRoute( new ezpMvcRailsRoute( '/foo', 'myController',
'myActionOne' ), 1 ),
new ezpRestVersionedRoute( new ezpMvcRailsRoute( '/foo', 'myController',
'myActionOneBetter' ), 2 ),

);

return ezcMvcRouter::prefix( '/api', array_merge( $providerRoutes, $routes ) );
}
}


Extensible REST API
Key features

37

Key features
Extensible REST API

Content resources


Key features

GET /[api]/v1/content/object/
<objectId>/fields HTTP/1.1


Key features

fields/<fieldname>

type (datatype string)

identifier (attribute identifier)

value (string representation of data)

id (object attribute numerical ID)

classattribute_id (class attribute numerical ID)


Key features

GET /[api]/v1/content/object/
<objectId>/field/
<FieldIdentifier> HTTP/1.1


Content Recommendation
YooChoose, eZ Recommender Engine

42

A tough selection needs to
be made amongst the infinite
amount of content published


Which
one is my
slope ?

I only have 30
minutes a day,
which posts
should i read ?


Doesn’t it
feel like this
sometimes :

One sometimes needs a
helping hand to choose the
right slope to ride, the right
content to consume

One sometimes needs a
helping hand to choose the
right slope to ride, the right
content to consume
Content
recommendation


Track content
consumption



Track content
consumption

+

Learn content
metadata



Track content
consumption

+

Learn content
metadata

=

Content Recommendation


Cloud-based learning of behaviors using
• Events
“Viewing, Purchasing, Rating, Sharing”

• Models
Users who viewed A also viewed B

• Stereotypes
Affinity calculated against larger sets of
content


Hybrid filtering
Increasing recommendation quality by combining
methods for qualifying behaviors



Hybrid filtering
Content-based
filtering
 “Content like this”

~



Hybrid filtering
Content-based Collaborative
filtering filtering
 “Content like this”  “Customers who
were interested in
this product also
bought …”

~



Hybrid filtering
Content-based Collaborative Community- Stereotype- Context-based
filtering filtering based filtering based filtering filtering
 “Content like this”  “Customers who  “Customers like you  Recommendation  Recommendation
were interested in also bought …” combines content depends on
this product also cluster with affinity location, time,
bought …” vectors mood, environment
…

Rock

~ ~ Pop

R&B



Hybrid filtering
Content-based Collaborative Community- Stereotype- Context-based
filtering filtering based filtering based filtering filtering
 “Content like this”  “Customers who  “Customers like you  Recommendation  Recommendation
were interested in also bought …” combines content depends on
this product also cluster with affinity location, time,
bought …” vectors mood, environment
…

Rock

~ ~ Pop

R&B

+ A/B testing + near cold-start recommendations



I/O through REST

Native connection with any HTTP-enabled client
( simple with PHP, native extension for eZ
Publish CMS )

Cloud-based : scales

Different methods for event tracking : JS, built-in
the CMS,

Famous Last Slides

51

RECAP

REST

RECAP

REST
Extensible REST API

Find me on Twitter : @jeanvoye

Rate this talk : http://joind.in/3852
Slides available soon at http://slideshare.net/jeanvoye

eZ Community
http://share.ez.no

eZ Publish Community Project
https://github.com/ezsystems/ezpublish
http://share.ez.no/download
http://share.ez.no/get-involved
Thank you !
YooChoose, recommendation engine
http://www.yoochoose.com

eZ Systems & eZ Publish Enterprise Edition
http://ez.no

Nicolas Pastorino - REST + recommendation, consume the right content, anywhere - IPC11

Recomendados

Recomendados

Mais conteúdo relacionado

Destaque

Destaque (6)

Semelhante a Nicolas Pastorino - REST + recommendation, consume the right content, anywhere - IPC11

Semelhante a Nicolas Pastorino - REST + recommendation, consume the right content, anywhere - IPC11 (20)

Mais de Nicolas Pastorino

Mais de Nicolas Pastorino (8)

Último

Último (20)

Nicolas Pastorino - REST + recommendation, consume the right content, anywhere - IPC11