glam/schemas/20251121/linkml/modules/classes/Documentation.yaml
kempersc 60e66d60f9 Add new slots and classes for enhanced documentation and availability tracking
- Introduced `is_or_was_created_through` slot to indicate content creation methods, replacing previous boolean flags.
- Added `is_or_was_required` slot for generic temporal boolean requirements, aligning with Schema.org.
- Created `AutoGeneration` class to represent automatic content generation, capturing methods and provenance.
- Established `AvailabilityStatus` class to model resource availability with temporal validity.
- Developed `Documentation` class for structured documentation resources, replacing domain-specific slots.
- Implemented `Taxon` class for biological classification in natural history collections.
- Archived previous slots related to API availability and documentation, ensuring a clean schema.
- Enhanced existing slots with detailed descriptions and examples for clarity and usability.
2026-01-14 13:09:31 +01:00

100 lines
3.5 KiB
YAML

id: https://nde.nl/ontology/hc/class/Documentation
name: documentation_class
title: Documentation Class
imports:
- linkml:types
- ../slots/has_or_had_label
- ../slots/has_or_had_description
- ../slots/has_or_had_identifier
- ../slots/valid_from
- ../slots/valid_to
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
dcterms: http://purl.org/dc/terms/
foaf: http://xmlns.com/foaf/0.1/
doap: http://usefulinc.com/ns/doap#
default_prefix: hc
classes:
Documentation:
class_uri: schema:TechArticle
description: >-
Documentation resource for a service, API, platform, or system.
**DEFINITION**:
Documentation represents technical documentation resources such as
API documentation, user guides, developer references, or system manuals.
This replaces domain-specific slots like `api_documentation` with a
structured class that can capture multiple documentation resources
with different types and purposes.
**ONTOLOGY ALIGNMENT**:
- Schema.org: `schema:TechArticle` - technical documentation
- DOAP: `doap:homepage`, `doap:wiki` - project documentation
- FOAF: `foaf:Document` - generic document
- DCTERMS: `dcterms:references` - documentation references
**DOCUMENTATION TYPES**:
- API Reference: Endpoint specifications, parameters, responses
- User Guide: End-user instructions and tutorials
- Developer Guide: Integration and development instructions
- System Manual: Technical specifications and architecture
**USE CASES**:
1. **API Documentation**: Link to REST API reference docs
2. **Integration Guides**: How to integrate with the platform
3. **User Manuals**: End-user documentation for staff
exact_mappings:
- schema:TechArticle
close_mappings:
- foaf:Document
- doap:homepage
related_mappings:
- dcterms:references
- doap:wiki
slots:
- has_or_had_label
- has_or_had_description
- has_or_had_identifier
- valid_from
- valid_to
slot_usage:
has_or_had_identifier:
range: uri
required: true
identifier: true
examples:
- value: "https://data.rijksmuseum.nl/object-metadata/api/"
description: Rijksmuseum API documentation URL
has_or_had_label:
range: string
examples:
- value: "API Reference Documentation"
description: Label for API docs
- value: "Developer Integration Guide"
description: Label for integration guide
has_or_had_description:
range: string
examples:
- value: "Complete REST API reference with endpoint specifications, authentication, and response formats."
description: Description of API documentation content
comments:
- Generic documentation class replacing domain-specific documentation slots
- Supports multiple documentation types (API, user, developer, system)
- URL stored in has_or_had_identifier as the primary identifier
- Aligns with Schema.org TechArticle for technical documentation
see_also:
- https://schema.org/TechArticle
- http://usefulinc.com/ns/doap#
examples:
- value:
has_or_had_identifier: "https://data.rijksmuseum.nl/object-metadata/api/"
has_or_had_label: "Rijksmuseum Collection API"
has_or_had_description: "REST API documentation for accessing collection metadata and images"
description: Rijksmuseum API documentation