<!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>Semantic Wiki for Visualization of Social Media Analysis</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Daniel Reininger</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>David Ihrie</string-name>
          <email>dihrie@semandex.net</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Bob Bullard</string-name>
          <email>bob@semandex.net</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Semandex Networks Inc.</institution>
          ,
          <addr-line>5 Independence Way, Suite 309, Princeton, NJ 08540 (609) 681-5382</addr-line>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2010</year>
      </pub-date>
      <abstract>
        <p>A semantic wiki provides visualization of social media analysis applicable to military Information Operations and law enforcement counterterrorism efforts. Using inputs from disparate data sets, semantic software exports data to link analysis, geospatial displays, and temporal representation. Challenges encountered in software development include the balance between automated and human assisted entity extraction, interoperability with existing visualization systems and ontology management.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        Social media analysis is an important part of military and law enforcement operations
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The analysis requires the ability to model and extract significance from the
social media interactions of persons and organizations of interest. This analysis must
be done in real time and in the virtual, collaborative workspaces of the law
enforcement and intelligence communities.
      </p>
      <p>This paper outlines issues identified during the development and demonstration of
a software tool to provide shared visualization for social media analysis in selected
government environments. We developed and tested a software application pursuant
to a federally sponsored program titled Information Networking for Operational
Reporting and Monitoring (INFORM). The project was designed to facilitate
collaborative analysis and workflows for elements of the U.S. Marine Corps, the U.S.
Special Operations Command, and the U.S. Department of State.</p>
      <p>
        Existing information sharing applications available to the user community included
the Combined Information Network Data Exchange (CIDNE) [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], Intellipedia [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], and
the Net-Centric Diplomacy portal [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Each of these programs provided an avenue for
information sharing and multi-agency collaboration, primarily by making
documents—whether finished reports or community-updated web pages—available to
a broad community. However, each of these systems exhibited a common
disadvantage that the INFORM program was designed to help mitigate: tactical users
needed to model information of local interest that could not be easily captured in
CIDNE, NCD, or Intellipedia in a way that facilitated efficient and dynamic query,
retrieval and display. A solution had to provide three advantages over the existing
systems. First, the solution had to provide the user with a means to rapidly tailor the
information model to handle novel concepts encountered at the lowest tactical
echelons. Second, the solution had to allow for the dynamic assembly of documents
so that views of information were automatically and continually updated throughout
the knowledge base; new social links had to be instantly recognized and published as
soon as these links were discovered by the system. Third, the solution had to provide
a means of efficient manual and automated query and display, including the ability to
export data extracts to specific visualization applications (external to this software
solution) designated by the user community.
      </p>
      <p>The goal of the INFORM program was to create a web-based application with
these capabilities that supported Information Operations. The technical approach was
to develop a semantic wiki for data capture, analysis, and display. The desired end
state was the ability to link entities contained in reports, open source articles and other
sources encountered by users, creating a semantic graph that helped with social media
analysis rather than simply serve as a document management system. A semantic
approach met the end state requirements and offered additional advantages. First, data
could be combined from disparate sources. Some data were highly structured and
amenable to computer processing, while other data were unstructured, with syntactic
incompatibilities that inhibited automated data ingestion to the system. We used a
semantic schema and domain-specific ontology to parse information, generate
concept instances, and represent relationships identified in the data. Second, a
webbased wiki provided distributed access and rapid dissemination of information for
multi-user collaboration. It provided a platform that generated and transmitted alerts
based on changes in collective knowledge, such as the discovery of additional
relevant information. Individual users set their own alert parameters and received
individual notifications, by email or web-based chat, that included embedded links for
one-click viewing of updated information.</p>
    </sec>
    <sec id="sec-2">
      <title>2 Discussion</title>
      <p>
        The use case in which the software was applied involved social media analysis
supporting psychological operations. Specifically, we used the new semantic
application to perform analysis of a selected target audience in accordance with
existing doctrinal procedures [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. This involved the review of data from open source
media, combined with data from additional sources, to support an assessment of
social groups, subgroups, and individuals within a population.
      </p>
      <p>Visualization of the results of social media analysis is essential to effective target
characterization for influence operations. The analysis in this project supported the
initial study of a subject audience and evaluated measures of effectiveness to
determine behavioral change, as evidenced in differences in social media behavior.
Variations were observed both in social media content generation and activity
patterns. The approach taken to determine changes in social media behavior was
driven by the data available, which was a function of available sensors and
information access.</p>
      <sec id="sec-2-1">
        <title>2.1 Input Interfaces</title>
        <p>
          The semantic software developed supported interfaces with databases, emails, RSS
feeds, web pages, and spreadsheet files customized to support existing concepts of
operation. An issue we faced was achieving the optimal balance between automated
and human-assisted data ingestion. Uploading spreadsheets is a simple means of
automated input; however, extracting pertinent information and context from
unstructured text is also an important component of social media analysis, since
statistical display of themes extracted from social media (e.g., blogs) are an indicator
of social sentiment. Research comparing human-assisted entity extraction from text
with automated methods, in efforts to enable automated network node/edge
determination, indicate that the methods are complementary [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. A mix of human
involvement and automated processes provides the ideal balance of speed, ease, and
validity. We used automated entity recognition in text coupled with human-validated
associations to input data into a semantic graph. Additionally, for statistics not
requiring additional human validation (such as summations of statistical analysis of
sentiment), we incorporated automated data ingestion and automated visualization.
        </p>
        <p>A customized data loader feature was developed for the software to facilitate
automated upload of information. The primary challenge encountered during
automated input from source databases was gaining an understanding of the structure
of source data without a descriptive model of that data. This understanding was
integral to writing the appropriate SQL statements to retrieve data in the desired
format. This obstacle was overcome by manual inspection of columns in the source
database, looking for promising column names, and examining the contents to verify
that the mapping was appropriate. This mapping and tailored ingestion [detailed in
reference 8] was critical to harmonize geospatial and temporal data from disparate
datasets. This process would have been greatly aided by a mechanism to find similar
names, similar content, and matching enumerations in order to help understand how
the source data mapped to the target, as well as a mechanism to build and test the
necessary SQL statements that ultimately retrieved data from the source. Once
complete, the data loader mapped data into the semantic database while ensuring that
incoming data met certain standards. The data loader template built and loaded
concept instances and properties, and then built relationships between the concepts to
form the semantic graph.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2 Output Interfaces</title>
        <p>Visualization was delivered in three distinct categories: link analysis, geospatial
representation and temporal representation. Rather than duplicate efforts to develop
capabilities that would require user training, we focused on utilities for export of
relevant data to existing third party applications already commonly employed by the
user community.</p>
        <p>Figure 1 shows the system’s architecture and input/output interfaces. Input
interfaces included databases, emails, RSS feeds, web pages, spreadsheet files.
External applications included, but were not limited to, link analysis, and geospatial
visualization of select data. Figure 2 shows the output displays of results into Link
Analysis tools and geospatial visualization. Results summarized in the person’s page
can be visualized as a link chart and in geospatial representations.</p>
        <p>
          Figure 3 shows a geographic display, using Google Maps, of population sentiment
derived using statistical aggregation of data related to individuals, exported as KML.
Geographic clustering and display of sentiment statistics derived from social surveys
is an accepted methodology within the military for obtaining “ground truth” [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ].
        </p>
        <p>
          Temporal views complemented geographic displays. Software views based on
adjusting time frames can indicate periods of high and low centrality, productivity,
and information dissemination; however, contextual cues that compliment temporal
views are critical to gaining a true understanding of social interactions [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]. We
developed a tailored display to fit the unique requirements of temporal visualization
for social communications between individuals, which we could not obtain using
existing external applications.
        </p>
        <p>Tailored representations included a heat map that showed activity by time and day
of week to identify changes in individual social communications behavior. Filters
provided adjustable date ranges and the ability to select the type or types of
interaction (phone call, text message, etc.) displayed by the software.</p>
        <p>Such visualization of the results of social media monitoring and analysis offers
direct application to addressing the challenges and opportunities that result from the
widespread use of social media, and its necessary inclusion in an environment of
Information Operations. The utility of these visualizations applies equally to law
enforcement, particularly in a counter-terrorism role.</p>
        <p>During the course of this project, we encountered several salient issues that merit
further research to expand the capabilities for social media analysis and visualization.
We next present some possible approaches to ontology management, but leave the
recommendations as open-ended avenues for the development of the field.</p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3 Ontology Management</title>
        <p>This project developed a common schema for representation of information of interest
to multiple potential user communities, including psychological operations, civil
affairs, and intelligence information related to people, regions, countries, events,
threats, and similar topics. This common schema provided the foundation for
semantic information modeling that resulted in the ability of users to contribute to and
draw on a common information picture expressed in a semantic graph.</p>
        <p>
          There has been discussion of implementing a high-level, domain-independent
ontology to provide a framework from which disparate systems in the government
and military arenas could derive domain-specific ontologies [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. Lacking such a
foundational ontology of universal application, we developed a semantic schema and
a domain-specific ontology for this project. Our solution did not need to provide
formal inferencing; accordingly, our application did not require a formal ontology.
We did need enough structure to capture associations in the data to present, for
example, the optimal path to get a message to influential individuals within a
community of interest.
        </p>
        <p>
          Certainly, the integration of social media analysis software with existing enterprise
information systems requires either ontological commonality or ontological bridging
to enable effective interface across domains. Such a bridging ontology [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] might be
useful to more easily ingest additional data sets into the semantic graph, or export data
from the semantic graph to other databases without the need for customizing data
loader templates or data export functions.
        </p>
        <p>Even within a single domain and system, users required a method of tailoring the
ontology by extending it “on the fly” to accommodate new concepts. For example,
while examining media inputs, a user identified the need to add a “Tweet” as a
subtype of instant message. Fortunately, the user interface provided a means by which
the user could, without the need for software programming, spontaneously add
relevant concepts and integrate this data into the analysis picture without corrupting
the structure of the database or impacting functionality of the software. While the
ontology remained “informal” in that users could extend it, the software-enforced
adherence to that ontology “formalized” its acceptance by the user community.</p>
        <p>The requirement for an adaptable ontology poses conflicting challenges. First, a
user faced with a new classification of information must be able to define the new
entity in the ontology. Second, this process must be managed collaboratively. If every
user is continually modifying the structure of the ontology, it will rapidly cease to
function; data calls for visualization will fail. Instead, designated stewards of the
ontology in a user organization must make necessary modifications without recourse
to technical support. Developers must take the requirements for agile schema into
account in the planning and design phases of the software design life cycle to ensure
that users can keep the application relevant in the ever-evolving conditions of social
media analysis.</p>
        <p>Two lessons learned, and successfully applied, were that recognition engines and
recommendation engines can assist with ontology management. A recognition engine
was incorporated that functions on free text input from files or websites, and
preprocesses the text before presenting it to the user’s view. It highlights entities in
the text that are already known to the semantic wiki, such as the name of a specific
person or place. The engine then uses a semi-automated process to help the user
delineate relationships between existing entities and new entities created by the user.
This human-to-machine interface prevents the user from unnecessarily creating new
entities, and prevents the software from making errors of association that are a
common byproduct of fully automated text recognition and database ingestion.</p>
        <p>A recommendation engine provides assistance if the operator is still not satisfied
with existing subtypes (as in the above example of the “Tweet”). First, the user
interface allows the addition of a new subtype to the ontology. The software then
repopulates the modification to all user displays, allowing collaborative awareness
and use of the new subtype. Now a recommendation engine can provide the user with
awareness of alternatives, including newly created subtypes; when the software
processes incoming text, this recommendation engine presents the user with a list of
available entity types with which to tag new entities. “Tweet” is now recommended as
an option that the user can select. This utility optimizes visibility of the ontology and
limits the unnecessary duplication of subtypes.</p>
      </sec>
      <sec id="sec-2-4">
        <title>2.4 Results</title>
        <p>A source corpus of data composed of 204 files in four formats (.jpg, .html, .txt, .doc)
produced a semantic graph of 4310 concept instances in a semantic database totaling
102 MB. This represented the interrelations of 585 events and 196 persons.</p>
        <p>The domain-specific ontology expanded from eight basic concepts (Person,
Organization, Place, Event, File, Characteristic1 and Watchlist2) to 262 types of pages
defined by use case analysis and by direct user additions. For example,
“Communication Event” is a type of “Event” and “Tweet” is a type of
“Communication Event”. Also a “Facility” is a type of “Place” and a “Broadcasting
Station” is a type of “Facility”. However, actual data modeling for social media
analysis during the practical application phase of this program utilized only 63 types
of pages, or 24% of the total available. This suggests that users will, even when
presented with a myriad of choices in modeling data, often use commonly recognized
entity types. It also evidences the effectiveness of recognition and recommendation
engines in limiting the inclination of users to modify an adequately developed
ontology.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3 Conclusion</title>
      <p>This project has resulted in the development of software that provides social media
analysis and visualization for specific customers in the government community. We
have developed and tailored a commercially available semantic software solution to
integrate disparate social media data sources using automated and machine-assisted
techniques that promote data validity and collaborative accessibility. While the results
apply directly to military Information Operations and law enforcement
counterterrorism efforts, we believe that the issues faced are widely applicable to researchers,
software developers, and program managers in other domains related to the semantic
exploitation of social media.</p>
      <p>An issue of interest to the reader community is the delicate task of finding the
balance between automated and machine-assisted (human-validated) data ingestion.
This is a balance that all data analysis applications must attain to preserve data
1 Characteristics model distinctive features of any entity (e.g., person, thing, event, place). For
example, “tall”, “long hair” and “caucacian” can be person’s characteristics.
2 A Watchlist page has two links: (Has Member) Page and (Is Watchlist Of) User. When a
member page is updated, the user will be notified of the update.
validity, without sacrificing scalability. Input methods such as spreadsheet and
unstructured text ingestion promote speed and utility, while entity recognition and
user-supervised text exploitation validate input to a collective database.</p>
      <p>We have leveraged existing third party applications preferred by the user
community to visualize information, including relations between abstract concepts in
social media, using link analysis and geographic display. Additionally, selected user
requirements have been met by the development of tailored temporal displays.</p>
      <p>Ongoing challenges include ontology management, where the requirement is to
provide the user with a mechanism to continually refine a domain-based ontology.
While adaptable software, with recognition and recommendation engines, allows for a
user-extensible ontology, the broader issue of cross-domain mapping using a bridging
ontology offers opportunity for further study.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. U.S. Department of Defense (USDoD) Joint Publication 2-
          <issue>01</issue>
          .3:
          <string-name>
            <given-names>Joint</given-names>
            <surname>Intelligence</surname>
          </string-name>
          <article-title>Preparation of the Operational Environment, pg</article-title>
          . xii. Department of Defense, Washington, DC (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <source>International Association of Law Enforcement Intelligence Analysts (IALEIA)</source>
          .
          <year>2004</year>
          <article-title>Law enforcement analytic standards, published in association with the U.S</article-title>
          . Department of Justice (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>Intelligent</given-names>
            <surname>Software</surname>
          </string-name>
          <string-name>
            <surname>Solutions</surname>
          </string-name>
          , Inc.: CIDNE, http://www.issinc.com/solutions/cidne.html
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>4. Wikipedia: Intellipedia, http://en.wikipedia.org/wiki/Intellipedia</mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Pack</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Profiling and testing procedures for a net-centric data provider. SPAWAR System Center Charleston, North Charleston</article-title>
          ,
          <string-name>
            <surname>SC</surname>
          </string-name>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6. U.S.
          <article-title>Department of the Army (USDoA)</article-title>
          .
          <source>FM 3-05</source>
          .302:
          <article-title>Tactical psychological operations tactics, techniques, and procedures</article-title>
          , pp.
          <fpage>6</fpage>
          -
          <issue>4</issue>
          to 6-
          <fpage>11</fpage>
          . Headquarters, Department of the Army, Washington, DC (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Graham</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Carley</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cukor</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Intelligence database creation &amp; analysis: network-based text analysis versus human cognition</article-title>
          .
          <source>In: Proceedings of the 41st Hawaii International Conference on System Sciences</source>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>Semandex</given-names>
            <surname>Networks</surname>
          </string-name>
          ,
          <article-title>Inc: Rapid semantic integration of data using the Tango DataLoader framework</article-title>
          , http://www.semandex.net/servlet/DownloadServlet?id=
          <fpage>397</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9. U.S.
          <source>DoA 2005: FM 3-05.302</source>
          , pp.
          <fpage>B1</fpage>
          -
          <lpage>B12</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Gloor</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Laubacher</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dynes</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Temporal visualization and analysis of social networks</article-title>
          .
          <source>In: Proceedings of the North American Association for Computational, Social and Organizational Science Conference</source>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Semy</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pulvermacher</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Obrst</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Toward the use of an upper ontology for U.S. Government and U.S. military domains: an evaluation</article-title>
          .
          <source>MITRE Corporation</source>
          , Bedford, MA (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Gilson</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Silva</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grant</surname>
            ,
            <given-names>P.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>From web data to visualization via ontology mapping</article-title>
          .
          <source>Computer Graphics Forum</source>
          ,
          <volume>27</volume>
          , no.
          <issue>3</issue>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>