Skip to content

Latest commit

 

History

History
90 lines (67 loc) · 6.76 KB

repository_contents.md

File metadata and controls

90 lines (67 loc) · 6.76 KB

Art and Rare Materials (ARM) Repository Contents

Introduction

This document describes the organization of the ARM repository.

Structure and Content of the Repository

The core ontology and the three modularized ontologies (award, custodial_history, and measurement) are each housed in a top-level directory, which contains the OWL ontology files, associated original vocabularies, human-readable documentation, and any SHACL validation profiles.

The core ontology has been split into two OWL files, core.rdf and activity.rdf, because the issue of whether to adopt the BIBFRAME Contribution model or the bibliotek-o Activity model is still unresolved. As a temporary accommodation, the Activity model is used, but the relevant terms are stored in a separate RDF file for easy separation.

The /application_profiles/sources/ directory contains ontology and vocabulary fragments referenced in the modeling recommendations and application profiles. Two types of vocabularies are included:

  • Fragments of existing RDF vocabularies, such as Getty AAT.
  • RBMS vocabularies converted from XML to RDF. While in the absence of an RBMS-defined namespace they are namespaced within ARM, ARM does not claim ownership of these vocabularies nor does it publish them.

Some aspects of the directory structure and filenames are accommodations to the publication implementation. Specifically:

  • GitHub does not recognize the .owl file extension, so we have used .rdf instead. Ideally we prefer the use of the .owl extension since these are OWL ontologies.
  • For simplicity, the RDF files are published directly from the repository directory tree rather than from a separate document root. In order to use versioned namespaces (see Versioning), we therefore store every published version of the files in the repository tree, as opposed to the more usual practice of identifying versions solely with tags on the repository.
  • The top-level css and js directories are used in the display of the human-readable LODE documentation pages.

Directory Structure

All paths are relative to the top level of the repository.