glam/schemas/20251121/linkml/modules/classes/OutputData.yaml
kempersc c2cdbed614 Refactor Price, PriceRange, Primary, and PrimaryDigitalPresenceAssertion classes for improved clarity and multilingual support
- Updated descriptions and titles for Price and PriceRange classes to enhance understanding.
- Added multilingual alt_descriptions for Price, PriceRange, Primary, and PrimaryDigitalPresenceAssertion classes.
- Enhanced examples in Price and PriceRange classes to provide clearer context.
- Improved annotations and comments for better documentation and understanding of class purposes.
- Introduced new slots for official names (including and excluding type) to standardize naming conventions.
- Added sorting variant for official names to facilitate alphabetical ordering.
- Ensured all changes align with the latest schema requirements and best practices.
2026-02-15 21:54:42 +01:00

65 lines
2.2 KiB
YAML

id: https://nde.nl/ontology/hc/class/OutputData
name: output_data
title: Output Data
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
sosa: http://www.w3.org/ns/sosa/
dct: http://purl.org/dc/terms/
dcterms: http://purl.org/dc/terms/
prov: http://www.w3.org/ns/prov#
crm: http://www.cidoc-crm.org/cidoc-crm/
skos: http://www.w3.org/2004/02/skos/core#
rdfs: http://www.w3.org/2000/01/rdf-schema#
org: http://www.w3.org/ns/org#
xsd: http://www.w3.org/2001/XMLSchema#
default_prefix: hc
imports:
- linkml:types
- ../slots/has_description
- ../slots/has_format
- ../slots/identified_by
classes:
OutputData:
class_uri: hc:OutputData
description: Specification of the data output produced by a device, service, or process.
comments:
- "Use cases: IoT device outputs (sensor readings), API responses (JSON/XML/RDF), export files (CSV/PDF), and streaming data."
- "Captures format and description; use identified_by when the output is addressable (e.g., URL or file identifier)."
close_mappings:
- sosa:Result
- schema:DataDownload
slots:
- has_format
- has_description
- identified_by
slot_usage:
has_format:
# range: string # uriorcurie
inlined: false # Fixed invalid inline for primitive type
examples:
- value:
has_type: JsonFormat
has_description:
# range: string
examples:
- value: Temperature and humidity readings from conservation sensors
- value: https://analytics.museum.nl/data
- value: https://api.museum.nl/schemas/climate-v1.json
- value: true
- value: false
annotations:
custodian_types: '["*"]'
custodian_types_rationale: Output data specifications apply to all custodian
types with digital systems.
specificity_score: 0.65
specificity_rationale: Fairly specific to IoT and digital platform contexts.
examples:
- value:
has_format:
has_type: JsonFormat
has_media_type: application/json
has_description: Climate sensor readings
identified_by: https://analytics.museum.nl/climate