<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>The LinkedTV Platform {Towards a Reactive Linked Media Management System</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jan Thomsen</string-name>
          <email>jan.thomsen@condat.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ali Sarioglu</string-name>
          <email>ali.sarioglu@condat.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Rolf Fricke</string-name>
          <email>rolf.fricke@condat.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Condat AG</institution>
          ,
          <addr-line>Alt-Moabit 91D, 10559 Berlin</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The LinkedTV Platform was developed in the EU FP7 project LinkedTV1 with the objective of supporting semi-automatically linking TV content with additional information and content. The realized approach can be used for many di erent applications and purposes, in which the LinkedTV Platform serves as the backbone connecting and managing the di erent services for analyzing, annotating, linking and enriching media resources and storing the aggregated metadata. This paper describes the subsequent evolution of the LinkedTV Platform towards a Linked Media Management System supporting exible and scalable linked media applications.</p>
      </abstract>
      <kwd-group>
        <kwd>linked media</kwd>
        <kwd>media fragments</kwd>
        <kwd>semantic media</kwd>
        <kwd>media analysis</kwd>
        <kwd>media annotation</kwd>
        <kwd>media enrichment</kwd>
        <kwd>media interlinking</kwd>
        <kwd>reactive systems</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        In recent years research e orts have sought to deal with the structured
analysis, annotation, enrichment2 and interlinking of multimedia resources, subsumed
under the label of Semantic Multimedia [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ],[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] or more recently (with the use of
Linked Data for concept identi cation and linkage) Linked Media [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], in order to
improve computer-based processing and re-use of digital media. The creation of
Linked Media covers a wide range of approaches, including media metadata
extraction, text, audio and video analyses, transcription / speech-to-text, Named
Entity Recognition (NER) and semantic similarity measures / graph
transversal to link to conceptually related resources. Once this Linked Media has been
produced it could support a wide range of speci c applications and user
experiences including Second Screen applications to complement and enhance media
consumption, media content recommendation and personalization, on-screen
information overlays and so on. However current media management does not take
1 http://www.linkedtv.eu
2 Here, we mean the association of some content with a part of the multimedia resource
based on its annotation with some concept(s), to which the content is related (e.g.
explanatory).
the support of such functionalities into account nor provide a holistic work ow
for their combination, leading to the necessity for a new type of media
management system which we call Linked Media Management Systems. The LinkedTV
Platform[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] is an example of this new type of system and was an outcome of
the EU FP7 project LinkedTV [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] which ran from October 2012 until March
2015 and has been further developed since. This paper describes the current
state of the evolution of the LinkedTV Platform to become a general solution to
Linked Media Management for future media services. In Section 2, we introduce
the concept of Linked Media Management and the functionalities required and
provide a short overview of the state of the art with related approaches. Section
3 describes the work ow as realized by the LinkedTV Platform as a result of
the LinkedTV project. In Section 4, we present the evolution of the LinkedTV
Platform towards becoming a Linked Media Management System. Section 5
concludes the paper by discussing the approach and giving a short outlook.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Linked Media Management: State of the Art</title>
      <p>Today's media service providers rely on legacy MAM systems without the
functionalities required for Linked Media, and faced with the need for costly ad-hoc
integration of diverse services to realize Linked Media it is clear that this is
currently an unassailable barrier to industry uptake.</p>
      <p>
        Based on the experience with LinkedTV we propose that Linked Media
Management Systems should support the following main functionalities:
{ Not just ingestion of media resources but also les related to them, such
as subtitles/transcriptions (SRT, VTT) or metadata descriptions such as
TVAnytime [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]
{ Analysis of video and audio tracks of a media resource with respect to
temporal or spatial aspects, such as fragmentation (to shots and scenes), object
(re-)detection, face recognition, speaker identi cation, visual concept
classication, etc. resulting in an audio-visual description of the media resource,
including temporal and spatial segments. This can be captured in e.g. an
MPEG-7 AVDP pro le [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]
{ Generation of Media Fragment URIs [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] from the pro le segments, which
supports simpli ed and Web-friendly references to temporal and spatial parts
of a media resource
{ Generation of structured annotations at the media fragment level by
classication (i.e. shot, visual concept type, detected face, etc.) and provenance
(e.g. which classi ers were used, when), preferably by using commonly
understood and used models such as the W3C Annotation Data Model [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] and
W3C PROV Data Model [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]
{ Named Entity Recognition on textual resources (subtitles, speech
transcriptions) for associating named entities such as persons, events, locations,
objects to the media fragments (semantic annotation)
{ Linking named entities to Linked Data resources on the Web, such as
dbpedia (a structured metadata representation of the information in Wikipedia),
which provide both a global disambiguation mechanism and access to
additional metadata and links
{ A repository for storing this metadata information. Given the proposed
speci cations, a graph-based storage and retrieval approach makes most sense,
e.g. RDF.
{ Connecting to enrichment services which can suggest related content such
as conceptual descriptions, Web pages or similar images/videos for media
fragments according to their annotated entities
{ Exposing this data to client applications as a Web service through a
consistent REST based interface, which is in line with service-oriented
architectures and Web-based communication, enabling any connected
application (e.g. on a SmartTV, Set Top Box or mobile device acting as a Second
Screen) to easily and asynchronously retrieve data for an enhanced media
service (e.g. LinkedTV providing related content synchronized to the TV
broadcast on a second screen)
{ Providing for manual oversight, correction and con rmation of the generated
annotations and enrichments for a media resource
{ Managing the work ow of all these di erent steps and phases
{ O ering a framework for integrating these di erent systems and services,
as well as further ones, e.g. integration with TV Program Planning or
Production Systems, streaming servers, Content Delivery Networks, Content
Management Systems, or Rights Management Systems.
      </p>
      <p>Linked Media Management is thus a complex and innovative new media
management process which connects and manages di erent kinds of services from
production to consumption of media content Fig. 1). However, a Linked Media</p>
      <p>Management System does not necessarily have to host all mentioned
functionalities locally. In line with current trends towards service-oriented architectures and
cloud-based computing, the architecture should allow the connection of external
3rd party services, open or commercial. The crucial core components are the
work ow management, the connections to the di erent services (Linked Media
Services) and the metadata store (Linked Data Repository).</p>
      <p>
        As of today Linked Media Management Systems do not exist as a category
named as such. However, there are similar and related approaches such as the
former Linked Media Framework (LMF) [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], now being continued within the
Apache Marmotta project [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], or the MICO Platform [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] (currently being
developed on top of Apache Marmotta) which is very similar to the LinkedTV
Platform approach, even down to technological choices, as we will return to in
the conclusion.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>The LinkedTV</title>
    </sec>
    <sec id="sec-4">
      <title>Work ow</title>
      <p>The LinkedTV Platform would be an example of a Linked Media Management
System. The generation, aggregation and usage of the annotated media
fragments is done through a general work ow of di erent tasks which are grouped
into three main successive work ows (Fig. 2):</p>
      <p>
        The production work ow has the objective to make the media resources
Linked Media-ready. It consists of the steps: (1) ingestion of the video itself
and related metadata (TVAnytime metadata and subtitle les), including also
an encoding to various resolutions and formats and a transfer to a streaming
server, (2) deep analysis of the video and audio tracks with various techniques
developed within the project [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], (3) serialization of the analysis results and
metadata les into a common LinkedTV data model [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] (being an RDF-based
description format making use of all kinds of existing ontologies such as the W3C
Media Ontology and which provides annotated media fragments identi ed using
Media Fragment URIs), (4) an automatic annotation of the media fragments
with provenance information, named entity recognition results and other media
resource information [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ].
      </p>
      <p>
        The publishing work ow is mainly a manually curation and enrichment
process. Its objective is to take the raw LinkedTV production data, evaluate it,
correct it (e.g. incorrect chapter segmentations) lter out unwanted data, and
most notably, enrich it by adding all kinds of related material to the various
chapters or entities by making use of a rich set of enrichment services developed
within the LinkedTV project [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. For this a speci c LinkedTV Editor Tool has
been developed [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ].
      </p>
      <p>
        The playout, consumption and personalization work ow is the process
of: (1) playing the video itself to a viewer, (2) displaying the related content either
on the same screen or a second screen depending on the respective scenario, (3)
adapting the related information to the viewers pro le, (4) reacting to viewer
events like pause, fast forward or switch channel, (5) building the user pro le out
of her implicit or explicit preferences. Steps (3) to (5) are the personalization
part of the consumption and, of course, optional; see [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ] for an overview of
personalized content delivery in LinkedTV.
4
      </p>
    </sec>
    <sec id="sec-5">
      <title>The LinkedTV Platform Evolution</title>
      <p>
        The rst version of the LinkedTV Platform was designed to linearly process the
di erent steps as depicted in Fig.2. However, as this approach does not scale very
well and is not resilient as well as not exible enough for adding new services,
the platform has been redesigned according to the principles of reactive design
(responsiveness, resilience, elasticity, message driven) [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ]. In fact, a lot of the
above mentioned tasks do not need to be executed subsequently but can run in
parallel and independently from each other. After a redesign, the new distributed
processing path can be illustrated like a \tube map" (Fig. 3).
      </p>
      <p>In this map, the black lines depict the services running locally in the LinkedTV
platform, whereas the colored ones depict the connected services provided by
third parties via REST APIs.3</p>
      <p>The LinkedTV Platform (i.e. the system running the black lines) has been
designed and implemented now in a way which maps system components
almost 1:1 to parts as depicted in Fig. 2. Thus, this gure can be read also as
an architectural diagram. Using a message driven architecture, the nodes
represent individual micro services whereas the lines represent queues. Normally, the
nodes act as consumers, reading messages from the dedicated queue, do some
processing (which may or may not include invoking external REST services) and
then produce again messages and send into the next queue. Sending messages to
several queues (like the Ingestion service does) evokes parallel processing. But
there are also pure producers (like the Providers, which initiate the processing
by sending media resources and associated metadata les to the ingestion
service) or pure consumers (like the micro service storing RDF graphs in the Linked
Data Repository).</p>
      <p>With the vision of creating an open, reactive Linked Media Management
System, this redesign has, among others, the following main properties which
are relevant in the LinkedTV context: (1) it is highly scalable as each node and
the respective queues can be multiplied so an implicit work and load balance
is ensured. Through this, a high level of elasticity and resilience is achieved. Of
course, however, the degree of these properties in the overall system is generally
limited by how reactive the connected services themselves are, so these have to
scale in the same way. (2) The system is very open as easily new queues and
new micro services can be added without a ecting current work ows. (3) It is
also quite easy to con gure new set-ups (routes) for individual clients or use
case pro les, e.g. depending on whether subtitle les are already provided by
the source or have to be generated from automatic speech recognition. (4) The
whole process management, delivery and acknowledgement control is done by
the underlying message system.
4.1</p>
      <p>
        Technologies used and links
The current version of the LinkedTV Platform has been implemented on base
of RabbitMQ [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ] which employs the AMPQ protocol [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]. Client micro services
are implemented in either Java or Python, but a lot of others are supported
by RabbitMQ as well, such as JavaScript or Scala. For other technologies like
Node.js there exist speci c AMPQ libraries. For the storage of RDF graphs,
Openlink Virtuoso is used. A web based interface for uploading videos and
starting the LinkedTV process is available under http://api.linkedtv.eu. A REST
inter-face for accessing the media generated media fragment annotations exists
under http://data.linkedtv.eu (realized with Elda [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ], an open source
implementation of the Linked Data API [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ] by Epimorphics) and also a SPARQL
3 in our case LinkedTV partners, a full list of LinkedTV platform compatible tools and
services and the respective partner has been published at http://www.linkedtv.eu/
demos-materials/tools-and-services/.
endpoint under http://data.linkedtv.eu/sparql. Fig. 4 shows a screenshot
of the LinkedTV dash-board displaying metadata and to a media resource
processed by the LinkedTV system.
      </p>
    </sec>
    <sec id="sec-6">
      <title>Summary, discussion and outlook</title>
      <p>The core functionalities required for the purposes of Linked Media Management
as followed within LinkedTV and described in Section 2 project have already
been realized within the rst version of the LinkedTV Platform. The current
version of the LinkedTV Platform did not add any new functionality, but
focused on a redesign and refactoring process in order to prepare the LinkedTV
Platform for industrial use. We did this by applying principles of reactive
design. In comparison with the above mentioned related approaches, the LinkedTV
Platform architecture is in fact quite similar to the approach taken by the MICO
Platform: Both ones are based on a message driven backend with even RabbitMQ
as the same technology; within LinkedTV we also consider using Apache Camel
for Service Orchestration. Both employ Linked Data Repositories (LinkedTV:
Virtuoso/Elda, MICO: Apache Marmotta).</p>
      <p>The main di erence between these two architecture lies in the integration
of the connected Linked Media Services: while LinkedTV is a very distributed
architecture connecting the di erent services over the Web via REST services,
MICO seems to use mainly native components. While the LinkedTV approach
seems to be more open and more directed to creating a web-scale envisioned
Linked Media Layer, the MICO approach will quite surely be more e cient.</p>
      <p>As next steps we will be addressing the evaluation of the new platform
architecture by testing di erent con gurations and pro les. From anecdotal
experience we can say that within the rst platform version the processing ratio was
about 1.5, i.e. the whole automated processing of a 20-min German news show
took about 30 min, whereas within the new platform architecture this ratio went
down to about 0.75. By far the most time takes the visual analysis, but this can
be done now almost completely in parallel to the other steps.</p>
      <p>Acknowledgments. This work has been partially supported by the European
Commission via the FP7 project LinkedTV (GA 287911).4 We wish to thank
particularly Lampis Apostolidis (CERTH), Jose Luis Redondo Garcia
(EURECOM), Daniel Oeckeloen and Pieter van Leeuwen (Noterik), Jaap Blom (Sound
and Vision) for greatly supporting the further development of the LinkedTV
Platform after the end of the project LinkedTV and LinkedTVs former
scienti c coordinator Lyndon Nixon for his input on this paper as well as all of the
developers and advocates for the di erent Web services which are used by the
Platform.
4 The full list of LinkedTV partners can be found at http://www.linkedtv.eu/
about-the-project/consortium/.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>Evaggelos</given-names>
            <surname>Spyrou</surname>
          </string-name>
          et al.,
          <source>Semantic Multimedia Analysis and Processing</source>
          , CRC Press,
          <year>June 2014</year>
          . ISBN 978-1-
          <fpage>4665</fpage>
          -7549-3.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>Lyndon</given-names>
            <surname>Nixon</surname>
          </string-name>
          and
          <article-title>Raphael Troncy, Survey of Semantic Multimedia Annotation Tools for the Web</article-title>
          ,
          <source>in ESWC Satellite Events</source>
          <year>2014</year>
          , LNCS 8798, pp.
          <fpage>100</fpage>
          -
          <lpage>114</lpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Lyndon</surname>
            <given-names>Nixon</given-names>
          </string-name>
          ,
          <article-title>The importance of Linked Media to the Future Web</article-title>
          ,
          <source>in WWW 2013 Companion</source>
          , pp.
          <fpage>455</fpage>
          -
          <lpage>456</lpage>
          ,
          <year>2013</year>
          . http://www2013.wwwconference.org/companion/ p455.pdf
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>Jan</given-names>
            <surname>Thomsen</surname>
          </string-name>
          ,
          <string-name>
            <surname>Final LinkedTV</surname>
          </string-name>
          End-to-end Platform,
          <source>LinkedTV project deliverable D5</source>
          .6,
          <year>October 2014</year>
          . http://www.linkedtv.eu/deliverables
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Lyndon J. B. Nixon</surname>
          </string-name>
          ,
          <article-title>Delivering related web content synchronized to online television: The LinkedTV solution</article-title>
          ,
          <source>Proc. 2015 IEEE 5th International Conference on Consumer Electronics (ICCE</source>
          <year>2015</year>
          ),
          <article-title>September 2015</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>6. TVAnytime, http://www.tv-anytime.org/</mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>MPEG7</given-names>
            <surname>Audiovisual Description</surname>
          </string-name>
          <article-title>Pro le</article-title>
          , http://mpeg.chiariglione.org/ standards/mpeg-7/profiles
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <source>Media Fragments URI 1</source>
          .0, https://www.w3.org/TR/media-frags/
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>9. W3C Web Annotation Working Group, https://www.w3.org/annotation/</mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>PROV-Overview</surname>
          </string-name>
          , https://www.w3.org/TR/prov-overview/
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>11. Linked Media Framework, http://semanticweb.org/wiki/Linked_Media_ Framework.html</mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>12. Apache Marmotta, http://marmotta.apache.org/</mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>13. MICO Platform, http://www.mico-project.eu/platform/</mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Patrick</surname>
          </string-name>
          Aichroth et al.,
          <source>MICO Technical Report</source>
          Vol. 3
          <string-name>
            <given-names>Enabling</given-names>
            <surname>Technology Modules: Version</surname>
          </string-name>
          <string-name>
            <surname>I</surname>
          </string-name>
          , Salzburg Research Forschungsgesellschaft mbH, Salzburg, Austria,
          <year>2016</year>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Evlampios</surname>
          </string-name>
          Apostolidis et al.,
          <article-title>Visual, text and audio information analysis for hypervideo, nal release</article-title>
          ,
          <source>LinkedTV project deliverable 1</source>
          .4,
          <year>September 2014</year>
          . http://www. linkedtv.eu/deliverables
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>16. LinkedTV Ontology, http://www.linkedtv.eu/ontology</mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>J.L. Redondo</surname>
          </string-name>
          Garcia et al.,
          <article-title>Annotation and retrieval module of media fragments</article-title>
          ,
          <source>LinkedTV project deliverable 2</source>
          .4,
          <year>October 2013</year>
          . http://www.linkedtv.eu/ deliverables
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Tomas</surname>
          </string-name>
          Kliegr et al.,
          <article-title>LinkedTV Framework for generating video enrichments with annotations</article-title>
          ,
          <source>LinkedTV project deliverable 2</source>
          .6,
          <year>October 2014</year>
          . http://www. linkedtv.eu/deliverables
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>19. LinkedTV EditorTool, http://editortoolv2.linkedtv.eu/</mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Dorothea</surname>
          </string-name>
          Tsatsou et al.,
          <string-name>
            <surname>When</surname>
            <given-names>TV</given-names>
          </string-name>
          <article-title>meets the Web: towards personalised digital media, book chapter in [1].</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>21. The Reactive Manifesto, http://reactivemanifesto.org</mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>22. RabbitMQ, http://www.rabbitmq.com/</mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>23. AMPQ, https://www.amqp.org/</mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Elda</surname>
          </string-name>
          , https://github.com/epimorphics/elda
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Linked Data</surname>
            <given-names>API</given-names>
          </string-name>
          , https://code.google.com/archive/p/linked-data-api/ wikis/Specification.wiki
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>