4. Recommenda;ons
1. Improve
double
screen
experience
in
uses
cases
2. Focus
more
on
user
experience
for
each
use
case
3. Develop
web
services
based
on
the
results
of
the
projects
4. Think
of
a
beTer
exploita;on
of
the
results
aUer
the
end
of
the
project
26-‐27
March
2012
NoTube
3rd
review
4
12. Exploita;on
• Extensive
exploita;on
ac;vi;es,
both
in
in
open/public
space
and
proprietary
– Extensive
presenta;on
tomorrow
• Some
exploita;ons
are
somewhat
unexpected
26-‐27
March
2012
NoTube
3rd
review
12
13. Con;nuous
evalua;on
• Systema;c,
throughout
the
project,
mul;ple
;mes
26-‐27
March
2012
NoTube
3rd
review
13
17. What
did
we
achieve?
• Not:
one
big
integrated
system
• Rather:
rela;vely
small
nuggets
• But:
those
nuggets
have
a
silver
lining
– Services,
APIs,
TV
data,
contribu;ons
to
standards
• Deployed,
also
outside
NoTube
– Insighcul
showcases
– Tested
in
several
cycles
• Dissemina;on:
e.g.
IBC
(twice),
MIPTV
26-‐27
March
2012
NoTube
3rd
review
17
18. Problems
&
mistakes
• Bridging
the
TV
&
Web
culture
– Proprietary
vs.
open
standards
– Reflected
in
use
cases
• Need
to
adapt
our
service
approach
• Adap;ng
to
the
swiUly
changing
reality
of
the
TV
world
– exploita;on
26-‐27
March
2012
NoTube
3rd
review
18
20. Day
1:
technical
workpackages
• Before
lunch:
– WP6
Architecture
– WP3:
User
profiling
&
recommenda;ons
• AUer
lunch:
– WP2:
TV
metadata
– WP4:
Enrichment
– WP1:
Models
&
seman;cs
• WP10:
Management
26-‐27
March
2012
NoTube
3rd
review
20
21. Day
2
• Before
lunch
– Showcases
:
demos
of
the
three
use
cases
– Exploita;on
– Dissemina;on
• AUer
lunch
– Internal
mee;ng
reviewers
– Feedback
session
– 16:00:
end
of
mee;ng
26-‐27
March
2012
NoTube
3rd
review
21