<!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>
      <journal-title-group>
        <journal-title>19http://www.plosone.org/article/info%3Adoi%2F10.1371%2Fjournal.pone.0077626#pone</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Relations for Reusing (R4R) in A Shared Context: An Exploration on Research Publications and Cultural Objects</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Andrea Wei-Ching Huang</string-name>
          <email>andreahg@iis.sinica.edu.tw</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tyng-Ruey Chuang</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Institute of Information Science</institution>
          ,
          <addr-line>Academia Sinica, Taipei</addr-line>
          ,
          <country country="TW">Taiwan</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2014</year>
      </pub-date>
      <fpage>49</fpage>
      <lpage>60</lpage>
      <abstract>
        <p>Will the rich domain knowledge from research publications and the implicit cross-domain metadata of cultural objects be compliant with each other? A contextual framework is proposed as dynamic and relational in supporting three different contexts: Reusing, Publication and Curation, which are individually constructed but overlapped with major conceptual elements. A Relations for Reusing (R4R) ontology has been devised for modeling these overlapping conceptual components (Article, Data, Code, Provence, and License) for interlinking research outputs and cultural heritage data. In particular, packaging and citation relations are key to build up interpretations for dynamic contexts. Examples are provided for illustrating how the linking mechanism can be constructed and represented as a result to reveal the data linked in different contexts.</p>
      </abstract>
      <kwd-group>
        <kwd>citation</kwd>
        <kwd>context</kwd>
        <kwd>cultural heritage</kwd>
        <kwd>curation</kwd>
        <kwd>ontology</kwd>
        <kwd>packaging</kwd>
        <kwd>publication</kwd>
        <kwd>R4R</kwd>
        <kwd>research data</kwd>
        <kwd>reuse</kwd>
        <kwd>sharing</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        A digital object Y curated in a digital museum, is a cultural object Y with metadata
descriptions. This cultural object Y reused by an academic article is not a cultural object
but a science object Z that can be viewed under different context perspectives. By a
definition of Zimmermann et. al., “when the contexts of two entities overlap and part
of the context information become similar and shared,” a shared context emerges [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>Embedded information has been well preserved and curated in research data
repositories and in Libraries, Archives and Museums (LAM) databases, but has not been
explored for their potentials in enriching each other’s contexts. For instance, cultural
objects are mostly preserved with metadata information, but part of the data may come
from the outputs of research projects. As for research data, the interpretation of domain
knowledge is professionally established from scholarly publications which are
comprehend by articles’ textual descriptions, or by supportive evidences like associated
publications (i.e. data and code), and these supportive evidence may come from cultural
objects curated in LAM collections. Thus, is there a shared context between these two
domains that can serve for a common understanding? And, how can a shared context
between these two help us enrich contextual information and make our data better? In
practice, will linking data from scholarly publications to metadata-rich LAM
collections foster contextualizing research outputs? Will linking data from LAM collections
to research publications increase the reuse and the remix of cultural heritage for a broad
range of disciplines? And, in particular, what kinds of relations exist, or need to be
established for a shared context? Finally, how these relations can be represented?</p>
      <p>
        However, citations need context [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], linked data is not enough only for research data
[
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], and the lack of theory and “object-rich but resource-poor” problems are identified
in cultural heritage domains [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. Therefore, above mentioned developments with these
problems have motivated us to the design of a contextual framework to disclose context
by a systematic approach in the next section.
2.
      </p>
    </sec>
    <sec id="sec-2">
      <title>A Contextual Framework for a Shared Context</title>
      <p>
        For modeling and representing contextual linking, we follow the operational definition
of [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] for determining the design space of context models. The five essential contexts
are time, location, individuality, activity and relations. And in specific to model the
activity, we further adopt Courtright’s theoretical concept of actors-in-context which
combines a relational view on activities of users, information systems and information
1 http://www.codata.org/task-groups/data-citation-standards-and-practices
2 https://rd-alliance.org/
3 https://www.force11.org/
4 Linked Open Data in Libraries, Archives, and Museums (LODLAM): http://lodlam.net/
5 http://www.oclc.org/data.en.html
6 https://github.com/blog/1840-improving-github-for-science
existence that context not only shapes action but is also shaped by it [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. Our
framework consists three major parts: (1) three contexts relate actors’ levels with associated
activities as Reusing, Publication and Curation7. (2) a
Representation-Preservation-Interpretation setting is established. (3) Nine contextual elements are derived and
extended from a contextual study on cultural heritage objects, and are further adjusted to
accommodate particular settings. Table 1 provides a summary of this contextual
framework, and the following offers theoretical backgrounds in details.
From session one, we realize the importance of modeling publication and reusing
contexts. However, Contextualizing only for these two activities is not enough since this
framework is also to assist system designers, developers and curators for their practices.
Thus a third Curation level is added for two more reasons: (1) Zimmermann et.al [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]
defines activity context as a context which decides to its current needs and covers
current and future activities. In other words, curation activity not only determines current
needs of curators but also future activities like publication or reusing. Similarly, the
publication activity serves publication-now and reusing-in-the-future purposes. (2) As
[
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] indicates that technology has a dual role in context, technology variations depend
on other contextual elements while at the same time technologies influence information
practices. In other words, a shared context between Reusing and Publication emerges
as a technical dimension for the Curation. In short, three activity levels are situated in
a multiple, overlapping, and dynamic context because Publication involves both
publication and curation activities, and Reusing involves reusing, publication and curation,
while Curation cannot exist without considerations of two other activity contexts.
(2) A perspective setting: Representation-Preservation-Interpretation.
In considering theoretical issues for a contextual framework, a
Representation-Preservation-Interpretation setting is established from Charles Sanders Peirce (1839–1914)’s
triadic sign theory: {Representation, Object, Interpretant} that a sign constituents three
basic parts with a relation that a something, Representation, brings its Interpretant sign
determined or created by it, into the same sort of correspondence with its Object, as that
7 Three activity contexts are italics with the first word capitalized.
the something (Representation) stands to the Object [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. Here, we define a contextual
setting as a sign with the triadic relation [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]:
 The Representation is a representation of the activity context setting itself, and is
the form that the setting takes. For instance, in Reusing, the Representation is the
application cases employed to determine a resource to be used by oneself or others.
 The Object is the entity to which the context setting points, refers or applies. In this
study, it is the specific preservation object that the authors, users, and curators refer
to. The original “Object” has been adjusted to the object preservation for
“Preservation” to describe associated activities.
 The Interpretant of a contextual setting is the Interpretation that is made of the
setting. In this study, the interpretation is taken from the view of [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] on Relations
Context that context information captures the relations an entity has recognized to
the others.
      </p>
      <p>
        The triadic sign theory has been empirically applied as an analytical framework for
dynamic and complex composition such as for social tagging [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] and semantic web
[
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. Furthermore, according to Tim Berners-Lee's own words, the Semantic Web is "a
fervent desire to implement some ideas of Charles S. Peirce"8. Thus, we use this triadic
relation that has also influenced Resources Description Framework (RDF) data model
(Subject-Predicate-Object) to some degrees, as a basis to construct the context model
as a triadic setting: Representation-Preservation-Interpretation. In addition, [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] argues
that contextual elements must be explicitly linked to particular information practices,
and the variability must be distinguished among actors and contexts. Thus, contextual
elements need to be constructed within the Representation-Preservation-Interpretation
setting and three dynamic activity contexts: Reusing, Publication and Curation. Next,
we will move to disclose what contextual elements are constructed.
(3) Nine contextual elements: eight dimensions about context and its role are
suggested by Beaudoin as technical, utilization, physical, intangible, curatorial,
authentication, authorization, and intellectual [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. The eight dimensions were generated for
digital preservation of cultural heritage. For more context needs in this study, we adjust
and extend technical, curatorial and intellectual dimensions to identification,
application, classification and ontological relations. Table 1 is summarizes this framework.
Details of these nine contextual elements associated with specific contexts and settings
are introduced by using cases to illustrate how they can be applied in session 49. Thus,
we brief here four new contextual elements that are different from Beaudoin’s work.
      </p>
      <p>(I) Identification is a representation for disclosing the Intangibleness of the
physical objects. In this framework, it is a publication-level representation for disclosing the
existence of article, data, or code that can be identified for publication. It is restricted
8 http://www.w3.org/DesignIssues/CG.html
9 See more possible scenarios for different contents
http://guava.iis.sinica.edu.tw/r4r/examples/possible_scenarios_for_different_contexts
by the Curation, and can be potentially utilized for the Reusing. For instance, when
publishing linked data, it requires using URIs as names for things, the URIs are curated
in restrict rules of the curation activity, and can be potential utilized for Reusing.</p>
      <p>(II) Application is a specific result or application cases like remixing or reusing, a
representation for determining the Utilization of the presence of Authorization objects
like digital policy or license that concerns the needs of users for Reusing.</p>
      <p>(III) Classification is a classifying representation brings relational interpretations
for Authentication elements (ex. metadata or provenance). It is a curatorial-level
representation since it is the main task for curators to curate metadata about datasets. And
metadata is interpreted by domain ontologies in the Publication, but interpreted by
domain-independent ontologies in the Curation. For instance, the catalogue metadata of
European Union Open Data is available as linked data10, and uses the Data Catalog
Vocabulary (DCAT) 11 to classify seven basic classes for catalogue metadata12.</p>
      <p>
        (IV) Ontological Relations is an interpretation for Classification that represents
authentication elements such as metadata or provenance at the curatorial-level. Since
contexts are changeable, we extend Beaudoin’s intellectual dimension [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] and focus
on the construction of a fundamental relationships for dynamic contexts and a
domainindependent ontology formation. For instance, the Fedora relationship ontology13 is
used to model partial and provenance relations that can be shared across in its Fedora
Ontology. Similarly, R4R ontology is designed for such functions.
      </p>
      <p>
        To sum up, in Publication, an Identification name (ex. URI) is published and brings the
interpretation by the network linkages of Intangibleness (ex. a domain vocabulary or
citation), which determined or created by it, into the same sort of relation to the
Physicalness (ex. data), as that in which the Identification stands to the Physicalness.
Similarly, the rules are applied for Reusing: Application-Authorization-Utilization as well
as for Curation: the Classification-Authentication-Ontological Relations. In practice,
this framework is a conceptual tool to help us establish relations if we want to use the
shared context for modeling Reusing and Publication. Since these two contexts share
Curation, according to [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] we should start to establish relations between these two by
examining what major preservation objects can be found in the Curation context.
3.
      </p>
    </sec>
    <sec id="sec-3">
      <title>Relations for Reusing (R4R) Ontology</title>
      <p>
        For a light-weight design purpose, R4R consists 15 terms only: 7 classes and 7
properties plus one exceptional property Cites. Figure 1 illustrates the conceptual model of
10 http://open-data.europa.eu/en/linked-data
11 http://www.w3.org/TR/vocab-dcat/
12 Catalog, Catalog record, Dataset, Distribution, Concept scheme, Concept, and Organization/Person
13 http://www.fedora.info/definitions/1/0/fedora-relsext-ontology.rdfs
the R4R, and a full specification can be accessed online14. In the following, we will
brief the major structure, and discuss our modeling decisions. Two crucial components
as individual class concepts are identified in this model, namely, Reusing Related
Object (RRObject) and Reusing Related Policy (RRPolicy). RRObject distinguishes
R4R’s basic components of described targets, creating the unique identification of the
related objects, from RRPolicy being packaged for more specific combinations of
provenance and license. The primary consideration for designing R4R is that it should on
the one hand being capable of describing the combination of RRObject and RRPolicy,
while on the other hand still allowing to just represent RRObject alone without
packaging the RRPolicy. This is a decision made from reasons:
(1)Provenance and license concerns are not fully taken and implemented in existing
practices, or have been curated as metadata in local curation that are not accessible or
downloadable. Thus we use hasProvenance and hasLicense for relating local curation
or for sharing publications. For Reusing, the context transitions occur, and according to
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], context attributes will change from one context entering another, thus Provenance
or License, or both can be packaged with RRObject for reusing purposes. For such
using of the relation, isPackagedWith, RRObject (article/data/code) and RRPolicy
(provenance/license) are reachable and accessible for changing the original Publication
and Curation contexts to a shift of the Reusing context.
(2) isPartOf and isCitedBy/Cites like hasProvenance and hasLicense that can relate
internal relations within subclasses of RRObject (article/data/code). Meanwhile, these
two relations can also be used for describing external relations. isPartOf describes
partial relationships with temporal and spatial constraints. A isPartOf B only if A and B
share the same time and location. This design helps to clarify relations of collections
and items since temporal and spatial attributes of collections constrain item-level
attributes. It also helps semantic publishing that one partial paragraph, session, chapter
or even a sentence can be represented as an RRObject for article enrichments.
14 http://guava.iis.sinica.edu.tw/r4r
(3) isCitedBy is distinguished from Cites for temporal constraints. Normally, when A
isCitedBy B implies the publication time of A occurs before B. However, it is also
possible that A and B are mutual-cited at the same time. For instance, two articles
publishing in the same journal and citing each other are common research practices.
(4) Relations between Data and Code in current practice are sometimes isPartOf,
sometimes isCitedBy, since dataset and code are quite often published together as Data.
When Data and Code share the same temporal and spatial attributes, and data modelers
wish to distinguish the two, it can be described as Code isPartOf Data.
(5) Citation is one of the most important traces to link contextual information from
the original to many interpretations of the reused. In Publication, authors create their
works by citing references as evidences/interpretations. In Reusing, afore mentioned
publications become other’s evidences/interpretations. As indicated by [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], when the
activity (like citation) predominantly determines the relevance of context elements in
specific situations, citation thus becomes one of our major interpretations for relations.
(6)Packaging relation in R4R is a relation between RRObject and RRPolicy.
isPackagedWith is utilized only when Reusing occurs. It is a design specific to differentiate
interpretations of metadata/provenance and license in different contexts. In Publication,
metadata/provenance are curated for local preservation, and may be interpreted by
domain vocabularies as a reflection of the author. In Reusing, metadata/provenance, and
license are necessary components for Authorization and Authentication, therefore
RRPolicy needs to be packaged to be able to be reused or remixed.
      </p>
      <p>In sum, the design concept of R4R components are more toward modularity, in which
components can be separated and recombined in different contexts, at different time.
This is important because R4R wish to describe the future relations which will grow
and evolve like future citations, provenance changed, or license policy changed.
So far we have dealt only with the contextual framework and the R4R ontology that
reveal how context shared or changed can be modeled through establishing and
exploring relations. But how a shared context between different domains like research
publications and LAM collections help us enrich contextual information and make our data
better? In the fowling, we will use R4R and different contexts to represent an example
of interlinked data between research publications and a cultural object curated in LAM.</p>
    </sec>
    <sec id="sec-4">
      <title>4. A Use Case from the Digital Archives Taiwan</title>
      <p>Digital Archives Taiwan (digitalarchives.tw) consists collections of five million
digitized cultural objects contributed by the largest memory institutions in Taiwan, and
spanning various domains (history, art, biodiversity, geology, geography, ethnology,
anthropology, etc.). The collection of Digital Archives Taiwan curated both in item
and collection levels is indexed and catalogued through the Union Catalog
(catalog.digitalarchives.tw) for data aggregation, representation, and citation. Figures
2 shows one item15 that is published as a form which is similar to “data papers” (dataset
descriptions for scientific research) or “nanopublications” (small units of publishable
information with unique identifiers) 16. Each item page constitutes: (1) The collection
object and its basic information (Scientific Names and Vernacular Name); (2) Link to
the original database; (3) Metadata Description; (4) Contact Information for Licensing;
(5) Citation Information (bibliography and the unique URL). In addition, this item has
an archive record ID, S010384, and it will be discussed in following sessions several
times, thus we use daT(S010384) as a substitute name for this collection item17.</p>
      <p>
        The daT(S010384) has the Union Catalog metadata which uses Dublin Core for
curation schema. The item also has a citation spec18 and the license information is
expressed by a contact information. The following shows how we use R4R in Turtle
syntax to model this cultural object being curated and published in the Union Catalog. For
Curation, daT(S010384) is being classified as RRObject (Classification) using R4R
:daT_Collection
a r4r:data, dc:Collection ;
dc:publisher "Digital Archives Taiwan";
dc:provenance:daT_Metadata .
:t3
a time:Instant ;
time:inXSDDateTime "2012-01-01" .
15 http://catalog.digitalarchives.tw/item/00/61/e8/e2.html
16 http://nanopub.org/wordpress/
17All figures presented in this paper are published with high-resolution gif files in the reference [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ].
18 http://digitalarchive-taiwan.blogspot.tw/2012/02/blog-post.html
ontology (Interpretation) to relate its metadata description (Authentication). For
Publication, daT(S010384) is published using an R4R Identification that brings the
Interpretation of Dublin Core and citation relations to it (Intangibleness). For a Shared Context,
the relation is established by modeling daT(S010384) as subclass of RRObject (in
Curation level ) to be r4r:Data (Physicalness in Publication level), and using hasTime and
locateAt to relate the Representation of two contexts, and prepare for the possible future
Reusing emerging context.
      </p>
      <p>
        A simple Reusing is presented by a citation relation. The daT(S010384) has been
cited in a science articles’ material and method session19. For a simple citation
modeling, we can add this citation in local metadata using isCitedBy relation. The science
paper may be benefited from this citation since the daT(S010384) is also curated under
a catalog structure of domain knowledge interpretation from the international scientific
standard of the biological classification: Domain/Kingdom/Phylum/Class/Order/..., as
well as a hierarchy which includes the project information about the source organization
and project details20. For a complex Reusing, these rich domain knowledge can be
packaged for more application uses. For instance, we assume there is a digital plant atlas of
natural museum in Europe, called PA. In their plant atlas, lacking of digital collection
in Asia is one of major problems. PA finds that a plant specimen collection in Digital
Archives Taiwan is proper for their uses. The first problem PA will encounter is the
authorization of each digital item. The second problem is that they have to validate each
item’s collection and digital process for data quality. The third problem is that even
each item in Digital Archives Taiwan is well documented and accessible through
hyperlinks to original data repositories, PA does not want to manually click through all
the links. Thus, if a machine readable and executable license and provenance are
provided, not only PA but any other users can easily select, reuse or remix this digital
collection. Taking daT(S010384) for example, the item can be modeled by provenance
information using PROV-O ontology21. An example of this is described in [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ].
In short, when provenance or license is not ready to be packaged or not for releasing
openly, we can use RRObject individually by publishing their unique identifications
embedded with domain knowledge or citation interpretations through hasProvenance
and isCitedBy to relate provenance information at the metadata level, and citation
relations between article, data and code internally or externally. Once the RRObject is
packaged with RRPolicy as R4R(daT,S010384), it is ready for other resources to
connect and reuse by policy-aware tools for license like Semantic Clipboard [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], and by
capturing provenance through ontology use like PROV-O at multiple layers [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. It can
also be easily used and relate to many forms of resources and from different domains.
It can also be related to similar collections of other libraries, archives and museums;
reused and recreated by other works. Or it can be embed in the package format of digital
publishing like EPUB for E-books (see Figure 3).
      </p>
    </sec>
    <sec id="sec-5">
      <title>5. Related Works</title>
      <p>
        Although context modelling has been discussed in Artificial Intelligence literatures, the
use of mathematical theory and logical formalization is beyond the scope of this paper.
Instead, relations modeling that tries to classify linking structures in an attempt to make
complicated relationships easier for semantic representation is most related to our work.
For instance, the Fedora Relationship Ontology has been developed for representing
object-to-object relationships in the Fedora architecture for complex object modelling
[
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]. And another useful example of relation representations supporting domain
concepts interlinked by logical constrains is provided by the case of OBO Relation
Ontology22 in biomedical and life science. This ontology later influences the design of the
Artifact Relationship Ontology (ARO) that has been designed specifically for
comparing museum objects [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ].
      </p>
      <p>
        In addition, the Literature Object Re‐use and Exchange (LORE) relationship
ontology, a simplified version of IFLA FRBR is presented in [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ] to facilitate reuse and
exchange LAM collections for research purpose. Relations like authorship relations
(i.e. creators, agents, or organizations), object attribute relations (metadata
descriptions), or preservation and derivation relations are major concerns for LORE, and that
results in more than one hundred relations are defined. Although many relation
concepts of LORE are similar to R4R, it is taken from a bibliographic perspective. LORE
uses its own definitions to represent similar and provenance information, while R4R
recommend users to reuse SKOS23, which can reference other concepts using a variety
of semantic relationships, as well as PROV-O in the afore mentioned example. Most
importantly, modeling compound and complex objects as employed in Fedora,
Research Objects [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], and LORE alike is not the aim of R4R that takes the Shared
Context for a design space, and aims to meet data publication, citation, and reusing for Open
22 http://www.obofoundry.org/ro/
23 http://www.w3.org/TR/2009/REC-skos-reference-20090818/
Science that needs to distinguish reusing, publication and curation for different
contextual constructs. Table 2 is a summary of above mentioned relation ontologies, a full
view of comparison can be accessed in [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ].
      </p>
      <p>Time
Domain
Concept
Relation
Location
Partial
Similar
Provenance
Citation
Bundle
License
Compare
Definition</p>
    </sec>
    <sec id="sec-6">
      <title>Conclusion</title>
      <p>As responding to recent developments (Session 1) that have challenged research data,
archival and cultural heritage communities for a contextual framework to support a
dynamic and shared context environment, we have proposed a framework (Session 2),
and to the establishment of an ontology, Relations for Reusing (R4R), that can facilitate
the representation of contextual links between resources in diverse contexts (Section
3). In section 4, we use R4R for representing different contexts that can enhance
semantic relationships of research publications and cultural objects when both are
contextually linked. Section 5, related works are discussed and presented with a
comparison on five existing relation ontologies that distinguishes the R4R from previous works.</p>
      <p>The advantage of designing a new conceptual model to describe relations in a shared
context is to ensure articles, datasets, software codes, provenance and license
information can be treated as first-class contextual objects. At the same time, the
modulelike design of RRObject and RRPolicy can be practiced in isolation, and the unifying
representation of their relations is semantically enough but not so structurally
heavyweighted that curators or researchers find it difficult to apply.</p>
      <p>
        In sum, the daT(S010384) is a digital object with rich metadata descriptions being
curated in Curation context. It is published as a cultural object Y, with unique
identification, and being cited as a science object Z, interpreted by the citation relation for more
professional interpretations. At the same time, the citing research can be benefited from
the implicit information embedded in the institution’s cataloging vocabularies for more
domain knowledge. Through the exploration of the Shared Context and R4R
representation, the daT(S010384) now is capable to move from its traditional role and to “act as
a citation of active knowledge” indicated in [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]. Creating knowledge out of interlinked
data [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ] is thus one step forward by packaging provenance and license for a
policyaware Reusing context. As a result, when data sharing needs not to remove the data's
initial context but embedded in a shared context, the difficulty to interpret the reused
data [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ] may be expected positively through the use of the contextual framework and
R4R ontology proposed in this study.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Zimmermann</surname>
            ,
            <given-names>Andreas</given-names>
            , Andreas
          </string-name>
          <string-name>
            <surname>Lorenz</surname>
            , and
            <given-names>Reinhard</given-names>
          </string-name>
          <string-name>
            <surname>Oppermann</surname>
          </string-name>
          .
          <article-title>An operational definition of context. Modeling and using context (</article-title>
          <year>2007</year>
          ):
          <fpage>558</fpage>
          -
          <lpage>571</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Krafft</surname>
          </string-name>
          ,
          <string-name>
            <surname>Dean</surname>
            <given-names>B.</given-names>
          </string-name>
          , et al.
          <article-title>Vivo: Enabling national networking of scientists</article-title>
          .
          <source>Proceedings of the Web Science Conference</source>
          . Vol.
          <year>2010</year>
          .
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Keßler</surname>
            , Carsten, Mathieu d'Aquin,
            <given-names>and Stefan</given-names>
          </string-name>
          <string-name>
            <surname>Dietze</surname>
          </string-name>
          .
          <article-title>Linked Data for science and education</article-title>
          .
          <source>Semantic Web 4.1</source>
          (
          <year>2013</year>
          ):
          <fpage>1</fpage>
          -
          <lpage>2</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Haslhofer</surname>
          </string-name>
          , Bernhard, and
          <article-title>Antoine Isaac. data. europeana. eu: The europeana linked open data pilot</article-title>
          .
          <source>International Conference on Dublin Core and Metadata Applications</source>
          .
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Malmsten</surname>
          </string-name>
          , Martin.
          <article-title>Making a library catalogue part of the semantic web</article-title>
          .
          <source>Proceedings of the 2008 International Conference on Dublin Core and Metadata Applications</source>
          (
          <year>2008</year>
          ):
          <fpage>146</fpage>
          -
          <lpage>152</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Ford</surname>
            ,
            <given-names>Kevin.</given-names>
          </string-name>
          <article-title>LC Classification as linked data</article-title>
          .
          <source>Italian Journal of Library and information science</source>
          ,
          <volume>4</volume>
          .1 (
          <year>2013</year>
          ):
          <fpage>161</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Shotton</surname>
            ,
            <given-names>David.</given-names>
          </string-name>
          <article-title>Semantic publishing: the coming revolution in scientific journal publishing</article-title>
          .
          <source>Learned Publishing 22.2</source>
          (
          <year>2009</year>
          ):
          <fpage>85</fpage>
          -
          <lpage>94</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Keivanloo</surname>
          </string-name>
          ,
          <string-name>
            <surname>Iman</surname>
          </string-name>
          , et al.
          <article-title>Towards sharing source code facts using linked data</article-title>
          .
          <source>Proceedings of the 3rd International Workshop on Search-Driven Development: Users</source>
          , Infrastructure, Tools, and
          <string-name>
            <surname>Evaluation</surname>
          </string-name>
          . ACM,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Wendl</surname>
          </string-name>
          , Michael C.
          <article-title>H-index: however ranked, citations need context</article-title>
          .
          <source>Nature</source>
          <volume>449</volume>
          .7161 (
          <year>2007</year>
          ):
          <fpage>403</fpage>
          -
          <lpage>403</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Bechhofer</surname>
          </string-name>
          ,
          <string-name>
            <surname>Sean</surname>
          </string-name>
          , et al.
          <article-title>Why linked data is not enough for scientists</article-title>
          .
          <source>Future Generation Computer Systems 29.2</source>
          (
          <year>2013</year>
          ):
          <fpage>599</fpage>
          -
          <lpage>611</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Skinner</surname>
            ,
            <given-names>Julia.</given-names>
          </string-name>
          <article-title>Metadata in Archival and Cultural Heritage Settings: A Review of the Literature</article-title>
          .
          <source>Journal of Library Metadata 14.1</source>
          (
          <year>2014</year>
          ):
          <fpage>52</fpage>
          -
          <lpage>68</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Courtright</surname>
          </string-name>
          , Christina. Context in information behavior research.
          <source>Annual review of information science and technology 41.1</source>
          (
          <year>2007</year>
          ):
          <fpage>273</fpage>
          -
          <lpage>306</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Peirce</surname>
          </string-name>
          , Charles Sanders. “
          <article-title>Elements of Logic”, Chapter 2: Division of Signs</article-title>
          . In: C. Hartshorne and P. Weiss (eds),
          <source>Collected Papers of Charles Sanders Peirce (2)</source>
          (Thoemmes Press, Bristol,
          <year>1998</year>
          ) :
          <fpage>134</fpage>
          -
          <lpage>272</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Huang</surname>
          </string-name>
          ,
          <string-name>
            <surname>Andrea</surname>
          </string-name>
          Wei-Ching, and
          <string-name>
            <surname>Tyng-Ruey Chuang</surname>
          </string-name>
          .
          <article-title>Social tagging, online communication, and Peircean semiotics: a conceptual framework</article-title>
          .
          <source>Journal of Information Science 35.3</source>
          (
          <year>2009</year>
          ):
          <fpage>340</fpage>
          -
          <lpage>357</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Legg</surname>
          </string-name>
          , Catherine. Peirce, meaning, and
          <article-title>the Semantic Web</article-title>
          .
          <source>Semiotica</source>
          <year>2013</year>
          .
          <volume>193</volume>
          (
          <year>2013</year>
          ):
          <fpage>119</fpage>
          -
          <lpage>143</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Beaudoin</surname>
          </string-name>
          , Joan E. Context and
          <article-title>its role in the digital preservation of cultural objects</article-title>
          .
          <source>D-Lib Magazine 18.11</source>
          (
          <year>2012</year>
          ):
          <fpage>1</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Seneviratne</surname>
            , Oshani,
            <given-names>Lalana</given-names>
          </string-name>
          <string-name>
            <surname>Kagal</surname>
          </string-name>
          , and
          <string-name>
            <surname>Tim</surname>
          </string-name>
          Berners-Lee.
          <article-title>Policy-Aware Content Reuse on the Web</article-title>
          .
          <source>The Semantic Web - ISWC</source>
          <year>2009</year>
          (
          <year>2009</year>
          ):
          <fpage>553</fpage>
          -
          <lpage>568</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Carata</surname>
          </string-name>
          ,
          <string-name>
            <surname>Lucian</surname>
          </string-name>
          , et al.
          <article-title>A primer on provenance</article-title>
          .
          <source>Communications of the ACM 57.5</source>
          (
          <year>2014</year>
          ):
          <fpage>52</fpage>
          -
          <lpage>60</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Lagoze</surname>
          </string-name>
          ,
          <string-name>
            <surname>Carl</surname>
          </string-name>
          , et al.
          <article-title>Fedora: an architecture for complex objects and their relationships</article-title>
          .
          <source>International Journal on Digital Libraries 6.2</source>
          (
          <year>2006</year>
          ):
          <fpage>124</fpage>
          -
          <lpage>138</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Yu</surname>
          </string-name>
          ,
          <string-name>
            <surname>Chih-Hao</surname>
            , and
            <given-names>Jane</given-names>
          </string-name>
          <string-name>
            <surname>Hunter</surname>
          </string-name>
          .
          <article-title>Documenting and sharing comparative analyses of 3D digital museum artifacts through semantic web annotations</article-title>
          .
          <source>Journal on Computing and Cultural Heritage (JOCCH) 6</source>
          .4 (
          <year>2013</year>
          ):
          <fpage>18</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Gerber</surname>
            , Anna, and
            <given-names>Jane</given-names>
          </string-name>
          <string-name>
            <surname>Hunter</surname>
          </string-name>
          .
          <article-title>Authoring, editing and visualizing compound objects for literary scholarship</article-title>
          .
          <source>Journal of Digital Information 11.1</source>
          (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Srinivasan</surname>
          </string-name>
          ,
          <string-name>
            <surname>Ramesh</surname>
          </string-name>
          , et al.
          <article-title>Digital museums and diverse cultural knowledges: Moving past the traditional catalog</article-title>
          .
          <source>The Information Society 25.4</source>
          (
          <year>2009</year>
          ):
          <fpage>265</fpage>
          -
          <lpage>278</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Auer</surname>
            , Sören, and
            <given-names>Jens</given-names>
          </string-name>
          <string-name>
            <surname>Lehmann</surname>
          </string-name>
          .
          <article-title>Creating knowledge out of interlinked data</article-title>
          .
          <source>Semantic Web 1.1</source>
          (
          <year>2010</year>
          ):
          <fpage>97</fpage>
          -
          <lpage>104</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Borgman</surname>
          </string-name>
          , Christine L.
          <article-title>The conundrum of sharing research data</article-title>
          .
          <source>Journal of the American Society for Information Science and Technology 63.6</source>
          (
          <year>2012</year>
          ):
          <fpage>1059</fpage>
          -
          <lpage>1078</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <article-title>Associated data publication can be accessed</article-title>
          at http://guava.iis.sinica.edu.tw/r4r/examples
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>