60e66d60f9
- 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.
96 lines
3.1 KiB
YAML
96 lines
3.1 KiB
YAML
id: https://nde.nl/ontology/hc/class/AvailabilityStatus
|
|
name: availability_status_class
|
|
title: AvailabilityStatus Class
|
|
imports:
|
|
- linkml:types
|
|
- ../slots/has_or_had_label
|
|
- ../slots/has_or_had_description
|
|
- ../slots/valid_from
|
|
- ../slots/valid_to
|
|
prefixes:
|
|
linkml: https://w3id.org/linkml/
|
|
hc: https://nde.nl/ontology/hc/
|
|
schema: http://schema.org/
|
|
dcat: http://www.w3.org/ns/dcat#
|
|
dcterms: http://purl.org/dc/terms/
|
|
default_prefix: hc
|
|
classes:
|
|
AvailabilityStatus:
|
|
class_uri: schema:Availability
|
|
description: >-
|
|
Represents the availability state of a resource, service, or feature.
|
|
|
|
**DEFINITION**:
|
|
|
|
AvailabilityStatus models whether something (API, service, feature, resource)
|
|
is currently available for use. This replaces domain-specific boolean flags
|
|
like `api_available` with a structured class that can capture temporal
|
|
validity and descriptive context.
|
|
|
|
**ONTOLOGY ALIGNMENT**:
|
|
|
|
- Schema.org: `schema:Availability` - availability of a product/service
|
|
- DCAT: `dcat:DataService` availability patterns
|
|
- DCTERMS: `dcterms:available` - date resource became available
|
|
|
|
**USE CASES**:
|
|
|
|
1. **API Availability**: Whether a CMS provides API access
|
|
2. **Service Availability**: Whether a digital platform is operational
|
|
3. **Feature Availability**: Whether specific features are enabled
|
|
|
|
**TEMPORAL VALIDITY**:
|
|
|
|
Availability can change over time:
|
|
- API available from 2015-01-01 to 2020-12-31 (deprecated)
|
|
- Service temporarily unavailable during maintenance
|
|
|
|
exact_mappings:
|
|
- schema:Availability
|
|
close_mappings:
|
|
- dcat:DataService
|
|
related_mappings:
|
|
- dcterms:available
|
|
slots:
|
|
- has_or_had_label
|
|
- has_or_had_description
|
|
- valid_from
|
|
- valid_to
|
|
slot_usage:
|
|
has_or_had_label:
|
|
range: string
|
|
required: false
|
|
examples:
|
|
- value: "API Available"
|
|
description: Indicates API is available
|
|
- value: "Service Unavailable"
|
|
description: Indicates service is down
|
|
has_or_had_description:
|
|
range: string
|
|
examples:
|
|
- value: "REST API available with JSON responses"
|
|
description: Details about API availability
|
|
valid_from:
|
|
range: date
|
|
examples:
|
|
- value: "2015-01-01"
|
|
description: API available since 2015
|
|
valid_to:
|
|
range: date
|
|
examples:
|
|
- value: null
|
|
description: Still available (no end date)
|
|
comments:
|
|
- Generic availability status class replacing domain-specific boolean flags
|
|
- Supports temporal validity for tracking when availability changed
|
|
- Aligns with Schema.org Availability enumeration pattern
|
|
see_also:
|
|
- https://schema.org/Availability
|
|
- https://www.w3.org/TR/vocab-dcat-2/#Class:DataService
|
|
examples:
|
|
- value:
|
|
has_or_had_label: "API Available"
|
|
has_or_had_description: "REST API with JSON responses available for collection metadata access"
|
|
valid_from: "2015-06-01"
|
|
valid_to: null
|
|
description: CMS API availability status
|