<!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>Poster: Relative Relationship ODP: Scaling Case</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Holly Ferguson</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Charles F. Vardeman II</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Introduction &amp;</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>University of Notre Dame</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>This research describes a proposed case study utilizing the Dynamic Relative Relationship (RR) Pattern. This poster is aimed at those interested in Linked Open Data (LOD) and Decision Support (DS) integration, ODP translations and mappings, and/or Building Information Management (BIM). Speci cally, it is an ontology design pattern for dynamically conceptualizing, establishing, tracking, and updating relative relationships and dependencies between entities (real or representational) of a physical, temporal, and/or importance scope; it is potentially an intermediate step for facilitating data transitions between LOD and DS Frameworks. We present an RR pattern use case from the BIM domain showing how a translation between two building models with di erent physical scales and di erent geometric coordinate systems are given foundation relative to one another for data/schema interoperability.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Motivation</title>
      <p>
        As professionals continue to answer increasingly complex questions with more
than two decision criteria, the more demands are added into the Multi-Criteria
Analysis Decision Support (DS) Tools that process data for answers. This level
of DS requires integrations of data from distributed sources to be pre-structured
via consumable Linked Open Data methods. Our research group is involved
with building simulation technologies, their data semantics, and techniques to
improve interoperability [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Currently in the building professions, tools rely on
secular data schemas each with their own set of semantics making it di cult to
know which tools are the most accurate. In order to compare and integrate the
plethora of data available to each of these separate tools, we need methodologies
for integrating sets of data from a variety of ontological structures, the ability
to swap between di erent data schemas such as Building Information Modeling
(BIM/IFC) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], and for capturing the relationship between two entities.
      </p>
      <p>Data interoperability via translation automation mean building models could
be mapped to a common schema allowing simulations across platforms without
laborious and often ine ective intervention; thus, we developed the Dynamic
Relative Relationship (RR) Pattern that provides this functionality. In a larger
scope, previously incomparable entities now have a foundation from which to
be related via any type of relationship. Thus, we can now e ectively handle,
rank, and structure data over distributed data access points, potentially allowing
data to be computationally constructed, enabling more powerful inferences, and
reaching more accurate predictions. This paper describes the core RR Pattern,
gives an example Physical Scale translation instance between two buildings, and
discusses some of the overall implications. For additional details and examples
beyond that provided, please see the WOP 2015 full research paper entitled, \An
Ontology Design Pattern for Dynamic Relative Relationships."
2</p>
    </sec>
    <sec id="sec-2">
      <title>Core Pattern for Dynamic Relative Relationships</title>
      <p>
        Currently, the gap between Linked Open Data and DS Systems is problematic,
especially when there are more than two decision criteria and domain speci c
applications (city planning, geospatial, engineering, architectural) that need to
consume distributed data sources exposed using Linked Open Data principles.
Patterns capable of computationally (and eventually automatically)
interconnecting data, concepts, and methods are required to relate entities across a
variety of domains as well as track changes and dependencies over time; below we
discuss one possible use for building model interoperability. Additionally, there
is the challenge of automatically integrating [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] newly discovered intelligent data
sets [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] into tools in real-time to enhance DS Systems [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>
        The RR Pattern [Figure 1] can record physical, temporal, informational,
idealistic, and other data/entity relationships and dependencies; it essentially
creates a framework a relationship between any two entities. Instances require
an origin and target entity, representations of those two entities, and the
relationship description that links them together. The pattern provides data hooks
that allow dynamic updating of linked data as changes occur in preference
systems, scaling systems, or temporal parameters. The goal of the RR Pattern is to
provide a way to create instances, link them together for updatability, and use
them to automatically integrate several types of ontologies or patterns [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
The situation-based objectives for the example explored in the next section are
solved in the context of the RR Pattern [Figure 1]. In particular, the example
demonstrates a translation and links two separate scaling systems-or geometric
relationships. Scale itself is the de nition of the impact or perception of one
entity relative to another, making it a specialized relative relationship.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Example Use Case for Describing Physical Scales</title>
      <p>At a basic level, the RR Pattern [Figure 1] is meant to answer \How does one
entity compare to another? Within the Construction Industry alone there are
any number of data integration challenges that can be ameliorated by using the
RR Pattern. For example, if a client has several houses proposed for construction
with computational models existing in di erent data formats (suppose one model
is a CAD File and one is an IFC le) and they need to be processed through a
common application to test building footprint areas against available space on
potential building sites, there will need to be a way to integrate these le types
[Figure 2]. To comprehensively synthesize these pieces together that are not
otherwise directly comparable, we need a mechanism such as the RR Pattern that
records and maintains how the data in these two models relate, so this problem
tractable over di erent semantic contexts and distributed sources [Figure 3].</p>
      <p>While the pattern may include only the establishment of scale between one
building model and another to have a method of nding the best t selection for
a site, it can also record any other desired data with this relationship instance or
by including several instances as a sequence describing the necessary contextual
limits. In addition to this scale data [Figure 3] that informs us that geometries
in the CAD File are twice as big as geometries in the IFC File, the example
populated pattern also indicates the dependency of the relationship, coordinate
system, scope, domain, usage, scale type (volume), entity age, and entity
expected lifespan-to name a few possibilities. Apart from this example use case,
the RR Pattern can also potentially become a dynamic \link" for
communication and provides a tool to maintain data or preferences so that solutions can
be better understood, tracked, and updated as needed for decision making.</p>
    </sec>
    <sec id="sec-4">
      <title>Conclusion</title>
      <p>We present a Dynamic Relative Relationship ontology pattern in the context of
comparing two building models of di erent coordinates systems and le types.
This pattern provides a relationship tracking mechanism and a connection
between data and the decision frameworks that might use it as a meta-data layer
of information. In addition to a physical scaling use case, the RR Pattern can be
used for other physical, temporal, and informational relationships so that
structured data over distributed data access points can be computationally created
to enable more powerful inferences and reach more accurate predictions.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>BIM</surname>
            <given-names>XML</given-names>
          </string-name>
          , http://www.bimxml.org/
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. GeoKnow:
          <article-title>Making the web an exploratory for geospatial knowledge</article-title>
          , http:// geoknow.eu/Welcome.html
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Blomqvist</surname>
          </string-name>
          , E.:
          <article-title>Pattern ranking for semi-automatic ontology construction</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Blomqvist</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>The use of semantic web technologies for decision support - a survey</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Degbelo</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuhn</surname>
            ,
            <given-names>W.:</given-names>
          </string-name>
          <article-title>A conceptual analysis of resolution</article-title>
          .
          <source>In: Proceedings XIII GEOINFO</source>
          . pp.
          <volume>11</volume>
          {
          <fpage>22</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>El</given-names>
            <surname>Idrissi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Baina</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Baina</surname>
          </string-name>
          ,
          <string-name>
            <surname>K.</surname>
          </string-name>
          :
          <article-title>Automatic generation of ontology from data models: A practical evaluation of existing approaches pp</article-title>
          .
          <volume>1</volume>
          {
          <fpage>12</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Smirnov</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Levashova</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shilov</surname>
          </string-name>
          , N.:
          <article-title>Patterns for context-based knowledge fusion in decision support systems 21</article-title>
          , 114{
          <fpage>129</fpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>