glam/schemas/20251121/linkml/modules/classes/TextDirection.yaml
kempersc fc405445c6 Refactor and update schema definitions
- Removed obsolete slots: `has_or_had_custodian_observation`, `provider`, and `specificity_annotation`.
- Updated `has_or_had_score` slot to use `SpecificityScore` class and modified its description and examples.
- Added new slots: `end_seconds`, `end_time`, `has_archive_path`, `has_or_had_custodian_name`, `protocol_name`, and `protocol_version`.
- Introduced a script `check_annotation_types.py` to validate the presence and structure of `custodian_types` in YAML files.
- Added a script `update_specificity.py` to automate updates related to `SpecificityAnnotation` to `SpecificityScore`.
2026-02-01 19:55:38 +01:00

79 lines
No EOL
2.7 KiB
YAML

id: https://nde.nl/ontology/hc/class/TextDirection
name: TextDirection
title: Text Direction Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
crm: http://www.cidoc-crm.org/cidoc-crm/
skos: http://www.w3.org/2004/02/skos/core#
default_prefix: hc
imports:
- linkml:types
- ../metadata
- ../slots/has_or_had_code
- ../slots/has_or_had_label
classes:
TextDirection:
class_uri: hc:TextDirection
description: |
The directional orientation of text flow on an information carrier.
**Purpose**:
Captures how text is read/written on manuscripts, inscriptions, and other
information carriers. Essential for proper display and understanding of
historical documents from different writing traditions.
**Common Directions**:
| Direction | Scripts | Example |
|-----------|---------|---------|
| LEFT_TO_RIGHT | Latin, Cyrillic, Greek | Modern European books |
| RIGHT_TO_LEFT | Arabic, Hebrew, Syriac | Quran manuscripts, Torah scrolls |
| TOP_TO_BOTTOM | Traditional CJK | Classical Chinese scrolls |
| BOUSTROPHEDON | Ancient Greek, Etruscan | "Ox-turning" alternating lines |
**Relationship to WritingSystem**:
TextDirection is distinct from WritingSystem (ISO 15924 script codes).
A single script may have multiple historical or regional direction conventions.
**Usage**:
Used with `has_or_had_direction` slot in InformationCarrier and similar classes.
**Migrated From**: text_direction string slot (2026-01-16) per Rule 53/56
slots:
- has_or_had_label
- has_or_had_code
slot_usage:
has_or_had_label:
examples:
- value: "Left to Right"
- value: "Right to Left"
- value: "Top to Bottom"
has_or_had_code:
examples:
- value: "LTR"
- value: "RTL"
- value: "TTB"
- value: "BOUSTROPHEDON"
annotations:
custodian_types: '["L", "A", "M", "R", "H"]'
custodian_types_rationale: Relevant to libraries, archives, museums, research centers, and holy sites holding manuscripts
specificity_score: 0.45
specificity_rationale: Moderately specific class for manuscript/document analysis
examples:
- value:
has_or_had_code: "LTR"
has_or_had_label: "Left to Right"
- value:
has_or_had_code: "RTL"
has_or_had_label: "Right to Left"
- value:
has_or_had_code: "TTB"
has_or_had_label: "Top to Bottom"
- value:
has_or_had_code: "BOUSTROPHEDON"
has_or_had_label: "Boustrophedon"