<!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>Short Paper: Annotating Microblog Posts with Sensor Data for Emergency Reporting Applications</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>David N. Crowley</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alexandre Passant</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>John G. Breslin</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Digital Enterprise Research Institute National University of Ireland</institution>
          ,
          <addr-line>Galway</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>School of Engineering and Informatics National University of Ireland</institution>
          ,
          <addr-line>Galway</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>The explosion in user-generated content (on the Social Web) published from mobile devices has seen microblog platforms like Twitter grow exponentially. Twitter is a microblogging platform founded in 2006, which by October 2010 had roughly 175m users and as of June 2011, Twitter processed 200m posts per day. Twitter data has been utilised to predict/report natural disasters, civil unrest, and media topics. Smartphones and other mobile devices contain an array of sensors but are under-utilised on the Social Web. In this paper, we propose a method for annotating microblog posts with multi-sensor data by representing it with ontologies such as SSN and SIOC. We present an alignment of these ontologies and outline an enhanced Twitter client that would allow users to enter an emergency mode where all or most of the available sensor data would be published as annotations to the users post, allowing relief organisations to use any data relevant.</p>
      </abstract>
      <kwd-group>
        <kwd>SSN</kwd>
        <kwd>Microblog</kwd>
        <kwd>SIOC</kwd>
        <kwd>Citizen</kwd>
        <kwd>Sensors</kwd>
        <kwd>Social Sensing</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>The unprecedented 96% growth in smartphone sales1 and in user numbers on
social platforms like Twitter (572,000 new accounts created on March 12, 2011)
demonstrate the growth in the use of the mobile web. As microblogging lends
itself to instantaneous updates, data related to events occurring around the world
is created before it can be reported on by more traditional media methods or
even by blog or blog-like services. In parallel with this growth in mobile-based
microblogging, mobile devices themselves have begun to incorporate increasing
amounts of sensors for various purposes, ranging from detecting light levels when
a phone is placed close to one's head to accelerometers that can detect orientation
changes and movement in various directions.
1 http://www.gartner.com/it/page.jsp?id=1466313</p>
      <p>In this short paper, we look at using microblogging platforms as citizen
sensing/reporting platforms by adding mobile sensor data to user posts and
describing that data using the SSN (Semantic Sensor Network)2 ontology and the
SIOC (Semantically-Interlinked Online Communities)3 ontology. In particular,
we outline applications for emergency scenarios, where people can report on
events using microblogging while automatically attaching all available sensor
data from their mobile devices (in order to provide context to emergency
reports). The structure of this paper is as follows. Section 2 will describe related
work in this area along with a brief review of mobile sensors. We will describe
the Twitter Annotations initiative in Section 3, and how it can be used for
sensor data annotations. Section 4 will detail the alignments required between
the social and sensor data ontologies SIOC and SSN. Section 5 will outline our
proposed 'emergency mode' microblogging client that allows users to upload all
available sensor data with a post to aid relief workers/government agencies. We
will present conclusions in Section 6.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        Sheth uses the example of Twitter posts during the Mumbai terrorist attacks in
November 2008 when Twitter updates and Flickr feeds by citizens using mobile
devices reported observations of these events in real time[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].4 Twitter data has
been used in event/disaster reporting and prediction[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Tapia et al. examined the
usage of Twitter to aid relief workers with information regarding disasters, and
they saw one method of using \microblogged data as ambient or contextual data
to enrich the information provided to the NGO at the time of disaster"[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Mobile
devices contain many sensor formats that provide information such as location
(through GPS or cell tower locations) to create/add context to microblog posts
and status updates. Companies like Foursquare use this contextual data to create
various geo-social gaming/marketing applications.
      </p>
      <p>
        In relation to microblog posts, at present GPS adds location to the data of
the post made, but in the eld of multi-sensor context awareness, researchers
are currently examining ways to augment devices with an awareness of their
situation and environment to add contextual understanding through the use of
combined sensor data. As Gellersen et al. asserts \Position is a static environment
and does not capture dynamic aspects of a situation"[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], and this concept can
be applied to most single sensor data, but with multi-sensor context awareness
the diverse sensor readings are combined and then with processing situational
awareness can be derived. Situation awareness is the observation of
surrounding elements/events in relation to the user, this perception of the immediate
environment lets humans derive meaning and aids in decision making.5
      </p>
      <sec id="sec-2-1">
        <title>2 http://www.w3.org/2005/Incubator/ssn/XGR-ssn/</title>
      </sec>
      <sec id="sec-2-2">
        <title>3 http://sioc-project.org/</title>
      </sec>
      <sec id="sec-2-3">
        <title>4 http://www.telegraph.co.uk/news/worldnews/asia/india/3530640/</title>
        <p>Mumbai-attacks-Twitter-and-Flickr-used-to-break-news-Bombay-India.html</p>
      </sec>
      <sec id="sec-2-4">
        <title>5 http://en.wikipedia.org/wiki/Situation_awareness</title>
        <p>Twitter Annotations is an initiative from Twitter that allows additional
structured metadata to be attached to tweets, going beyond the geotemporal
annotations normally found in social media content. While the annotation or metadata
is structured, it is open to the user or developer to decide what additional
information is attached to the microblog post. There is an overall limit of 512 bytes
for the metadata payload, but this may be expanded as usage increases.</p>
        <p>As an example in JSON, data about a movie described in a tweet could be
attached to the tweet using the annotation f\movie":f\title":\The Guard"gg,
indicating that the title of the movie is \The Guard". The guidelines for
Twitter Annotations state that the goal is to \bring more structured data to tweets
to allow for better discovery of data and richer interactions."6 In the sphere
of citizen sensing, Twitter annotations can be seen as a way to standardise an
emerging eld of supplementing microblog posts with sensor data and, as with
any area, standardisation is important. Figure 1 illustrates two examples of
annotations in the Twitter Annotations JSON format. The rst example describes
a digital compass sensor in an Android mobile device that returns direction in
degrees, and the second describes data returned from a three-axis accelerometer.</p>
      </sec>
      <sec id="sec-2-5">
        <title>6 http://dev.twitter.com/pages/annotations_overview</title>
        <p>In this work, the Twitter Annotations format will be used for adding sensor/
multi-sensor data to tweets using the Twitter Annotations API, and will inspire
how we attach sensor data (represented using the SSN ontology) to tweets, blog
posts and other microblog posts described via SIOC.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Aligning the SIOC and SSN ontologies</title>
      <p>
        SIOC allows the semantic interlinking of content items from forums, blogs and
other social websites, and aims to enable the integration of online community
information[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. SIOC provides a Semantic Web ontology for representing rich
data from the Social Web using the Resource Description Framework (RDF).
By describing the social data contained within online communities (powered by
blogs, wikis, and forums) using semantic technologies, SIOC enables this data
to become a \Social Web of Data"[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
      <p>Microblog
has_container
has_sensor_data</p>
      <p>SNN</p>
      <p>ObservationValue
hasValue some
MicroblogPost</p>
      <p>SensorOutput
isProducedBy some</p>
      <p>Sensor</p>
      <p>SIOC was originally written to describe web-based discussion on blogs and
message boards, but with the SIOC Types module this has been expanded to
include items like Microblog and MicroblogPost. SIOC has received signi cant
adoption in commercial and open-source software applications7: it has been
adopted in the core of Drupal 7 and around 100 applications use SIOC.</p>
      <p>Figure 2 outlines our method for annotating microblog posts with
sensor/multi-sensor data by representing it with ontologies such as SSN
and SIOC. The property has sensor data will join sioct:MicroblogPost to
ssn:ObervationValue. We proprose to create a SIOC Sensors (siocs) module to
include this and future related properties. The sioct:MicroblogPost itself can have
one or more ObservationValue(s). Figure 3 is an example of a microblog post
with orientation sensor data attached. We de ne an AndroidOrientation sensor
that has a de ned SensorOutput that has value OriObservationValue a subclass
of ObservationValue and has three properties hasXQuantityValue,
hasYQuantityValue, and hasZQuantityValue, de ned in a Citizen Sensors ontology (cs).
We will now describe a scenario whereby data from multiple sensors can be
attached to microblog posts using the aforementioned alignments to aid in
emergency scenarios. We are currently developing a semantic microblogging client
for the Android platform that implements both Twitter Annotations and
SSNannotated SIOC posts for emergency reporting with sensor data.</p>
      <p>In an emergency, the user could employ the semantic microblogging client
and activate the emergency mode that would allow the application to annotate
any available sensor data to their post (including photos). The available sensor
readings could help emergency workers by attaching the direction the user is
facing, noise levels in the surrounding area, light levels, direction of movement,
and any other available data to the post. If GPS is unavailable, then from these
sensors and the information extracted from the microblog post (place names or
points of interest) an estimated location along a directional line could be
calculated. In situations where a snapshot of data is not relevant, attaching aggregated</p>
      <sec id="sec-3-1">
        <title>7 http://sioc-project.org/applications</title>
        <p>values/lists of values describing changes in activity, compass direction, and noise
levels over time might better communicate the user's situation. Furthermore, the
microblog post contents and the annotated sensor readings could aid emergency
teams with reports including direction and lighting conditions.
6</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Conclusion</title>
      <p>By combining the Social Web and sensors, applications can provide an extension
of social activities through sensors, as user activity is modelled by both voluntary
user input and sensor data annotated to the posts. In this paper, we describe how
this will be implemented using web standards like the SIOC onotology and by
aligning SIOC with the SSN ontology to both describe users' posts semantically
and attach contextual sensor data to the post through metadata annotations.
We have described a scenario that uses this combined SIOC-SSN representation,
based on a semantic microblogging client currently being developed for mobile
devices that will enable emergency reporting functionality.
7</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgements</title>
      <p>This work has been supported in part by Science Foundation Ireland under grant
number SFI/08/CE/I1380 (L on 2). We would like to thank Fabrizio Orlandi and
Myriam Leggieri for their input.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Sheth</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          : Citizen Sensing,
          <source>Social Signals, and Enriching Human Experience. Internet Computing, IEEE</source>
          <volume>13</volume>
          (
          <issue>4</issue>
          ),
          <volume>87</volume>
          {
          <fpage>92</fpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Sakaki</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Okazaki</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Matsuo</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Earthquake Shakes Twitter Users: Real-Time Event Detection by Social Sensors</article-title>
          ,
          <source>Proceedings of the 19th International Conference on World Wide Web</source>
          , pp.
          <volume>851</volume>
          {
          <fpage>860</fpage>
          .
          <string-name>
            <surname>Raleigh</surname>
          </string-name>
          , North Carolina, USA (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Tapia</surname>
            ,
            <given-names>A.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bajpai</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jansen</surname>
            ,
            <given-names>B.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yen</surname>
          </string-name>
          , J.:
          <article-title>Seeking the Trustworthy Tweet: Can Microblogged Data Fit the Information Needs of Disaster Response and Humanitarian Relief Organizations</article-title>
          ,
          <source>Proceedings of the 8th International ISCRAM Conference</source>
          ,. pp.
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
          , Lisbon, Portugal (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Gellersen</surname>
            ,
            <given-names>H.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schmidt</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Beigl</surname>
          </string-name>
          , M.:
          <string-name>
            <surname>Multi-Sensor</surname>
            Context-Awareness in Mobile Devices and
            <given-names>Smart</given-names>
          </string-name>
          <string-name>
            <surname>Artefacts</surname>
          </string-name>
          .
          <source>Mobile Networks and Applications</source>
          <volume>7</volume>
          (
          <issue>5</issue>
          ),
          <volume>341</volume>
          {
          <fpage>351</fpage>
          (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Lane</surname>
            ,
            <given-names>N.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Miluzzo</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hong</surname>
            <given-names>Lu</given-names>
          </string-name>
          , Peebles,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Choudhury</surname>
          </string-name>
          , T.,
          <string-name>
            <surname>Campbell</surname>
          </string-name>
          , A.T.:
          <article-title>A Survey of Mobile Phone Sensing</article-title>
          .
          <source>Mobile Networks and Applications</source>
          <volume>48</volume>
          (
          <issue>9</issue>
          ),
          <volume>140</volume>
          {
          <fpage>150</fpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Berrueta</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brickley</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Decker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fernandez</surname>
            <given-names>S.</given-names>
          </string-name>
          , Gorn,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Harth</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Heath</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Idehen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Kjernsmo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Miles</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Passant</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Polleres</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Polo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ,
            <surname>Sintek</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.:</surname>
          </string-name>
          <article-title>SIOC Core Ontology Speci cation</article-title>
          .
          <source>W3C Member Submission 12 June</source>
          <year>2007</year>
          , http://www.w3.org/Submission/sioc-spec/
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Bojars</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Passant</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cyganiak</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Breslin</surname>
            ,
            <given-names>J.G.</given-names>
          </string-name>
          :
          <article-title>Weaving SIOC into the Web of Linked Data</article-title>
          ,
          <source>Proceedings of the WWW 2008 Workshop on Linked Data on the Web (LDOW2008)</source>
          , Beijing, China (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>