<!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>Ontology modeling with domain experts: The GeoVoCamp experience</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Pascal Hitzler</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Krzysztof Janowicz</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Adila A. Krisnadhi</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Faculty of Computer Science</institution>
          ,
          <addr-line>Universitas</addr-line>
          <country country="ID">Indonesia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Typical Work ow at a GeoVoCamp</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University of California</institution>
          ,
          <addr-line>Santa Barbara</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Wright State University</institution>
          ,
          <addr-line>OH</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>A series of GeoVoCamps, run at least twice a year in locations in the U.S., have focused on ontology design patterns as an approach to inform metadata and data models, and on applications in the GeoSciences. In this note, we will redraw the brief history of the series as well as rationales for the particular approach which was chosen, and report on the ongoing uptake of the approach.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Since Spring 2012, a series of GeoVocamps has been held in the U.S. which used
a modeling approach driven by ontology design patterns (ODPs). In terms of
topics they have mostly (but not exclusively) stayed close to the GeoSciences and
related disciplines. Events have been held annually in Spring in Santa Barbara,
CA, and in Fall in the eastern U.S., mostly in the Washington D.C. area, with
additional occasional events in locations such as Notre Dame, IN, or Dayton,
OH.4 Each event usually drew between 20 and 30 participants, including 8-10
\regulars" which come very frequently to the events.</p>
      <p>GeoVoCamps are unconferences, and as such are loosely structured, with the
actual program decided upon by the participants on the spot. Starting with the
Santa Barbara event 2012, the organizers suggested to use ontology design
patterns as modeling approach, and indeed most of the work at these GeoVocamps
has adopted this since.
frequent planary sessions in which reports on the ongoing work are presented and
feedback is solicited from all participants. Sometimes some participants switch
between groups based on personal interest and on the need to have a balance of
experts in each of the groups.</p>
      <p>Working groups ideally have a mix of participants: two or more domain
experts, one or two participants familiar with base data addressed by the modeling,
at least one ontology engineer with knowledge about formal axiomatizations and
technical modeling choices, and at least one person who is familiar with the
general ODP-based modeling process. Domain experts with di ering perceptions of
their topic are particularly stimulating for the discussions, as are data providers
with di erent target use cases in mind: reconciling these di erences within a
single pattern usually leads to more versatile, and thus more readily reusable,
patterns.</p>
      <p>When a working group starts working on a model for a notion, then often
the rst half-day is used up by determining the scope of what shall be modeled,
and by understanding and possibly reconciling di erent ideas which the group
participants may have about the topic. This phase often feels almost
unproductive, in particular for participants which did not have previous exposure to the
process. After a few hours, however, the scope usually falls into place, and at
this stage rst rough drafts can emerge. The initial phase is often dominated by
discussing the exact de nition of terminology, by looking at concrete examples,
in particular exceptional cases, by looking at real data and potential use cases,
and sometimes by formulating concrete competency questions for a use case.</p>
      <p>
        To give an example about this initial process: In some recent work regarding
data from high-energy physics experiments at CERN's LHC [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], we originally
set out to model the general notion of nal state as in particle physics. After
some time, though, it turned out to be more adequate and in tune with data
and intended use cases to model a more speci c notion of detector nal state,
which de nes the physical characteristics that form the basis of measurements as
presented in a published paper about ndings from a particle physics experiment
such as those located at the Large Hadron Collider (LHC) at CERN.
      </p>
      <p>
        Most of the discussions during the remainder of a working group at a camp
will then evolve around producing an informal graph which, for the ontology
engineers, captures the main components of the notion in the sense that it
informs the structure of the RDF graph which results from populating the pattern
with data. To give an example of this type of informal graph, consider Figure 1
which is taken from [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. It informs the RDF graph structure but it it still bare of
details regarding RDF and OWL, e.g. namespaces, domain/range restrictions,
and other axioms. In our experience, this format is ideal in order to engage with
domain experts; of course the ontology engineers in the group will be aware
of the missing details and will make sure that they gather enough details and
knowledge to be able to ll in the more technical details after the event.
      </p>
      <p>At the end of the 2-3 day event, a working group has then usually completed
a stable draft of a pattern in the sense of having a stable graph, and having an
understanding of how to populate the graph. The ontology engineers will also
have made sure that they understand enough of the domain expert's perspectives
to be able to come up with axiomatizations in OWL. A working group may then
choose to work out further details o ine, provide axiomatizations in OWL, as
well as example populations with available data, and may publish the resulting
documentation at a workshop, conference or journal. Sometimes work is also
continued at a follow-up camp.
3</p>
    </sec>
    <sec id="sec-2">
      <title>Spreading the GeoVoCamp Model</title>
      <p>The interactive modeling approach taken at the GeoVoCamps as reported, has in
the meantime been carried over into other events, communities, and disciplines
mostly mediated by some camp participants. While we can in no way account
for all the in uences, we want to mention a few of the activities which were
spawned.</p>
      <p>
        Some of these actually resulted directly in camps which were targeted at
speci c application areas which were previously not considered. For example, for
the 2015 Santa Barbara event5 international experts on environmental impact of
product life cycles { life cycle analysis or LCA for short { gathered to jointly look
into metadata modeling for data integration and applications in their area. Two
pattern descriptions already resulted from this, published at the 2015 Ontology
and Semantic Web Patterns, WOP 2015, in Bethlehem, PA [
        <xref ref-type="bibr" rid="ref3 ref6">3,6</xref>
        ]. An event at
University of Notre Dame held in summer 20156 drew experts from high-energy
physics with involvement in CERN LHC experiments, as already mentioned
above, and a corresponding pattern description has also already been published
at WOP2015 [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
5 http://vocamp.org/wiki/GeoVoCampSB2015
6 http://vocamp.org/wiki/VoCampND2015
      </p>
      <p>
        The authors are furthermore all involved in the project GeoLink,7 funded by
the National Science Foundation under the EarthCube program, which has at its
goal to showcase an integration infrastructure for earth science data repositories.
The GeoVoCamp approach and ontology design patterns have been fully adopted
by the ongoing project [
        <xref ref-type="bibr" rid="ref4 ref5">4,5</xref>
        ].
      </p>
      <p>Frequent invited presentations to speak on the approach also indicate growing
interest. E.g., such invited presentations have been made by di erent frequent
GeoVoCamp participants for the ontolog forum,8 at an OGC workshop,9 at
an RDA event,10 for several EarthCube workshops and events,11 at ESIP, the
Federation of Earth Science Information Partners,12 etc.</p>
      <p>In our experience, one reason why the approach easily appeals to domain
experts in application areas is that discussions are predominantly at the level
of knowledge transfer : The domain experts are required to educate the ontology
engineers about their most intricate terminoloty, and to do so to the minimum
extent needed such that a formal model can be produced. At the same time,
with suitable guidance by the ontology engineers, the domain experts can be
shielded from technical discussions and from implementation details.
4</p>
    </sec>
    <sec id="sec-3">
      <title>Bridging the Interdisciplinarity Gap</title>
      <p>We want to brie y share some of our thoughts why our setting seems to be so
e ective for interdisciplinary modeling.</p>
      <p>It is probably four things which come together in a very favorable way.
(1) The ODP approach prompts the group to work on one notion at a time.
This provides a focus on a particular issue which enables the group to really
explore the ner details of the notion. The informal graph which is collaboratively
produced further emphasizes that the group is looking to develop precise and
versatile de nitions.</p>
      <p>(2) Di erences in perspectives by the domain experts in the group can be
leveraged through their reconciliation into a single model. Hence they are
particularly helpful in generating models which are versatile, in the sense that they
capture all these di erent perspectives, and thus are general enough to be easily
adopted or reused for other purposes or scenarios.</p>
      <p>(3) The presence of ontology engineers in the group, which may have little
or no knowledge about the subject matter which is to be modeled, can actually
be turned to a signi cant advantage: In essence, the group needs to start by
explaining to the ontology engineers what their notions really mean, and ontology
engineers will ask for clari cations if the de nitions given are not crisp enough to
7 http://www.geolink.org/
8 http://ontolog.cim3.net/cgi-bin/wiki.pl?ConferenceCall_2014_01_23
9 http://earthcube.org/event/earthcube-session-ogc-quarterly-meeting-dc
10 E.g.
https://rd-alliance.org/rda-metadata-semantics-workshopindianapolis-usa-feb-23-25-2015.html
11 E.g. http://daselab.cs.wright.edu/pub/2014-05-DC-C4P.pdf
12 http://daselab.cs.wright.edu/pub/2014-07-ESIP-ODP.pdf
be developed into a formal model. This process will prompt domain experts to be
precise, and to expose critical cases or exceptions to the general de nitions, and it
will also help to expose di erences in perspectives by the domain experts. In our
experience, it even sometimes exposes di erences about which the participating
domain experts were not aware earlier.</p>
      <p>(4) Ideally, a working group also has participants which can act as bridges
between the domain experts and the ontology engineers, i.e. participants who have
some knowledge about either side. They can help explain when communication
gaps occur, or if some notions have di erent meanings in di erent communities.
Typical examples for the latter would be the meaning of \data" versus
\metadata", or the notion of \model."</p>
      <p>Throughout, it is paramount that participants understand their roles.
Ontology engineers have to make sure they receive the information and minimal
knowledge needed to produce the formal model after the meeting. Domain
experts and data providers need to be aware that there are modeling experts in
the room who have solid advice on how to structure a model. Bridge builders
need to be aware that one of their main roles is that of facilitator and mediator.
Listening to each other, and going with the ow of the group are very important
in order to obtain useful results.
5</p>
    </sec>
    <sec id="sec-4">
      <title>Tangible Outcomes</title>
      <p>It is di cult to count all the outcomes { even the tangible ones { of an
unconference. We easily came up with over a dozen papers which directly resulted from
GeoVoCamp work, and almost a dozen which were directly in uenced by it.13
Of course these are primarily the papers where we were directly involved. And
for many of the pattern papers the corresponding ontology design patterns have
also been made available on the Web as OWL les.14</p>
      <p>A signi cant body of work started in the working groups also awaits
completion and casting into concrete patterns and papers. As these things go, without
concrete deadlines or project demands, it depends solely on the priorities and
bandwidths of the working group members whether this follow-up work will
happen.
6</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusions</title>
      <p>The GeoVocamps for ontology design pattern modeling have brought together an
interdisciplinary community including ontology engineers and domain scientists
from di erent disciplines, in order to engage in the modeling of conceptually
strong and versatile ontology design patterns. We are seeing tangible outcomes,
as well as a dissemination of the ideas and approach.
13 http://dase.cs.wright.edu/blog/geovocamps-taking-stock
14 E.g., on http://ontologydesignpatterns.org/.</p>
      <p>We will continue the work, announcements can be found at http://vocamp.
org/wiki/Main_Page, or contact us for inclusion in our distributor.</p>
      <p>Acknowledgements. This work was supported by the National Science
Foundation under award 1017225 III: Small: TROn { Tractable Reasoning with
Ontologies and award 1440202 EarthCube Building Blocks: Collaborative Proposal:
GeoLink { Leveraging Semantics and Linked Data for Data Sharing and
Discovery in the Geosciences.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Carral</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cheatham</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dallmeier-Tiessen</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Herterich</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hildreth</surname>
            ,
            <given-names>M.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hitzler</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krisnadhi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lassila-Perini</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sexton-Kennedy</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Watts</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vardeman</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>An ontology design pattern for particle physics analysis</article-title>
          .
          <source>In: Proceedings of the Workshop on Ontology and Semantic Web Patterns (6th edition)</source>
          ,
          <source>WOP2015</source>
          , Bethlehem, PA,
          <year>October 2015</year>
          (
          <year>2015</year>
          ), to appear
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Hu</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Janowicz</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Carral</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Scheider</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuhn</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berg-Cross</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hitzler</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dean</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kolas</surname>
            ,
            <given-names>D.:</given-names>
          </string-name>
          <article-title>A geo-ontology design pattern for semantic trajectories</article-title>
          . In: Tenbrink,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Stell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.G.</given-names>
            ,
            <surname>Galton</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Wood</surname>
          </string-name>
          ,
          <string-name>
            <surname>Z</surname>
          </string-name>
          . (eds.) Spatial Information Theory { 11th International Conference, COSIT 2013,
          <article-title>Scarborough</article-title>
          , UK, September 2-
          <issue>6</issue>
          ,
          <year>2013</year>
          .
          <source>Proceedings. Lecture Notes in Computer Science</source>
          , vol.
          <volume>8116</volume>
          , pp.
          <volume>438</volume>
          {
          <fpage>456</fpage>
          . Springer (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Janowicz</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krisnadhi</surname>
            ,
            <given-names>A.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hu</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Suh</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weidema</surname>
            ,
            <given-names>B.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rivela</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tivander</surname>
          </string-name>
          , J., Meyer, D.E.,
          <string-name>
            <surname>Berg-Cross</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hitzler</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ingwersen</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuczenski</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vardeman</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ju</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cheatham</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>A minimal ontology pattern for life cycle assessment data</article-title>
          .
          <source>In: Proceedings of the Workshop on Ontology and Semantic Web Patterns (6th edition)</source>
          ,
          <source>WOP2015</source>
          , Bethlehem, PA,
          <year>October 2015</year>
          (
          <year>2015</year>
          ), to appear
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Krisnadhi</surname>
            ,
            <given-names>A.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hu</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Janowicz</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hitzler</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Arko</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Carbotte</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chandler</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cheatham</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fils</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Finin</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ji</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jones</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karima</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mickle</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Narock</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>O'Brien</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Raymond</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shepherd</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schildhauer</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wiebe</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>The GeoLink framework for pattern-based linked data integration</article-title>
          .
          <source>In: ISWC2015 Poster Proceedings</source>
          (
          <year>2015</year>
          ), to appear
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Krisnadhi</surname>
            ,
            <given-names>A.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hu</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Janowicz</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hitzler</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Arko</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Carbotte</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chandler</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cheatham</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fils</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Finin</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ji</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jones</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karima</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mickle</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Narock</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>O'Brien</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Raymond</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shepherd</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schildhauer</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wiebe</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>The GeoLink modular oceanography ontology</article-title>
          .
          <source>In: Proceedings ISWC2015. Lecture Notes in Computer Science</source>
          , Springer (
          <year>2015</year>
          ), to appear
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Yan</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hu</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuczenski</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Janowicz</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ballatore</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krisnadhi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hitzler</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Suh</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ingwersen</surname>
            ,
            <given-names>W.:</given-names>
          </string-name>
          <article-title>An ontology for specifying spatiotemporal scopes in life cycle assessment</article-title>
          .
          <source>In: Proceedings of the Diversity++ Workshop</source>
          , Bethlehem, PA,
          <year>October 2015</year>
          (
          <year>2015</year>
          ), to appear
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>