ad5fbe82cf
- Consolidated valid_from and valid_to slots into a single temporal_extent slot in FundingRequirement, GiftShop, OrganizationBranch, OrganizationalChangeEvent, OrganizationalStructure, SocialMediaProfile, Storage, StorageUnit classes. - Updated slot definitions to use TimeSpan for temporal_extent, providing structured validity periods. - Removed deprecated slots: valid_from, valid_to, verified_by, wikidata_entity_id, and worldcat_id, archiving their definitions for reference. - Adjusted related documentation and examples to reflect the new temporal_extent structure.
101 lines
3.7 KiB
YAML
101 lines
3.7 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/temporal_extent # was: valid_from + valid_to - migrated per Rule 53
|
|
- ./TimeSpan
|
|
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
|
|
- temporal_extent # was: valid_from + valid_to - migrated per Rule 53
|
|
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
|
|
temporal_extent: # was: valid_from + valid_to - migrated per Rule 53
|
|
description: |
|
|
Availability validity period using CIDOC-CRM TimeSpan.
|
|
MIGRATED from valid_from + valid_to per slot_fixes.yaml (Rule 53).
|
|
Uses begin_of_the_begin for when available since and end_of_the_end for deprecation.
|
|
range: TimeSpan
|
|
inlined: true
|
|
required: false
|
|
examples:
|
|
- value:
|
|
begin_of_the_begin: "2015-01-01"
|
|
description: API available since 2015 (no end date - still available)
|
|
- value:
|
|
begin_of_the_begin: "2015-06-01"
|
|
end_of_the_end: "2020-12-31"
|
|
description: API available from 2015 to 2020 (deprecated)
|
|
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
|