<!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>Using Font Attributes in Knowledge Maps and Information Retrieval</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Richard Brath</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ebad Banissi</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>London South Bank University</institution>
          ,
          <addr-line>London</addr-line>
          ,
          <country country="UK">U.K</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Font specific attributes, such as bold, italic and case can be used in knowledge mapping and information retrieval to encode additional data in texts, lists and labels to increase data density of visualizations; encode data quantitative data into search lists; and facilitate text skimming and refinement by visually promoting of words of interest.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Information visualization (infovis) transforms data into visual representations.
In knowledge mapping, visualizations are used to gain insight into the
structure of large scale information spaces. In knowledge maps, similar to geographic
maps, text should have an inherent role to help viewer comprehend information,
however, the use of font-specific attributes, such as bold, italic, caps, etc., in
infovis is uncommon for encoding additional information. In information retrieval,
search results may use a few font-attributes, e.g. bold, underline, serif/sans serif,
to differentiate classes of metadata.</p>
      <p>
        The goal of this paper is to illustrate that font-specific attributes can be used
to: 1) facilitate skimming texts such as abstracts or lead paragraphs; 2) encode
quantitative data using a novel technique of proportional encoding in search
results and facets; and 3) encode multiple data attributes in labels.
Knowledge maps frequently use text labels: Places &amp; Spaces (scimaps.org) is
a repository of information visualizations and maps typically organizing large
information spaces (i.e. knowledge maps). Of 144 maps, 80% use some form of
text in the central visualization. When text is used, 2/3 use traditional infovis
attributes of size and color (e.g. text size corresponding to size of a region or size
of a node). Text-specific attributes are used in 28% of the examples, however,
these are typically used only to differentiate between compositional elements
(e.g. labels, axes, tick labels, hyperlinks, city, region, body of water in a map).
In only a few instances (mostly maps, infographics and a few infovis) are a
broader mix of font attributes used, e.g. case, italics and spacing [
        <xref ref-type="bibr" rid="ref18 ref7">7, 18</xref>
        ].
      </p>
      <p>
        Information retrieval infovis has a similar usage. Of 45 examples in
Hearst’s infovis chapters [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], half use traditional visual attributes of size and/or
color. There are 13 examples using one type-specific attribute, either bold, caps,
or font family, and in most cases these are used to either highlight a search term
or differentiate between types of data, e.g. category title vs. category instance;
axis title vs. tick label.
      </p>
      <p>
        Other infovis also use font attributes, e.g. italics [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ], uppercase [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] or bold
[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Innovators include Baecker &amp; Marcus [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] who utilize bold, italics, font size,
underlines, serif/sans-serif to enhance readability of computer code - a practice
now commonplace in most code editors. Fat fonts [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], is a specialized font
that varies font weight per character so that the ink varies in proportion to the
numeric value represented. Muriel Cooper’s Visible Language Workshop explored
3D typographic spaces with variations in size, case, color and font family, e.g.
[
        <xref ref-type="bibr" rid="ref20">20</xref>
        ]. Typographic maps [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] uses only type to create geographic maps.
      </p>
      <p>
        Typography and cartography have centuries of history with innovative
font encoding of information in documents hundreds of years old (e.g. fig. 1).
There are many techniques for creating emphasis and differentiation with font,
with various guidelines and conventions (e.g. typographic [
        <xref ref-type="bibr" rid="ref13 ref21">21, 13</xref>
        ], cartographic
[
        <xref ref-type="bibr" rid="ref11 ref17">11, 17</xref>
        ], user interface design [
        <xref ref-type="bibr" rid="ref10 ref12 ref22">12, 10, 22</xref>
        ]).
      </p>
      <p>Historically, user interfaces recommended against type attributes due to low
resolution displays. New higher resolution devices, improved font rendering
technology, a wide range of typefaces designed for the screen and rich markup
formats, now result in recommendations to more broadly use type-specific
attributes for user interfaces and web.</p>
      <p>
        In contrast to infovis for information retrieval, text-based search results and
navigation interfaces typically differentiate metadata associated with a document
using type size, color, underlines (e.g. links) or font family (e.g. titles). Bold or
color is frequently used to highlight search terms. See Hearst [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] or popular search
interfaces, e.g. Google, Yahoo, Bing, Ebay, Amazon, NYTimes, LinkedIn, etc.
      </p>
      <p>Notation systems such as chemical formulas (e.g. [As@Ni12As20]3−),
mathematical formulas (e.g. μe(A) = inf{λ∗(O) | O ∈ O, A ⊂ O} ) and markup notation
(e.g. &lt;div class=“body”&gt;Text &lt;/div&gt;) use different type elements to
emphasize, delineate or otherwise add information to text.</p>
      <p>Based on an review of these above domains, a list of font-specific properties
(not including generic color and size visual attributes) include:
• Weight (bold) can have up to six weights for screen and up to 9 for print.
• Italic or Oblique are both sloped fonts but italics have different letterforms
and there are instances of reverse italics and vertical italics.
• CASE includes UPPER, lower, Mixed and Small Caps. Uppercase is
designed to standout from lowercase while small caps blend in.
• S p a c i n g . Tracking (space between letters) and leading (between lines).
• Typeface indicates font family: sans, blackletter, script, source, MATHBOLD,...
• Underline can be d:i:s:tr:a:c:t:in:g:. Typographers recommend .s.u.b.t.l.e. variants.
• Condensed/Expanded. Similar to, but better than, horizontally scaled fonts.
• Superscript and subscript encode via size and position to adjacent text.
• “Paired delimiters” evoke enclosure by pairing the same (or mirrored) shapes.
• Alphanumeric glyphs (A,B,C,1,2,3) can literally encode data and are uniquely
orderable. Glyphs not native to the viewer (e.g. α, β, γ) are also orderable,
but symbols (e.g. ∞, ∀, [) are not orderable.
3</p>
      <p>Type for Knowledge Maps and Information Retrieval
Type attributes can be used to encode additional information at different levels
of use in knowledge mapping and information retrieval, ranging from low-level
document views, to search lists, to the macro-level overviews. A few examples:
3.1</p>
    </sec>
    <sec id="sec-2">
      <title>Type Visualization on Texts</title>
      <p>In some search results, full sentences, abstracts or lead paragraphs are presented
(e.g. BioText Search Engine, Wikipedia’s Today’s featured article archive). At
the micro-level of documents and texts, type attributes can be used to aid
comprehension without changing layout. Text skimming is a reading technique of
rapid eye movement across a large body to text to get the main ideas and
content overview. At a low level, the strategy requires the reader to dip into the
text looking for words such as proper nouns, unusual words, enumerations, etc.
Word frequency analysis can be used to weight the least common words (fig. 2).</p>
      <p>
        Font weight draws visual attention to the highest contrast which are the
least frequent words as per text skimming strategy. In the above introductory
paragraph on flight, the terms glider and motor have the heaviest weight and
are possible terms for query refinement. Similarly, visual weighting of proper
nouns, enumerations and unusual words facilitates fact-finding tasks. Attributes
could instead be based on specific domain vocabulary [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] with interactions (e.g.
drag and drop) to facilitate guided search. Other type attributes can also be
applied, e.g. in the above figure dotted underlines indicate search terms. Also, less
important parts of speech (e.g. articles, pronouns, etc) are italicized to enhance
figure-ground separation between the heavy-weight words and background.
3.2
      </p>
    </sec>
    <sec id="sec-3">
      <title>Type Visualization on Lists</title>
      <p>Query results can be visualized and may include quantitative data e.g.
readership, relevance or number of citations. Newsmap.jp displays news headlines in a
treemap, with headline size indicating readership (fig. 3).</p>
      <p>Instead, using fixed size text enables more legible headlines to be displayed
and then font-weight can be used to encode readership, either by setting the
weight per headline (fig. 4-left), or proportionally encoding readership by setting
bold to proportionally correspond to the magnitude (fig. 4-right).</p>
      <p>
        Any visualization technique has some degree of lossiness as data is
transformed into a visual encoding. Lossiness can be evaluated in the above
representations by measuring:
1. Number of readable headlines: if a headline is too truncated, too small to
read or does not appear, it is considered unreadable. Six point was used as
the threshold for too small for a 96dpi screen.
2. Number of uniquely perceivable sizes: can be estimated using prior
experimental data [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], e.g. area ± 5% or length ±2.5%. For font weight, a show of
hands in seminar settings yielded the most responses for 4 levels of weights.
3. Area of the overall plot.
      </p>
      <p>Information density is a function of the measures (#readable x #sizes / area).
Density was measured across all three variants and repeated for different aspect
ratios with different numbers of items (e.g. sparse scenario, dense scenario).
Information density for the proportional encoding consistently outperformed the
treemap by a factor of 2 while the font weight encoding could underperform:</p>
      <sec id="sec-3-1">
        <title>Variant Font Weight Proportion</title>
      </sec>
      <sec id="sec-3-2">
        <title>Normal Dense Sparse</title>
        <p>1.42x 0.67x 0.86x
2.68x 2.22x 2.07x</p>
        <p>These three different encodings were presented to three different groups of
infovis researchers, each with more than 10 attendees. Proportional encoding
received a positive response. None of the participants were confused by the
encoding and consistently scored 3 or 4 on a 1-4 scale on three questions indicating
desirability, ease of use and likelihood of ease for others to understand.</p>
        <p>One concern expressed with proportional encoding is that the maximum
proportion length is limited to the shortest headline. This can be addressed by
adding the beginning of the lead sentence to the end of the headline, similar to
email lists (fig. 5). Also, the approach can be extended to convey multiple data
attributes, e.g. (font weight and underline).</p>
        <p>This approach could lead to new techniques for rapidly scanning through
search results, particularly in applications where each result is presented as an
individual row. For example, news search on financial terminals (e.g. Reuters,
Bloomberg) typically result in dense lists of headlines where space is at a
premium, so visual techniques such as icons or color are used to indicate additional
information; and font-based approaches could also be used to provide
information without requiring any additional space. Similarly, facets for query refinement
may have additional metadata and typically exist in narrow side panels. For
example, fig. 6 represents facets for query refinement provided by Amazon on a
search for information retrieval where the length of underline has been added to
indicate the quantity of matching items.</p>
        <p>Network Administration | Computers &amp; Technology | Databases |</p>
        <p>Programming | Web Development &amp; Design | Reference
Macro-scale visualizations of large domains of information usually have some text
but sometimes text can be minimal. For example, choropleth maps color regions
to indicate data values and are extremely popular. However, choropleth maps
have issues, including: 1) Small areas can be invisible (e.g. Dubai, Singapore
are not visible on a world map); 2) Identification of a selected area or finding a
named target can be difficult e.g. 63% of young adults in USA could not locate
Iraq on a map in a National Geographic survey in 2006; and 3) Data encoding
is typically limited to a single value, such as hue or brightness.</p>
        <p>Instead of using shapes to identify regions, mnemonic codes (e.g. ISO country
codes) are used. With some spatial adjustment to remove overlap, all labels
are visible while maintaining local proximity. Color can still be used, as well
as type-specific attributes to encode additional data. Health expenditures, life
expectancies and HIV data are represented using bold, case and italic into a
single label in fig. 7 allowing complex queries to be made visually, e.g. Are
there countries with high HIV (italics) and short lives (lowercase) even though
a signification portion of GDP is spent on health care (ultrabold)? (A. Yes, e.g.
Rwanda (rwa) or Sierra Leone (sle)).</p>
        <p>In addition to offering greater data density and no loss of small countries,
a similar map (using only labels and color) resulted in 62% correct responses
on identification tasks compared to 17% correct for a shape-based map with no
labels (i.e. choropleth map); in surveys in a seminar setting. This indicates a
strong potential for richly labeled maps to offer greater information density and
lower data lossiness.</p>
        <p>
          In knowledge maps (e.g. scimaps.org) representations range from highly
labeled maps such as Skupin’s self-organizing maps (e.g. [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ]) to graphs with many
or no labels (e.g. [
          <xref ref-type="bibr" rid="ref16 ref3">16, 3</xref>
          ]). This approach can be applied to any map or graph with
minimally overlapping labels (e.g. fig. 8).
Feedback, metrics and informal surveys are promising and indicate that
fontspecific attributes can be used to increase data density in texts (e.g. abstracts,
lead paragraphs) and lists (e.g. results lists, facets) to add additional information
to aid tasks such as fact finding, information gathering and query refinement
(e.g. fig. 2,5,6). Font-specific attributes could also be potentially used on labeled
knowledge maps to add additional information (e.g. fig. 7).
        </p>
        <p>
          These typographic attributes may not have the same degree of effectiveness
as other visual channels (e.g. size, hue, angle, shape). Visual channels have been
researched in more detail (e.g. Bertin, Cleveland, MacKinlay, Wilkinson, Mazza,
Munzner), although a definitive list ranking visual channels for different types
of tasks and number of uniquely perceivable levels does not exist. Font-specific
attributes can be mapped back to these well-known visual channels [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ] and then
visual attribute heuristics can be used for guidance. For example, font weight,
which utilizes visual channels of size (i.e. line width) and intensity, will rank
higher for effectiveness of ordered or quantitative data encodings than font
family, which utilizes the visual channel of shape. These existing heuristics can also
be used to identify combinations of font-attributes that may be integral (e.g.
capitalization + italic) vs. separable (e.g. font weight + underline). While the
mapping of font-specific attributes to more general visual channels can provide
an initial indication of promising attributes and combinations, usability testing
should be done in the future to validate these approaches.
        </p>
        <p>Future work should also consider different representations e.g. there may be
other novel visualizations; as well as systems implemented to evaluate
applicability and efficacy to specific information retrieval tasks.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Afzal</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maciejewski</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jang</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Elmqvist</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ebert</surname>
            ,
            <given-names>D.S.:</given-names>
          </string-name>
          <article-title>Spatial text visualization using automatic typographic maps</article-title>
          .
          <source>Visualization and Computer Graphics</source>
          , IEEE Transactions on
          <volume>18</volume>
          (
          <issue>12</issue>
          ),
          <fpage>2556</fpage>
          -
          <lpage>2564</lpage>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Baecker</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marcus</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Human Factors and Typography for More Readable Programs</article-title>
          .
          <string-name>
            <surname>Addison-Wesley</surname>
          </string-name>
          (
          <year>1990</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Boyack</surname>
            ,
            <given-names>K.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Klavans</surname>
          </string-name>
          , R.:
          <article-title>Creation of a highly detailed, dynamic, global model and map of science</article-title>
          .
          <source>Journal of the Association for Information Science and Technology</source>
          <volume>65</volume>
          (
          <issue>4</issue>
          ),
          <fpage>670</fpage>
          -
          <lpage>685</lpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Brath</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Banissi</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>The design space of typeface. Visualization and Computer Graphics</article-title>
          , IEEE Transactions on (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Chan</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Podlaseck</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>A personalized navigation tool for online listening and free browsing: The glass engine</article-title>
          .
          <source>In: Proceedings of World Conference on Educational Multimedia, Hypermedia and Telecommunications</source>
          <year>2002</year>
          . pp.
          <fpage>263</fpage>
          -
          <lpage>264</lpage>
          (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Dobson</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ruecker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gabriele</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sinclair</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>The mandala browser (</article-title>
          <year>2005</year>
          ), http://mandala.humviz.org/help/
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Ellingham</surname>
          </string-name>
          , H.:
          <article-title>A chart illustrating some of the relations between the branches of natural science and technology</article-title>
          . http://bit.ly/1hlJ6VK (
          <year>1948</year>
          ), accessed
          <volume>11</volume>
          /02/2013
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Hearst</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Search User Interfaces</article-title>
          . Cambridge University Press (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Heer</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bostock</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Crowdsourcing graphical perception: Using mechanical turk to assess visualization design</article-title>
          .
          <source>In: ACM Human Factors in Computing Systems (CHI)</source>
          . pp.
          <fpage>203</fpage>
          -
          <lpage>212</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Heim</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>The Resonant Interface: HCI Foundations for Interaction Design</article-title>
          .
          <article-title>Pearson Education Inc</article-title>
          . (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Hodges</surname>
            ,
            <given-names>E.R.S.:</given-names>
          </string-name>
          <article-title>The Guild Handbook of Scientific Illustration</article-title>
          . John Wiley (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Kahn</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lenk</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Principles of typography for user interface design</article-title>
          .
          <source>InteractionsNew</source>
          York pp.
          <fpage>15</fpage>
          -
          <lpage>29</lpage>
          (
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Lupton</surname>
            ,
            <given-names>E.: Designing</given-names>
          </string-name>
          <string-name>
            <surname>Type. Yale</surname>
          </string-name>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Mayr</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mutschke</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Petras</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Reducing semantic complexity in distributed digital libraries: Treatment of term vagueness and document re-ranking</article-title>
          .
          <source>Library Review</source>
          <volume>57</volume>
          (
          <issue>3</issue>
          ),
          <fpage>213</fpage>
          -
          <lpage>224</lpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Nacenta</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hinrichs</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Carpendale</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Fatfonts: combining the symbolic and visual aspects of numbers</article-title>
          .
          <source>In: Proceedings of the International Working Conference on Advanced Visual Interfaces</source>
          . pp.
          <fpage>407</fpage>
          -
          <lpage>414</lpage>
          . ACM (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Paley</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Map of science</article-title>
          . http://wbpaley.com/brad/mapOfScience/index.html (
          <issue>accessed</issue>
          : 11/12/2013)
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Robinson</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Morrison</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Muehrcke</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kimerling</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Guptill</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          : Elements of Cartography. John Wiley &amp; Sons, New York, NY (
          <year>1995</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Skupin</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>The world of geography: Visualizing a knowledge domain with cartographic means</article-title>
          .
          <source>Proceedings of the National Academy of Sciences of the United States of America</source>
          <volume>101</volume>
          (
          <issue>Suppl 1</issue>
          ),
          <fpage>5274</fpage>
          -
          <lpage>5278</lpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Skupin</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Biberstine</surname>
            ,
            <given-names>J.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Börner</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Visualizing the topical structure of the medical sciences: a self-organizing map approach</article-title>
          .
          <source>PloS one 8</source>
          (
          <issue>3</issue>
          ),
          <year>e58779</year>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Small</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Navigating large bodies of text</article-title>
          .
          <source>IBM Systems Journal</source>
          <volume>35</volume>
          ,
          <fpage>515</fpage>
          -
          <lpage>525</lpage>
          (
          <year>1996</year>
          ), http://diglib.eg.org/EG/DL/conf/EG2013/stars/039-
          <fpage>063</fpage>
          .pdf
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Squire</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Willberg</surname>
            ,
            <given-names>H.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Forssman</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Getting it Right with Type</article-title>
          .
          <source>Laurence King Publishing</source>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Teague</surname>
          </string-name>
          , J.:
          <source>Fluid Web Typography. New Riders</source>
          , Berkeley, CA (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Weskamp</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          : Projects: Newsmap. http://marumushi.com/projects/newsmap (
          <year>2004</year>
          ), accessed:
          <volume>03</volume>
          /03/2014
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>