<!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>Developing Mobile Linked Data Applications</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Oshani Seneviratne</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Evan W. Patton</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Daniela Miao</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Fuming Shih</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Weihua Li</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lalana Kagal</string-name>
          <email>lkagalg@csail.mit.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Carlos Castillo</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Massachusetts Institute of Technology</institution>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Qatar Computing Research Institute</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Rensselaer Polytechnic Institute</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>With the rapid advancement of mobile technologies, users are generating and consuming a signi cant amount of data on their handheld devices. However, the lack of Linked Data tools for these devices has left much of the data unstructured and di cult to reuse and integrate with other datasets. We will demonstrate an application development framework that enables the easy development of mobile apps that generate and consume Linked Data. We also provide a set of easy-to-deploy Web Services to supplement functionality for mobile apps focused on crowdsourcing. We motivate our work by describing a real-world application of this framework, which is a disaster relief application that streams crowd-sourced reports in real time.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Many developers are shifting their attention to the mobile world as smartphones
are becoming the information hub for people's daily lives [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The pervasiveness of
smartphones has led to the ubiquitous consumption and generation of data on them.
Smartphones can derive contextual information from their environment, enabling
applications that provide great value both to individual users and to society. For
example, context-aware applications can recommend products, services, or connections
to others based on people's surroundings. People can also use social applications to
report their status and the situation around them in cases of emergencies, such as
oods or earthquakes.
      </p>
      <p>
        Most mobile applications create or consume data stored in standalone databases
without the potential of being \interlinked" with data from other applications or
organizations. The Web community has advocated the use of Linked Data
technologies to address this data interoperability issue in Web-based applications. Although
we have seen some success from content publishers in using or publishing Linked
Data, few examples exist for mobile platforms [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>Our goal is to bring support for Linked Data to mobile platforms by allowing
developers to build mobile applications that consume and publish Linked Data
automatically. We will demonstrate a framework that allows developers to accomplish
this on Android devices through modular components, as well as cloud scripts aimed
at enabling quick deployment of companion web services to interact with streams
of Linked Data. We believe that this framework will reduce the burdens of mobile
developers to work with Linked Data and open up many opportunities for building
applications that interact with and contribute to the Linked Data world.
Our framework1 extends MIT App Inventor,2 an open source, web-based
environment for developing Android applications. Though primarily designed for
pedagogical use, App Inventor has found great success in many domains and boasts about
87,000 users weekly, 1.9 million total users, and over 4.9 million applications ranging
from tracking rainfall in Haiti3 to teaching U.S. Marines how to destroy weapons.4
App Inventor is structured around components: discrete blocks that provide
functionality and user interface elements that developers connect together to create an
application. App Inventor provides a designer view for laying out an application's
user interface and a blocks view where users de ne their program logic by connecting
method blocks, associated with components, together (as shown in Fig. 1).</p>
      <p>We will demonstrate several components that we've developed powered by Apache
Jena5, including forms to generate Linked Data, maps for visualizing geographic
data, web services for cloud messaging, web services for exploring Linked Data,
and sensor components for context awareness. We will also demonstrate companion
web services that provide cloud functionality for mobile phones such as providing
messaging services to integrate streaming RDF content.
3</p>
    </sec>
    <sec id="sec-2">
      <title>Use Case: WeReport</title>
      <p>
        WeReport allows people to report (e.g. through a photo) the situation on the ground
during an emergency, hence enhancing situational awareness with respect to the
emergency [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The application demonstrates the capacity to generate and consume
Linked Data, as well as integrate with di erent public datasets.
      </p>
      <p>Consider a scenario where a hurricane has hit a city, and Joe, a volunteer citizen
reporter, notices a series of potential hazards in his neighborhood, e.g. fallen trees
blocking an intersection. With WeReport, Joe can take a picture of the hazard and
upload it, along with a tag and description, to warn others in the area. An example
of this report can be seen in Figure 2a.
1 http://punya.appinventor.mit.edu
2 http://appinventor.mit.edu/
3 http://www.webcitation.org/6PUXWVG0U
4 http://www.webcitation.org/6PUXZb7FM
5 https://jena.apache.org</p>
      <p>(a) Submitting Reports (b) Browsing Reports
Fig. 2: WeReport application for Mobile Devices: an application that allows users to
submit disaster reports to the cloud. Users can subscribe to reports close to a certain
location on a topic such as `Fallen Trees', and results are streamed in real-time to
subscribers via push noti cations.</p>
      <p>When creating a report, WeReport consumes Linked Data via pre-de ned SPARQL
queries that search for popular landmarks near Joe's location, so that those places
can be tagged if hazardous. At the same time, the mobile application enables him to
transparently produce structured data through our Linked Data-enhanced
components. The generated data can be published to SPARQL 1.1 compliant endpoints,
which enables data re-use by others.</p>
      <p>WeReport also supports real-time streaming of user-submitted disaster reports.
In this scenario, Bob and Anna are both relief workers heading towards the a ected
area. Using WeReport, they have subscribed to the hurricane disaster feed and they
continuously receive push noti cations as reports on the disaster area are submitted
by users like Joe. While Bob wishes to be continuously noti ed on every newly
submitted report, Anna chooses to receive an alert only when there are at least
3 reports of a certain type in a given location, a custom limit she had previously
speci ed. Whenever Bob and Anna want to view the newest reports, WeReport
provides a \Browse Reports" interface which automatically displays the received
reports, as show in Figure 2b.
4</p>
    </sec>
    <sec id="sec-3">
      <title>Related Work</title>
      <p>
        There has been some work in Linked Data use for smartphones, however, they do not
provide a comprehensive solution to mobile app development as our framework does.
[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] propose a lightweight general-purpose RDF framework for Android to share
application data inside the phone. Our framework focuses on obtaining external RDF
sources and consuming them and not necessarily application data integration using
RDF. Spinel [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] is a plug-in architecture and a set of web con guration tools for
Android that enable new datasets to be added to mobile phones without
programming. We provide both a plug-in architecture and support for adding new datasets
using program blocks that can be con gured easily. Another notable platform for
creating mobile Linked Data applications is the \RDF on the go", an RDF storage
and query processor library for mobile devices [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Our framework not only allows
storage and querying of RDF data, but more importantly makes it much more user
friendly to manipulate the data, be it contextual data from the phone or data from
a remote endpoint.
      </p>
      <p>
        Unlike applications such as Cinemappy [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] and DBPedia Mobile [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], which
require developers to have extensive knowledge of both Linked Data and mobile
programming, our target audience is Linked Data developers who want to develop
mobile applications but do not have mobile programming experience.
5
      </p>
    </sec>
    <sec id="sec-4">
      <title>Summary</title>
      <p>Though mobile devices have become the primary computing and communication
platform for users, the number of Linked Data apps available for these devices is
insigni cant because developing them is currently extremely time consuming.</p>
      <p>In this demonstration, we show a mobile application platform that enables
mobile Linked Data applications to be quickly and easily developed. Along with leading
to applications that are able to leverage structured data, these mobile applications
will help get around the classic \chicken-or-egg" situation by being both
generators and consumers of Linked Data. The current implementation contains a few
limitations including scalability, which our team will be working on. We will also
be conducting further user studies to evaluate the usability and usefulness of the
platform.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Tillmann</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moskal</surname>
          </string-name>
          , M.,
          <string-name>
            <surname>de Halleux</surname>
          </string-name>
          , J.,
          <string-name>
            <surname>Fahndrich</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bishop</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Samuel</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Xie</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>The future of teaching programming is on mobile devices</article-title>
          .
          <source>In: Proceedings of the 17th ACM annual conference on Innovation and technology in computer science education</source>
          ,
          <source>ACM</source>
          (
          <year>2012</year>
          )
          <volume>156</volume>
          {
          <fpage>161</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Ermilov</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Khalili</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Auer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Ubiquitous Semantic Applications: A Systematic Literature Review</article-title>
          .
          <source>International Journal on Semantic Web and Information Systems</source>
          <volume>10</volume>
          (
          <issue>1</issue>
          ) (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Vieweg</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Situational Awareness in Mass Emergency: A Behavioral and Linguistic Analysis of Microblogged Communications</article-title>
          .
          <source>PhD thesis</source>
          , University of Colorado at Boulder (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>David</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Euzenat</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosoiu</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , et al.:
          <article-title>Linked data from your pocket</article-title>
          .
          <source>In: Proc. 1st ESWC workshop on downscaling the semantic web.</source>
          (
          <year>2012</year>
          )
          <volume>6</volume>
          {
          <fpage>13</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <issue>5</issue>
          .
          <string-name>
            <surname>Chang</surname>
            ,
            <given-names>K.S.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Myers</surname>
            ,
            <given-names>B.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cahill</surname>
            ,
            <given-names>G.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Simanta</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Morris</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lewis</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>A plug-in architecture for connecting to new data sources on mobile devices</article-title>
          .
          <source>In: Visual Languages and Human-Centric Computing (VL/HCC)</source>
          ,
          <source>2013 IEEE Symposium on, IEEE</source>
          (
          <year>2013</year>
          )
          <volume>51</volume>
          {
          <fpage>58</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>Le</given-names>
            <surname>Phuoc</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Parreira</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.X.</given-names>
            ,
            <surname>Reynolds</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            ,
            <surname>Hauswirth</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.:</surname>
          </string-name>
          <article-title>RDF On the Go: RDF Storage and Query Processor for Mobile Devices</article-title>
          .
          <source>In: ISWC Posters&amp;Demos</source>
          . (
          <year>2010</year>
          )
          <fpage>12</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Ostuni</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gentile</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Noia</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mirizzi</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Romito</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sciascio</surname>
          </string-name>
          , E.:
          <article-title>Mobile movie recommendations with linked data</article-title>
          . In Cuzzocrea,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Kittl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Simos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Weippl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ,
            <surname>Xu</surname>
          </string-name>
          , L., eds.: Availability,
          <string-name>
            <surname>Reliability,</surname>
          </string-name>
          <source>and Security in Information Systems and HCI. Volume 8127 of Lecture Notes in Computer Science</source>
          . Springer Berlin Heidelberg (
          <year>2013</year>
          )
          <volume>400</volume>
          {
          <fpage>415</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Passant</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Measuring Semantic Distance on Linking Data and Using it for Resources Recommendations</article-title>
          .
          <source>In: AAAI Spring Symposium: Linked Data Meets Arti cial Intelligence</source>
          .
          <article-title>(</article-title>
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>