glam/schemas/20251121/linkml/modules/classes/CommentReply.yaml
kempersc fcd1c21c63 Add aliases and enhance slot definitions across various modules
- Added new aliases for existing slots to improve clarity and usability, including:
  - has_deadline: has_embargo_end_date
  - has_extent: has_extent_text
  - has_fonds: has_fond
  - has_laboratory: conservation_lab
  - has_language: has_iso_code639_1, has_iso_code639_3
  - has_legal_basis: legal_basis
  - has_light_exposure: max_light_lux
  - has_measurement_unit: has_unit
  - has_note: has_custodian_observation
  - has_occupation: occupation
  - has_operating_hours: has_operating_hours
  - has_position: position
  - has_quantity: has_artwork_count, link_count
  - has_roadmap: review_date
  - has_skill: skill
  - has_speaker: speaker_label
  - has_specification: specification_url
  - has_statement: rights_statement_url, rights_statement
  - has_type: custodian_only
  - has_user_category: serves_visitors_only
  - hold_record_set: record_count
  - identified_by: has_index_number
  - in_period: has_period
  - in_place: has_place
  - in_series: has_series
  - measure: has_measurement
  - measured_on: measurement_date
  - organized_by: has_organizer
  - originate_from: has_origin
  - part_of: suborganization_of
  - published_on: has_publication_date
  - receive_investment: has_investment
  - related_to: connection_heritage_type
  - require: preservation_requirement
  - safeguarded_by: current_keeper, record_holder_note
  - state: states_or_stated
  - take_comission: takes_or_took_comission
  - take_place_at: takes_or_took_place_at
  - transmit_through: transmits_or_transmitted_through
  - warrant: warrants_or_warranted

- Introduced a new slot definition for evaluated_through to capture evaluation methodologies and review statuses.
2026-02-14 14:41:49 +01:00

96 lines
3.6 KiB
YAML

id: https://nde.nl/ontology/hc/class/CommentReply
name: comment_reply_class
title: Comment Reply Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
sioc: http://rdfs.org/sioc/ns#
as: https://www.w3.org/ns/activitystreams#
imports:
- linkml:types
- ../metadata
- ../slots/has_quantity
- ../slots/has_measurement_unit
- ../slots/temporal_extent
default_prefix: hc
classes:
CommentReply:
class_uri: sioc:Post
description: "Reply metrics and relationships for comments/posts.\n\n**PURPOSE**:\n\
\nStructured representation of reply counts and relationships for threaded\n\
discussions. Replaces simple integer counts with rich reply data including\n\
quantity, temporal tracking, and relationship information.\n\n**DESIGN RATIONALE**:\n\
\nCreated per slot_fixes.yaml migration from `comment_reply_count` integer\n\
to structured `has_reply` + `CommentReply` with `has_quantity`\n\
+ `Quantity` for metric representation.\n\n**REPLY CONTEXTS**:\n\n| Context\
\ | Description |\n|---------|-------------|\n| YouTube | Comment replies on\
\ video comments |\n| Twitter | Reply threads |\n| Facebook | Comment replies\
\ on posts |\n| Forum | Threaded discussion replies |\n\n**ONTOLOGY ALIGNMENT**:\n\
\n| Ontology | Class/Property | Usage |\n|----------|----------------|-------|\n\
| **SIOC** | `sioc:Post`, `sioc:has_reply` | Online community content |\n| **Activity\
\ Streams** | `as:Note`, `as:inReplyTo` | Social activity |\n| **Schema.org**\
\ | `schema:Comment` | Generic comment modeling |\n\n**EXAMPLE**:\n\n```yaml\n\
has_reply:\n - reply_count: 5\n has_quantity:\n numeric_value:\
\ 5\n has_unit:\n unit_label: \"replies\"\n temporal_extent:\n\
\ begin_of_the_begin: \"2025-01-14T10:00:00Z\"\n```\n"
exact_mappings:
- sioc:Post
close_mappings:
- schema:Comment
- as:Note
related_mappings:
- sioc:has_reply
- as:inReplyTo
slots:
- has_quantity
- has_measurement_unit
- temporal_extent
slot_usage:
has_quantity:
range: integer
inlined: false # Fixed invalid inline for primitive type
required: false
examples:
- value:
numeric_value: 5
has_measurement_unit:
unit_label: replies
has_measurement_unit:
# range: string
inlined: false # Fixed invalid inline for primitive type
required: false
examples:
- value:
unit_label: replies
temporal_extent:
range: TimeSpan
inlined: true
required: false
examples:
- value:
begin_of_the_begin: '2025-01-14T10:00:00Z'
examples:
- value: null
- value:
has_quantity:
numeric_value: 5
has_unit:
unit_label: replies
temporal_extent:
begin_of_the_begin: '2025-01-14T10:00:00Z'
- value: null
comments:
- Created 2026-01-22 from comment_reply_count migration (Rule 53)
- Models reply metrics as structured data
- Supports temporal tracking of reply counts
- Aligned with SIOC vocabulary for online communities
see_also:
- http://rdfs.org/sioc/ns#has_reply
- https://schema.org/Comment
annotations:
custodian_types: '["*"]'
custodian_types_rationale: Universal - any custodian with discussion content
may track replies.
specificity_score: '0.55'
specificity_rationale: Moderately general - applies to threaded discussion contexts.