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/20260202_matang/has_quantity
  - ../slots/20260202_matang/has_measurement_unit
  - ../slots/20260202_matang/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_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_unit:
              unit_label: replies
      has_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.