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_or_had_quantity
  - ../slots/has_or_had_unit
  - ../slots/temporal_extent
  - ./Quantity
  - ./Unit
  - ./TimeSpan

default_prefix: hc

classes:
  CommentReply:
    class_uri: sioc:Post
    description: |
      Reply metrics and relationships for comments/posts.
      
      **PURPOSE**:
      
      Structured representation of reply counts and relationships for threaded
      discussions. Replaces simple integer counts with rich reply data including
      quantity, temporal tracking, and relationship information.
      
      **DESIGN RATIONALE**:
      
      Created per slot_fixes.yaml migration from `comment_reply_count` integer
      to structured `has_or_had_reply` + `CommentReply` with `has_or_had_quantity`
      + `Quantity` for metric representation.
      
      **REPLY CONTEXTS**:
      
      | Context | Description |
      |---------|-------------|
      | YouTube | Comment replies on video comments |
      | Twitter | Reply threads |
      | Facebook | Comment replies on posts |
      | Forum | Threaded discussion replies |
      
      **ONTOLOGY ALIGNMENT**:
      
      | Ontology | Class/Property | Usage |
      |----------|----------------|-------|
      | **SIOC** | `sioc:Post`, `sioc:has_reply` | Online community content |
      | **Activity Streams** | `as:Note`, `as:inReplyTo` | Social activity |
      | **Schema.org** | `schema:Comment` | Generic comment modeling |
      
      **EXAMPLE**:
      
      ```yaml
      has_or_had_reply:
        - reply_count: 5
          has_or_had_quantity:
            numeric_value: 5
            has_or_had_unit:
              unit_label: "replies"
          temporal_extent:
            begin_of_the_begin: "2025-01-14T10:00:00Z"
      ```
    
    exact_mappings:
      - sioc:Post
    
    close_mappings:
      - schema:Comment
      - as:Note
    
    related_mappings:
      - sioc:has_reply
      - as:inReplyTo
    
    slots:
      - has_or_had_quantity
      - has_or_had_unit
      - temporal_extent
    
    attributes:
      reply_count:
        description: |
          Simple count of replies (shorthand for has_or_had_quantity.numeric_value).
          Use has_or_had_quantity for structured representation with unit.
        range: integer
        required: false
        minimum_value: 0
        examples:
          - value: 5
            description: 5 replies to a comment
          - value: 42
            description: 42 replies in thread
      
      reply_type:
        description: |
          Type of reply context (comment_reply, thread_reply, direct_reply).
        range: string
        required: false
        examples:
          - value: "comment_reply"
            description: Reply to a comment
          - value: "thread_reply"
            description: Reply in a discussion thread
          - value: "direct_reply"
            description: Direct reply to author
    
    slot_usage:
      has_or_had_quantity:
        description: |
          Structured quantity for the reply count.
          Use Quantity class with numeric_value and has_or_had_unit.
        range: Quantity
        inlined: true
        required: false
        examples:
          - value:
              numeric_value: 5
              has_or_had_unit:
                unit_label: "replies"
            description: 5 replies using Quantity class
      
      has_or_had_unit:
        description: |
          Unit for the reply type (replies, responses, etc.).
          Can be specified directly or via has_or_had_quantity.has_or_had_unit.
        range: Unit
        inlined: true
        required: false
        examples:
          - value:
              unit_label: "replies"
            description: Replies unit
      
      temporal_extent:
        description: |
          Time when the reply count was observed/recorded.
        range: TimeSpan
        inlined: true
        required: false
        examples:
          - value:
              begin_of_the_begin: "2025-01-14T10:00:00Z"
            description: Observation timestamp
    
    examples:
      - value:
          reply_count: 5
        description: Simple reply count (minimal)
      
      - value:
          reply_count: 5
          reply_type: "comment_reply"
          has_or_had_quantity:
            numeric_value: 5
            has_or_had_unit:
              unit_label: "replies"
          temporal_extent:
            begin_of_the_begin: "2025-01-14T10:00:00Z"
        description: Full structured reply count with timestamp
      
      - value:
          reply_count: 0
          reply_type: "comment_reply"
        description: Comment with no replies
    
    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.