<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">PaleOrdia: Semantically Describing (Cuneiform) Paleography using Paleographic Linked Open Data</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Timo</forename><surname>Homburg</surname></persName>
							<email>timo.homburg@hs-mainz.de</email>
							<affiliation key="aff0">
								<orgName type="institution">Mainz University Of Applied Sciences</orgName>
								<address>
									<addrLine>Lucy-Hillebrand Straße 2</addrLine>
									<settlement>Mainz</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">PaleOrdia: Semantically Describing (Cuneiform) Paleography using Paleographic Linked Open Data</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">5607DD8146B55FCA9115FBFC35F0C94A</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T17:43+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>PaleOrdia</term>
					<term>Paleography</term>
					<term>Cuneiform</term>
					<term>Annotation</term>
					<term>Paleographic Linked Open Data</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>This publication describes PaleOrdia, a web application developed to visualize (cuneiform) paleographic sign variants in Wikidata and the data model developed in Wikidata to represent paleography. Modeling paleographic sign variants of (ancient) scripts in linked open data is a relatively new development. It will enable better descriptions of digital scholarly editions with paleographic annotations supported by established web annotation data model vocabularies. As a use case for showcasing the capabilities of PaleOrdia, the cuneiform annotation tool Cuneur is presented as one way to harness the paleographiclinked open data for digital scholarly editions.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>Describing the paleography of inscriptions on cultural heritage objects is a common task in many digital scholarly editions <ref type="bibr" target="#b0">[1]</ref> projects. In a digital scholarly edition, a set of texts is commonly transcribed, annotated, and finally translated or interpreted so that the respective scholar can address the targeted research question. While the contents of the respective textual materials are likely the main focus of the scholar's work, a closer inspection of the stylistic choices made in writing the text is necessary in many disciplines. Such analysis might hint at the detection of authors of texts by writing style, the identification of particularities of writing in a specific time and space, and finally, may give hints about the circumstances in which a text has been written. To make an accurate assessment of authorship, a detailed knowledge of not only the preferred choice of words but also the shape of the characters the author uses for writing, i.e., paleographic features, is important. An automatic analysis of paleographic data needs, at best, accurately described training data, which may assist in automated analysis of the given work of text at hand. This advocates for knowledge graphs of paleographic features, which may be reused in different research contexts. This publication wants to highlight the need for paleographic-linked open data by discussing the cases of cuneiform digital scholarly editions, which will serve as the primary, but not exclusive, application case made possible by this work. Section 2 will give some background on cuneiform signs and the terminologies used in paleography, Section 3 explains how paleographic linked open data can be represented in Wikidata. Finally, the tool PaleOrdia, a tool to manage paleographic linked open data in Wikidata, is introduced in Section 4, and the usefulness of paleographic linked open data is shown in an application example in Section 5.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Foundations and related work on the cuneiform LOD cloud</head><p>The cuneiform script is one of the earliest writing systems used in Ancient Mesopotamia as the script for many languages such as Sumerian, Akkadian, and Hittite. Throughout its existence, for 3000 years, cuneiform signs have considerably evolved and been simplified. They usually depict a transformation from a pictograph to increasingly simplified cuneiform wedge configurations-the basis of all known cuneiform signs. Figure <ref type="figure" target="#fig_0">1</ref> shows the evolution of cuneiform signs throughout space and time. For example, the cuneiform sign SAG for head starts as a pictograph of a head in the Late Uruk period and is subsequently simplified. Starting from the Early Dynastic period, cuneiform signs are comprised of cuneiform wedges to represent cuneiform signs. Cuneiform wedges as atomic components of every cuneiform sign allow for a more simple and formalized drawing of the grapheme and change in composition and positioning of the cuneiform wedges in the subsequent centuries.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1.">Sign variant terminology</head><p>This section briefly introduces terminology that may be used to describe paleographic sign variants.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Definition 1. Character A unit of information that often corresponds to a grapheme or a symbol.</head><p>The definition of a character can be seen as equivalent to something that can be represented by a Unicode codepoint. In contrast, a Unicode code point stands for a variety of shapes of the same grapheme, e.g., may be depicted by different fonts, which may visualize a Unicode codepoint to the user.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Definition 2. Sign A cuneiform sign is a set of shapes/graphemes of cuneiform wedge configurations across time and space that have been classified under a common identifier.</head><p>A sign identifier for a cuneiform sign may be represented in different ways. The cuneiform research community defines so-called sign names for cuneiform signs, often derived from the most common reading of the sign in the Sumerian language. Many, but not all, sign names are equivalent to a Unicode codepoint. Figure <ref type="figure" target="#fig_0">1</ref> shows the three sign names SAG, NINDA and GU7, which each have a corresponding Unicode codepoint in the Unicode standard. However, there are several sign names that have no Unicode codepoint attested at the time of writing. Most cuneiform signs without a Unicode codepoint are combinations of already existing cuneiform signs.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Definition 3. Sign Variant A sign variant is a class of representations of a cuneiform sign that has been attested in time and space.</head><p>A sign variant is a set of distinct configurations of cuneiform wedges that have been classified by a sign name and have been assigned a time period and/or location. Figure <ref type="figure" target="#fig_1">2</ref> shows a set of cuneiform signs that differ in the number of wedges, their positioning, and the shapes of the cuneiform wedges used to build the signs. The shapes of the individual cuneiform wedges shown in Figure <ref type="figure" target="#fig_1">2</ref> differ slightly due to font variations and due to semantic expressions font creators might want to convey. For example, a filled wedge head of a cuneiform sign might hint at the sign variant being created on a stone surface vs. on a clay surface.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Definition 4. Stylistic Sign Variant A stylistic sign variant is a stylistic change of a sign variant that does not constitute a change of its characteristic elements.</head><p>However, in reality, subtle changes in writing on the cuneiform clay tablet, expressed, for example, in the length of individual strokes, the angle of individual strokes in certain cuneiform sign variants, or the pointiness of wedge heads, might reveal the style of a particular writer or even writing school. The aforementioned changes would typically be part of a stylistic sign variant that hints at a specific author of cuneiform texts.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2.">Capturing sign variants using character encodings</head><p>Various approaches have been researched in the past to capture the essence of cuneiform sign variants. Different encodings such as <ref type="bibr" target="#b1">[2]</ref> and <ref type="bibr" target="#b2">[3]</ref> try to capture the number of cuneiform wedges per wedge type, and in the case of PaleoCodage, the positioning of wedges towards each other in a String encoding to create a unique identifier for each of the cuneiform sign variants in existence. These codes purposefully do not capture the elements that describe a stylistic sign variant but can be used as elements in knowledge graphs <ref type="bibr" target="#b3">[4]</ref> capturing paleographic information. Character encodings such as this form the building blocks for identifying and classifying cuneiform signs in knowledge graphs.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.3.">Related Work</head><p>The first ideas of modeling paleography with linked open data technologies emerged in the digital humanities community in 2020. <ref type="bibr" target="#b4">[5]</ref> proposed modeling paleographic features with linked open data vocabularies and creating a formalized vocabulary. <ref type="bibr" target="#b3">[4]</ref> described approaches to generalize a paleographic vocabulary which can be used in conjunction with the Ontolex-Lemon <ref type="bibr" target="#b5">[6]</ref> model to express the paleographic variants in which different words can be written. In particular, this model also introduces the connection between lexemes and paleographic descriptions and the concept of a paleographic sign variant occurrence for annotation purposes. Further approaches to capture features of inscriptions include the CIDOC CRMtex extension <ref type="bibr" target="#b6">[7]</ref>, which allows the description of characters on inscriptions of surfaces of cultural heritage objects. In general, though, digital humanities and computational linguistics approaches rarely use paleographic information for classifications for the time being.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Modeling paleography in Wikidata</head><p>In the previous sections, foundations for modeling paleographic-linked open data were defined. This section explains how Wikidata can be used to represent paleographic features such as cuneiform signs. Many cuneiform signs have been described in the Unicode standard, which Wikidata adopts as QIDs. Hence, a starting point for a paleographic description are the Unicode signs themselves. However, coverage of the Unicode codepoints for cuneiform signs would not be sufficient. Cuneiform signs may appear as ligatures, represented as more than one Unicode codepoint, or cuneiform signs may not occur sufficiently often to be considered for addition to the Unicode standard. These signs will be added as new items to Wikidata and referenced in   <ref type="figure" target="#fig_2">3</ref> shows the data model for paleographic data adopted in Wikidata. The data model relates cuneiform signs to their paleographic sign variants, which are classified by time periods and -if applicable -encodings for their description. Lexicographical data within Wikidata, such as the Sumerian word "a" (water) (L228723) may link to paleographic sign variants used within their respective forms. In this way, scholars can express not only that a Lexeme has been occurring in a specific time period, at a specific place, and in a specific text source but also in which paleographic shape the Lexeme form has been attested. As shown in fig:cuneiformsignhalcompoenents, many cuneiform signs consist of other cuneiform signs. These can be modeled using Wikidata has parts (wdt:P527) relations. Finally, the semantics of the original pictographs can be captured as their meanings in Wikidata using the depicts (wdt:P180) relation. This leads to the capture of cuneiform sign meanings not only on the level of the grapheme but also on a semantic level.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">PaleOrdia: A tool to visualize paleographic linked open data</head><p>PaleOrdia<ref type="foot" target="#foot_0">1</ref> is a fork of the tool Ordia <ref type="bibr" target="#b7">[8]</ref>, which has been developed as a view on Lexeme data in Wikidata. PaleOrdia differs from the original Ordia tool in two fundamental ways:</p><p>• PaleOrdia is a static web application which runs on a Github Page, as opposed to the original Ordia, which needed to be run on a web server</p><p>• PaleOrdia combines the view of Wikidata Lexemes with Wikidata Paleography data PaleOrdia offers the following functionalities to highlight cuneiform paleographic data:</p><p>• Listing of cuneiform sign variants by time period and reference work • Identification of cuneiform signs which have not been included into Unicode<ref type="foot" target="#foot_1">2</ref> </p><p>• Listing of cuneiform signs by type (compound<ref type="foot" target="#foot_2">3</ref> and allograph signs<ref type="foot" target="#foot_3">4</ref> )</p><p>• Representation of cuneiform sign etymology and compounds</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1.">Character Data / Cuneiform Signs</head><p>PaleoOrdia allows users to view information about a cuneiform sign, including the reference works and reference databases in which it is attested, its readings (phonetic values), its classification as a compound sign, allograph, or cuneiform sign, and whether a single Unicode codepoint represents it. Besides metadata such as the attestations of a cuneiform sign in sign lists and on actual cuneiform tablet texts, each PaleOrdia page for a cuneiform sign also lists the different sign variants <ref type="foot" target="#foot_4">5</ref> the sign has been attested with, as shown in Figure <ref type="figure" target="#fig_4">4</ref> Compound signs may be shown per cuneiform sign and cuneiform sign variant. Figure 5 <ref type="foot" target="#foot_5">6</ref> shows compound signs containing the cuneiform sign HAL in a sign variant common in the Old Babylonian and </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Application Case: Digital Editions of Cuneiform Tablets</head><p>A digital edition of cuneiform tablets encompasses a variety of steps by a scholar but usually requires the following components:</p><p>1. A transliteration of the written contents of the cuneiform tablet's sides into the Latin alphabet 2. The annotation of interesting text passages 3. The annotation of interesting features on image media depicting the cuneiform tablet (e.g., broken parts, cuneiform signs, or seal impressions)</p><p>Figure <ref type="figure">6</ref> shows common elements of a digital edition of cuneiform tablets. Figure <ref type="figure">7</ref> shows an example of an image annotation in the image annotation application Cuneur -Cuneiform Annotator <ref type="foot" target="#foot_6">7</ref> . The annotation, saved as an annotation in the W3C Web Annotation Data Model <ref type="bibr" target="#b8">[9]</ref>, currently includes the annotation of the tablet surface, line, and character index to locate the annotated sign. In addition, it includes a character encoding -here, a PaleoCode -to identify the cuneiform sign variant. With the availability of a paleographic sign registry in Wikidata, annotation tools such as Cuneur can be extended with search functionality for sign variants and with URIs, which allow for the reusage of paleographic sign variants across the boundaries of a single cuneiform digital edition.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Conclusions</head><p>This publication introduced the application of a paleographic-linked open data model in Wikidata. The model was tested using the cuneiform script as an example use case and has been used to describe actual cuneiform sign variants found on images and renderings of cuneiform tablet surfaces. The tool PaleOrdia gives an overview and can manage the entered cuneiform sign variants using only a static homepage on Github. This allows cuneiform scholars to get an overview of available cuneiform signs, allows them to compare these sign variants to their findings on the cuneiform clay tablets, and create a linked open data graph of image annotations that are linked to this sign variant registry, which has therefore emerged within Wikidata. The results of such annotations can not only prove valuable for the cuneiform scholar community but may also provide the basis and training data for a variety of machine-assisted classification methods. Finally, this case study based on the cuneiform script might inspire the modeling of sign variants of other scripts in Wikidata, contributing to an interconnected linked open data cloud for paleography.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Evolution of cuneiform signs over different centuries: Cuneiform signs SAG, NINDA and GU7 along with character description codes, Unicode references and time period annotations</figDesc><graphic coords="2,110.13,263.15,375.02,163.88" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Sign variants of the cuneiform sign HAL (U+1212C) occurring in time and space, ordered from the oldest to the most recent time period</figDesc><graphic coords="3,151.80,342.74,291.69,225.00" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: Paleographic data model in Wikidata: Cuneiform sign instances are linked to paleographic sign variants. Paleographic sign variants may be associated with Forms of Wikidata Lexemes to state that these forms have been attested in these particular paleographic representations</figDesc><graphic coords="5,89.29,84.19,416.69,231.09" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure</head><label></label><figDesc></figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: Cuneiform Sign Variants in PaleOrdia along with images from freely available fonts uploaded to Wikimedia Commons to be used as a reference. Sign variants in this view come with an associated time period and a description code.</figDesc><graphic coords="6,130.96,316.89,333.36,198.03" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>Figure 5 :</head><label>5</label><figDesc>Figure 5: Cuneiform signs containing the cuneiform sign HAL as one of its components. This image displays the sign variants for the Old Babylonian and Akkadian time periods</figDesc><graphic coords="7,89.29,84.19,416.70,194.53" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_6"><head>Figure 6 :Figure 7 :</head><label>67</label><figDesc>Figure 6: Typical elements of a digital edition of cuneiform tablets. Each element may be seen as a part of a digital edition knowledge graph and is connected to other knowledge graphs using web annotations</figDesc><graphic coords="8,130.96,84.19,333.34,187.10" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://situx.github.io/paleordia/script?q=Q401&amp;qLabel=cuneiform</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">https://situx.github.io/paleordia/no_unicode/?q=Q401&amp;qLabel=cuneiform&amp;qb=Q401</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">https://situx.github.io/paleordia/compoundsigns/?q=Q401&amp;qLabel=cuneiform&amp;qb=Q401</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">https://situx.github.io/paleordia/allographs/?q=Q401&amp;qLabel=cuneiform&amp;qb=Q401</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4">https://situx.github.io/paleordia/c/?q=Q87554995&amp;qLabel=%F0%92%80%80</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_5">https://situx.github.io/paleordia/cf/?q=Q120671708&amp;qLabel=Cuneiform%20Sign%20Variant%20HAL% 20(Akkadian)</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_6">https://fcgl.gitlab.io/annotator-showcase/</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.1.">Future Work</head><p>Future work should enhance the paleographic linked open data cloud with metrics that allow the calculation of the similarity of different graphemes in the linked open data cloud either by semantic similarity, by image similarity metrics, or by metrics built from encodings which allow the expression of a characters characteristics, such as a PaleoCode <ref type="bibr" target="#b2">[3]</ref> or a Gottstein code <ref type="bibr" target="#b1">[2]</ref> for cuneiform. Expressing these metrics will allow for the implementation of a better semantic search for paleographic sign variants and may prove valuable for approaches for automatic annotation of cuneiform signs.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">What is a scholarly digital edition?</title>
		<author>
			<persName><forename type="first">P</forename><surname>Sahle</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Digital scholarly editing: Theories and practices</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="page" from="19" to="39" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">The gottstein system implemented on a digital middle and neo-assyrian palaeography</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">V</forename><surname>Panayotov</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2015">2015</date>
			<pubPlace>CDLN, London</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Paleocodage-enhancing machine-readable cuneiform descriptions using a machine-readable paleographic encoding</title>
		<author>
			<persName><forename type="first">T</forename><surname>Homburg</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Digital Scholarship in the Humanities</title>
		<imprint>
			<biblScope unit="volume">36</biblScope>
			<biblScope unit="page" from="127" to="154" />
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title level="m" type="main">Towards the integration of cuneiform in the ontolex-lemon framework</title>
		<author>
			<persName><forename type="first">T</forename><surname>Homburg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Declerck</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">Towards paleographic linked open data (plod): A general vocabulary to describe paleographic features</title>
		<author>
			<persName><forename type="first">T</forename><surname>Homburg</surname></persName>
		</author>
		<editor>DH</editor>
		<imprint>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">The ontolex-lemon model: development and applications</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">P</forename><surname>Mccrae</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Bosque-Gil</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Gracia</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Buitelaar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Cimiano</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of eLex 2017 conference</title>
				<meeting>eLex 2017 conference</meeting>
		<imprint>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="19" to="21" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<title level="m" type="main">Definition of the crmtex</title>
		<author>
			<persName><forename type="first">M</forename><surname>Doerr</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Murano</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Felicetti</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Ordia: A web application for wikidata lexemes</title>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">Å</forename><surname>Nielsen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Semantic Web: ESWC 2019 Satellite Events: ESWC 2019 Satellite Events</title>
				<meeting><address><addrLine>Portorož, Slovenia</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2019">June 2-6, 2019. 2019</date>
			<biblScope unit="volume">16</biblScope>
			<biblScope unit="page" from="141" to="146" />
		</imprint>
	</monogr>
	<note>Revised Selected Papers</note>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Web annotation data model</title>
		<author>
			<persName><forename type="first">R</forename><surname>Sanderson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Ciccarese</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Young</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">W3C recommendation</title>
		<imprint>
			<biblScope unit="volume">23</biblScope>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
