SourceArchiveOnto (v2.0)

• Ontology IRI: http://www.SourceArchiveOnto/
• Version IRI: http://www.SourceArchiveOnto/2.0
• License: Creative Commons Attribution 4.0 International (CC-BY-4.0)

Description

• English: A lightweight ontology for passage-oriented description of ancient literary sources, their documentary structure, subjects, spatial coverage, chronology, authorship, and modern editions.
• Ελληνικά: Μια ελαφριά οντολογία για την προσανατολισμένη στα χωρία περιγραφή αρχαίων γραμματειακών πηγών, της δομής, των θεμάτων, της χωρικής κάλυψης, της χρονολόγησης, της συγγραφής και των σύγχρονων εκδόσεών τους.

Ontology composition and Dataset Contents

This Zenodo record provides two RDF files: the ontology-definition file (SourceArchiveOnto-v2.0.ttl), containing the formal ontology definitions, and the data-inclusive file (SourceArchiveOnto-v2.0-Lokris-data.ttl), containing the ontology together with the corresponding populated RDF data.

Ontology composition and vocabulary reuse

SourceArchiveOnto (SourceArchiveOnto-v2.0.ttl) comprises a compact set of locally defined semantic elements complemented by the targeted reuse of semantically compatible elements from established external Semantic Web vocabularies. The reuse strategy prioritizes semantic compatibility and modelling precision rather than maximizing the proportion of externally sourced elements.

In total, the ontology comprises 57 classes and properties: 18 Classes, 31 Object properties, and 8 Datatype properties. Of these, 40 (70.2%) are locally defined and 17 (29.8%) are reused from external vocabularies. This composition provides a balance between domain-specific expressiveness and interoperability with established Semantic Web modelling practices.

Western Locris dataset

The data-inclusive file (SourceArchiveOnto-v2.0-Lokris-data.ttl) provides a populated demonstration of SourceArchiveOnto using the ancient literary tradition of Western Locris as its target domain. The dataset is developed toward the broader objective of representing the ancient literary tradition of the region and demonstrates how the ontology can model its authors, works, passages, documentary structures, concepts, and geographical entities. It is intended primarily to showcase the expressive and queryable capabilities of the ontology and to support the evaluation of the model against competency questions.

The following metrics provide quantitative evidence of the scope and content of the populated demonstration dataset. The dataset represents 359 individuals and 12,408 asserted RDF triples, covering authors, works, passages, controlled subject and genre concepts, bibliographic citation components, and geographic entities. The following metrics provide evidence of the scope and content of the populated dataset.

Remark: The absence of outbound authority links reflects the current state of the populated demonstration graph and does not indicate a lack of interoperability with external vocabularies.

Namespace Prefixes

Key Core Classes & Structure

• sao:AncientWork: An ancient literary work described independently of a specific modern edition (Subclass of bibo:Book).
• sao:Author: The historical person responsible for creating an ancient literary work (Subclass of foaf:Person).
• sao:Passage: A citable excerpt or citation from an ancient text (Subclass of bibo:Excerpt).
• sao:Volume: A structural book-level division within a work.
• sao:ModernEdition: A modern scholarly edition, translation, or adaptation realizing the intellectual text (Subclass of bibo:Book).
• Reused External Classes: bibo:Chapter, doco:Paragraph, doco:Sentence, vivoweb:GeographicLocation, dbo:City, dbo:Region, skos:Concept, time:ProperInterval.

Core Properties

• Main Object Properties: sao:hasPassage / sao:isPassageOf (links works to excerpts); structural document paths using sao:hasVolume, sao:hasChapter, sao:hasParagraph, and sao:hasSentence; contextual metrics using sao:hasSpatialCoverage, sao:hasSubject, sao:hasGenre, sao:hasTemporalExtent, and sao:hasModernEdition.
• Main Datatype Properties: Structural indices represented as literals (sao:volumeNumber, sao:chapterNumber, sao:paragraphNumber, sao:sentenceNumber) and chronological metadata (sao:earliestPublicationYear, sao:latestPublicationYear, sao:edtfPublicationDate, sao:hasPublicationCentury).

Software Compatibility & Quick Start

1. Download and install Protégé Desktop.
2. Open Protégé, select File → Open..., and select SourceArchiveOnto-v2.0.ttl.
3. Use the Classes, Object Properties, and Data Properties tabs to explore the ontology.
4. To inspect the populated Western Locris graph, open SourceArchiveOnto-v2.0-Lokris-data.ttl.
5. Use Protégé's annotation/language rendering settings to display rdfs:label values in English (en) or Greek (el), where available.

Sample SPARQL Queries

The following example queries demonstrate retrieval and aggregation of passage-level information from the populated Western Locris dataset. The queries can be executed directly in Protégé Desktop using its SPARQL query facilities, provided that the data-inclusive RDF file (SourceArchiveOnto-v2.0-Lokris-data.ttl) is loaded. Alternatively, they can be executed against the same RDF graph using any SPARQL 1.1-compatible RDF store or query environment.

Query 1. Retrieval of passages associated with the Peloponnesian War.

PREFIX sao: <http://www.SourceArchiveOnto/>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX foaf: <http://xmlns.com/foaf/0.1/>

SELECT DISTINCT ?passage ?work ?workTitle ?author ?authorName
WHERE {
  ?work sao:hasPassage ?passage ;
        dcterms:title ?workTitle ;
        dcterms:creator ?author .
  ?passage a sao:Passage ;
           sao:hasSubject sao:PeloponnisiakosPolemos .
  OPTIONAL {
    ?author foaf:name ?authorName .
  }
}
ORDER BY ?authorName ?workTitle ?passage

Query 2. Number of represented passages by author and work.

PREFIX sao: <http://www.SourceArchiveOnto/>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX foaf: <http://xmlns.com/foaf/0.1/>

SELECT ?author ?authorName ?work ?workTitle (COUNT(DISTINCT ?passage) AS ?passageCount)
WHERE {
  ?work dcterms:creator ?author ;
        dcterms:title ?workTitle ;
        sao:hasPassage ?passage .
  ?passage a sao:Passage .
  OPTIONAL {
    ?author foaf:name ?authorName .
  }
}
GROUP BY ?author ?authorName ?work ?workTitle
ORDER BY DESC(?passageCount) ?authorName ?workTitle

Citation