<?xml version="1.0" encoding="UTF-8"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
  <teiHeader>
    <fileDesc>
      <titleStmt>
        <title>“The research is happening in the text fields” – Are Linked Open Data and Art History a good match?</title>
        <author>Giacomo Nanni</author>
        <author>Linda Freyberg</author>
        <author>Sabine de Günther</author>
        <author>Marian Dörk</author>
      </titleStmt>
      <publicationStmt>
        <p>Tag layer of the DHSS Meta-Tagging Project. The article text is reproduced from the
           staged copy named in sourceDesc and is not altered; the tags are held separately in
           standOff so that overlapping and nested spans are preserved.</p>
      </publicationStmt>
      <sourceDesc>
        <bibl>
          <title>“The research is happening in the text fields” – Are Linked Open Data and Art History a good match?</title>
          <date>2023</date>
          <publisher>Digital Humanities 2023 (DH2023), Graz</publisher>
          <idno type="DOI">10.5281/zenodo.8107731</idno>
          
          <idno type="record">lod2023-art-history</idno>
          <note type="staged-file">lod2023-art-history.txt, the project's staged copy</note>
          <note type="text-sha1">73b837e3f6705fdd5fcda7372e2d3041aa5f546b</note>
          <note type="rights">cc-by</note>
        </bibl>
      </sourceDesc>
    </fileDesc>
    <profileDesc>
      <textClass><keywords><term>art-history</term></keywords></textClass>
      <particDesc>
        <person xml:id="paper"><p>the paper's own words</p></person>
        <person xml:id="tagger"><p>the tag layer; a sentence written by the tagger about the
          paper, always anchored to a quotation but not itself a quotation</p></person>
      </particDesc>
    </profileDesc>
    <revisionDesc>
      <change when="2026-10-06"
              who="build_paper_edition.py">44 spans located by searching the stored text for the quote's exact words, allowing any whitespace between them</change>
    </revisionDesc>
  </teiHeader>
  <standOff>
    <spanGrp type="tags">
      <span xml:id="t0" from="#a7" to="#a8" type="object_of_study" ana="#object_of_study" resp="#paper">Where the boundary falls between what an art-historical research project can express as Linked Open Data and what it must leave as prose.</span>
      <span xml:id="t1" from="#a9" to="#a10" type="research_question" ana="#research_question" resp="#paper">Structured vocabularies buy accuracy and queryability - so what is lost when the reflexive, contextual part of humanities research is forced into them?</span>
      <span xml:id="t2" from="#a11" to="#a12" type="contribution" ana="#contribution" resp="#paper">Argues that only the quantitative, queryable part of art-historical research is worth modelling as triples, and bridges the rest to it through visual interfaces rather than forcing it into ontologies.</span>
      <span xml:id="t3" from="#a34" to="#a35" type="claim_type" ana="#claim_type" resp="#paper">critique</span>
      <span xml:id="t4" from="#a7" to="#a8" type="phenomenon" ana="#phenomenon" resp="#paper">linked open data modelling in art history</span>
      <span xml:id="t5" from="#a5" to="#a6" type="method" ana="#method" resp="#paper">practice-report<term>practice-report</term></span>
      <span xml:id="t6" from="#a28" to="#a29" type="mechanisms" ana="#mechanisms[0]" resp="#tagger" cert="1.0">mechanisms<term>an ontology can never close: no cultural artefact is finally contextualisable, and the vocabularies are uneven across subtopics</term></span>
      <span xml:id="t7" from="#a30" to="#a31" type="mechanisms" ana="#mechanisms[1]" resp="#tagger" cert="1.0">mechanisms<term>the target moves: meanings shift over the life of the project doing the modelling</term></span>
      <span xml:id="t8" from="#a26" to="#a27" type="mechanisms" ana="#mechanisms[2]" resp="#tagger" cert="1.0">mechanisms<term>the cost of manual tagging is what forces institutions to publish shallow metadata, which then constrains what anyone can ask of the data</term></span>
      <span xml:id="t9" from="#a20" to="#a21" type="mechanisms" ana="#mechanisms[3]" resp="#tagger" cert="1.0">mechanisms<term>deep modelling is not durable either - the British Museum modelled its whole collection in CIDOC CRM and then could not keep it accessible</term></span>
      <span xml:id="t10" from="#a38" to="#a39" type="limitations" ana="#limitations[0]" resp="#tagger" cert="0.9">One project, one discipline: the argument is illustrated by Restaging Fashion rather than tested across cases.<note>what this limits: the generality of the argument: it is illustrated by the Restaging Fashion project rather than tested across cases</note></span>
      <span xml:id="t11" from="#a42" to="#a43" type="limitations" ana="#limitations[1]" resp="#tagger" cert="0.8">The boundary it proposes - quantitative to triples, reflexive to interfaces - is asserted rather than operationalised; nothing says where a given sentence falls.<note>what this limits: the proposed boundary itself: QUANTITATIVE INFORMATION ... WHICH CAN BE QUERIED AND EXPRESSED STATISTICALLY, ARE WORTH TO BE MODELED IN TRIPLE STRUCTURES - asserted, not operationalised</note></span>
      <span xml:id="t12" from="#a1" to="#a2" type="transfers" ana="#transfers[0]" resp="#tagger" cert="0.9">Linked Data, reference ontologies and authority files, applied to art-historical research and found to fit only part of it</span>
      <span xml:id="t13" from="#a22" to="#a23" type="concepts" ana="#concepts[0]" resp="#paper">linked open data<term>linked open data</term></span>
      <span xml:id="t14" from="#a14" to="#a15" type="concepts" ana="#concepts[1]" resp="#paper">CIDOC CRM<term>CIDOC CRM</term></span>
      <span xml:id="t15" from="#a7" to="#a8" type="concepts" ana="#concepts[5]" resp="#paper" cert="1.0">free-form text<term>free-form text</term></span>
      <span xml:id="t16" from="#a11" to="#a12" type="concepts" ana="#concepts[6]" resp="#paper" cert="1.0">information visualization<term>information visualization</term></span>
      <span xml:id="t17" from="#a28" to="#a29" type="concepts" ana="#concepts[7]" resp="#paper" cert="1.0">ontologies<term>ontologies</term></span>
      <span xml:id="t18" from="#a26" to="#a27" type="concepts" ana="#concepts[8]" resp="#paper" cert="1.0">metadata<term>metadata</term></span>
      <span xml:id="t19" from="#a42" to="#a43" type="concepts" ana="#concepts[9]" resp="#paper" cert="1.0">triple structures<term>triple structures</term></span>
      <span xml:id="t20" from="#a34" to="#a35" type="senses" ana="#senses[0]" resp="#tagger" cert="1.0">representation - as machine-readable structure, whose point is that a formal query can be run over it</span>
      <span xml:id="t21" from="#a36" to="#a37" type="senses" ana="#senses[1]" resp="#tagger" cert="1.0">representation - as something another researcher can read and understand, which the paper argues needs no formalisation at all</span>
      <span xml:id="t22" from="#a32" to="#a33" type="senses" ana="#senses[2]" resp="#tagger" cert="1.0">the unrepresentable - material the paper holds cannot be captured by either, quoting Galloway</span>
      <span xml:id="t23" from="#a34" to="#a35" type="alternatives" ana="#alternatives.claim_type" resp="#tagger">claim_type: critique<note>a second reading reaching the same value. Recorded: critique — note: a second reading reaching the same value from a different sentence. Not applied - a person decides.</note></span>
      <span xml:id="t24" from="#a5" to="#a6" type="alternatives" ana="#alternatives.method" resp="#tagger">method: conceptual-analysis<note>a second reading DIFFERING from the recorded value. Recorded: practice-report — note: a second reading, verbatim-verified, disagreeing with the value on the record. Not applied - a person decides.</note></span>
      <span xml:id="t25" from="#a13" to="#a14" type="alternatives" ana="#alternatives.phenomenon" resp="#tagger">phenomenon: the trade-off between semantic formalisation and the expressiveness of humanities research writing<note>a second reading DIFFERING from the recorded value. Recorded: linked open data modelling in art history — note: a second reading, verbatim-verified, disagreeing with the value on the record. Not applied - a person decides.</note></span>
      <span xml:id="t26" from="#a32" to="#a33" type="claim_relations" ana="#claim_relations[0]" resp="#tagger">builds-on → Galloway (2011: 91) on the unrepresentable</span>
      <span xml:id="t27" from="#a16" to="#a17" type="claim_relations" ana="#claim_relations[1]" resp="#tagger">builds-on → Daquino et al. (2022) on institutional uptake of LOD-native systems</span>
      <span xml:id="t28" from="#a22" to="#a23" type="claim_relations" ana="#claim_relations[2]" resp="#tagger" cert="1.0">builds-on → Berners-Lee (2006) on Linked Data</span>
      <span xml:id="t29" from="#a34" to="#a35" type="claim_relations" ana="#claim_relations[3]" resp="#tagger" cert="0.9">contradicts → the programme of modelling cultural heritage research exhaustively in formal ontologies<note>differs in: THE AXIS IS WHICH PART OF THE WORK IS BEING MODELLED. &#x27;IN TERMS OF REPRESENTING THE RESEARCH PROCESS IT IS NOT WORTH MAKING THIS PART MACHINE-READABLE as a basis for formal queries.&#x27; The exhaustive-formalisation programme is contradicted for ONE COMPONENT and left standing for the rest - which is exactly the qualification a bare &#x27;contradicts&#x27; deletes.</note></span>
      <span xml:id="t30" from="#a7" to="#a8" type="concept_edges" ana="#concept_edges[0]" resp="#tagger">Linked Open Data —contrasted-with→ free-form text<note>strength of the relation: 1
Audit 2026-09-28: DOUBTFUL - read against its full span and kept, but the span poses the choice between LOD and free-form text as a question; contrasted-with is loose.</note><term>Linked Open Data</term><term>free-form text</term></span>
      <span xml:id="t31" from="#a14" to="#a15" type="concept_edges" ana="#concept_edges[1]" resp="#tagger">CIDOC CRM —is-a→ ontologies<note>strength of the relation: 1</note><term>CIDOC CRM</term><term>ontologies</term></span>
      <span xml:id="t32" from="#a7" to="#a8" type="content_tags" ana="#content_tags.findings[0]" resp="#tagger">The central question of the paper is a boundary question: what becomes structured data and what stays prose.</span>
      <span xml:id="t33" from="#a9" to="#a10" type="content_tags" ana="#content_tags.findings[1]" resp="#tagger">Standards buy accuracy and unambiguity, but research also needs room for observations that are not yet settled.</span>
      <span xml:id="t34" from="#a13" to="#a14" type="content_tags" ana="#content_tags.findings[2]" resp="#tagger">Modelling a collection early forces a trade-off between standardisation and semantic accuracy.</span>
      <span xml:id="t35" from="#a18" to="#a19" type="content_tags" ana="#content_tags.findings[3]" resp="#tagger">Even major museums publishing LOD share only shallow models of their objects.</span>
      <span xml:id="t36" from="#a20" to="#a21" type="content_tags" ana="#content_tags.findings[4]" resp="#tagger" cert="1.0">The British Museum structured its whole collection in CIDOC CRM but could not keep the database consistent and accessible.</span>
      <span xml:id="t37" from="#a24" to="#a25" type="content_tags" ana="#content_tags.findings[5]" resp="#tagger" cert="1.0">Manual tagging is precise but does not scale, and automatic tagging fails on inconsistent data - so neither route reaches existing collections.</span>
      <span xml:id="t38" from="#a44" to="#a45" type="content_tags" ana="#content_tags.findings[6]" resp="#tagger" cert="1.0">More elaborated, reflexive or contextualized information may need other forms of representation, such as visual interfaces.</span>
      <span xml:id="t39" from="#a40" to="#a41" type="content_tags" ana="#content_tags.findings[7]" resp="#tagger" cert="1.0">Free text is treated as the starting point for semantic contextualisation rather than as a residue to be tidied away.</span>
      <span xml:id="t40" from="#a3" to="#a4" type="content_tags" ana="#content_tags.definitions[0]" resp="#tagger">reference models<term>reference models</term></span>
      <span xml:id="t41" from="#a14" to="#a15" type="content_tags" ana="#content_tags.definitions[2]" resp="#tagger" cert="1.0">CIDOC CRM<term>CIDOC CRM</term></span>
      <span xml:id="t42" from="#a22" to="#a23" type="content_tags" ana="#content_tags.definitions[3]" resp="#tagger" cert="1.0">LOD<term>LOD</term></span>
      <span xml:id="t43" from="#a32" to="#a33" type="content_tags" ana="#content_tags.definitions[4]" resp="#tagger" cert="1.0">unrepresentable<term>unrepresentable</term></span>
    </spanGrp>
  </standOff>
  <text>
    <body>
        <p><anchor xml:id="a0"/> Introduction</p>
        <p>The scientific discourse in object-focused and historical disciplines follows  certain methods and builds a narration with objects, events, evidence and  conclusions.</p>
        <p><anchor xml:id="a1"/>In Digital Humanities (DH) research this process and its specific structure has  to be represented on a data level.<anchor xml:id="a2"/> Linked Open Data, Semantic Web ontologies  and, in particular, <anchor xml:id="a3"/>reference models like CIDOC CRM (2022) offer a  precise structural vocabulary to describe cultural heritage objects and their  relations<anchor xml:id="a4"/>. These frameworks can support GLAM institutions to  make the data on their objects findable, accessible and interoperable.</p>
        <p>However, in research projects the course of developing  arguments and describing findings is crucial. <anchor xml:id="a5"/>We use Art History research,  in particular, the project “Restaging Fashion - Digital contextualization of  vestimentary sources” (Refa), as one example to show how emerging discourses  within the research process can be mapped in a knowledge organization system  and which aspects may not be formally represented.<anchor xml:id="a6"/> <anchor xml:id="a7"/>A recurring question is: What should be modeled as linked open data (LOD)  and what should be entered as free-form text?<anchor xml:id="a8"/> <anchor xml:id="a9"/>Despite the proven utility of data standards,  vocabularies, and authority files providing for accuracy, context, and  unambiguity, there is also a need for an open space to formulate and present  tentative observations.<anchor xml:id="a10"/> <anchor xml:id="a11"/>With this contribution we present how we bridge LOD  and full text descriptions through information visualization.<anchor xml:id="a12"/></p>
        <p>Semantic data modeling in Museums</p>
        <p><anchor xml:id="a13"/>Semantic data modeling of a collection during an early  stage of the research prompts a trade-off to be made between data  standardization and semantic accuracy.<anchor xml:id="a14"/>Sophisticated ontologies like CIDOC CRM encourage the  detailed description of an object through an event-driven structure, which  makes it a very powerful tool for the cultural heritage sector by providing  for the possibility of adding meaning to the original data.<anchor xml:id="a15"/></p>
        <p><anchor xml:id="a16"/>Since 2006, when the term Linked Data was coined (see Berners-Lee 2006), according to  Daquinoet al.&quot;only a few pioneers have abandoned legacy cataloguing  and archiving systems to fully embrace the Semantic Web paradigm and manage  their catalogues through LOD-native management systems&quot; (2022).<anchor xml:id="a17"/></p>
        <p>When considering the LOD datasets published by The  British Museum and the Rijksmuseum, who also create tools such as  ResearchSpace (Oldman / Tanase 2018) and dedicated platforms to engage with  their collections, <anchor xml:id="a18"/>it appears that these museums only share relatively  shallow data models for their artworks on the web<anchor xml:id="a19"/>. The Rijksmuseum provides  basic metadata on objects structured in DC , EDM and LIDO schemas. Only one example is modeled deeply: Linked Art van Gogh object metadata  download . But the creators clearly state that: “both the  implementation of the model as well as the use of identifiers will be  subject to change” (RijksData 2022). <anchor xml:id="a20"/>The British Museum, on the other hand,  structured its entire collection using CIDOC CRM, but was unable to preserve  its database in a consistent and accessible manner (Lincoln, 2015).<anchor xml:id="a21"/> Data  that should be linked together is no longer accessible, making the research  of scholars no longer available ( see Programminghistorian 2017).</p>
        <p><anchor xml:id="a22"/>The potential of these applications is obvious: LOD  allows data to be reused and redistributed, revealing relationships with  other data on the Web (Berners-Lee 2006).<anchor xml:id="a23"/> The resources involved, however,  are somewhat excessive both from a technological perspective (see De Decker 2015)and regarding the cataloging of information. <anchor xml:id="a24"/>Manual  tagging can be performed by domain experts in a very precise manner, but it  cannot be performed manually to large volumes of already existing content  due to the lack of resources (Simou et al. 2017) or may not be conducted  automatically due to inconsistencies and/or the lack of standardization in  the datasets.<anchor xml:id="a25"/> <anchor xml:id="a26"/>This leads institutions to publish only a subset of the  available information, exposing minimal metadata (Doerr et al. 2010), which  might prevent researchers from using the data and constrains them to  conventional research methods.<anchor xml:id="a27"/></p>
        <p>Data-driven art historical discourse</p>
        <p>Art historical research on and with collections is  deeply concerned with the history of objects and their discourse such as  provenance history, history of interpretation, dating or attribution based  on comparable works. This can be expressed with the event structure of CIDOC  CRM including descriptive information on the objects like dimensions,  inscriptions, and alternative titles also linked to relevant vocabularies  like ICONCLASS and AAT . But a crucial part of humanities research consists  of annotating that basic formal information, by elaborating and  contextualizing the history of the artworks and their interpretation, often  concluding in the form of a paper or monograph. Undertaking this part  of research in the form of LOD is very intricate and laborious. <anchor xml:id="a28"/>Complex  ontologies will never be completely exhaustive since no cultural artifact or  experience could be fully and finally contextualized and vocabularies are  not equally accurate and detailed for every subtopic.<anchor xml:id="a29"/> <anchor xml:id="a30"/>In addition, contexts  and meanings shift over time, even during the timeframe of a research  project.<anchor xml:id="a31"/> <anchor xml:id="a32"/>According to Galloway &quot;there are some things that are  unrepresentable. And the computer is our guide into that realm&quot; (2011: 91).<anchor xml:id="a33"/>  <anchor xml:id="a34"/>In terms of representing the research process it is not worth making this  part machine -readable as a basis for formal queries.<anchor xml:id="a35"/> <anchor xml:id="a36"/>It is  more important to present it in a way that is accessible and understandable to  other researchers, which does not require this high level of formalization,  because it would end up in overcomplicated queries.<anchor xml:id="a37"/></p>
        <p>Visualizing context</p>
        <p>One way to equally accommodate formal LOD structures as well as full text  descriptions is through custom interfaces. In particular, information  visualization can be used for the contextualization of images, sources, texts  and their relations.</p>
        <p>Fig. 1: Draft of Refa interface</p>
        <p><anchor xml:id="a38"/>As part of the Restaging Fashion project, we devised different experimental  prototypes, linked specific parts of the textual description to artworks, to  classification entries, to archival sources as well as to other cultural  heritage objects<anchor xml:id="a39"/> (see Fig. 1.) with the aim to establish an overview of the  context.</p>
        <p><anchor xml:id="a40"/>Instead of hiding the full text in unstructured note fields, we approach this as  a starting point for the semantic contextualization of the research process.<anchor xml:id="a41"/></p>
        <p>In conclusion, certain aspects of humanities research can be properly expressed  by semantic web structures. <anchor xml:id="a42"/>In particular quantitative information, for  instance, on objects and their relations, which can be queried and expressed  statistically, are worth to be modeled in triple structures.<anchor xml:id="a43"/> <anchor xml:id="a44"/>Other, more  elaborated, reflexive, or contextualized information may require different forms  of representations like visual interfaces.<anchor xml:id="a45"/></p>
        <p>CIDOC Conceptual Reference Model</p>
        <p>Galleries, Libraries, Archives and Museums</p>
        <p>Dublin Core</p>
        <p>Europeana Data Model</p>
        <p>Lightweight Information Describing Objects</p>
        <p>https://iconclass.org/</p>
        <p>https://www.getty.edu/research/tools/vocabularies/aat/<anchor xml:id="a46"/></p>
    </body>
  </text>
</TEI>
