[Vcon] Clarification on Using vCon Format for Threaded Messages
Sergey Lyapustin <s.lyapustin@gmail.com> Fri, 18 October 2024 10:50 UTC
Return-Path: <s.lyapustin@gmail.com>
X-Original-To: vcon@ietfa.amsl.com
Delivered-To: vcon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E74B6C169435 for <vcon@ietfa.amsl.com>; Fri, 18 Oct 2024 03:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C4tTwZA1idVL for <vcon@ietfa.amsl.com>; Fri, 18 Oct 2024 03:50:58 -0700 (PDT)
Received: from mail-il1-x129.google.com (mail-il1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E6C6C157915 for <vcon@ietf.org>; Fri, 18 Oct 2024 03:50:58 -0700 (PDT)
Received: by mail-il1-x129.google.com with SMTP id e9e14a558f8ab-3a3938e73d3so7960945ab.1 for <vcon@ietf.org>; Fri, 18 Oct 2024 03:50:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729248657; x=1729853457; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=cp7Cej0fN17e27JOsUyNwISkwKipfDK2Z916+eeO+OQ=; b=P3qaLD3z7ZB9YiZ4Wd+3YSD04Jpsz/bIYeSlR304gsxvP9vWB/JMe7u6moP5W98Kdj UosTZEsoCRrfPFwynIc+gY6QMHy0nNXxVUfhZ5UnJd+XEKvYrYAzCSuXMs0aYk0w9Oii RJKdeZNE23P1Car5JNKvoDGa8FjlD0xedrRZXpi44xgkVZdivVkLjuXgPJ/1GtbJqQ5j qHGuba1srgPkbT/eIPxLX2Ibg1vj71nPMfuGxDNi/B9L2PlwPIul/MyEUgcn95cs8Wfo v86771LPwccoQ2OfPq5rb97t2WozOp458szPO/4+ii4FWybHiqXMuw3XE8RKCVqPjOya 283w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729248657; x=1729853457; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=cp7Cej0fN17e27JOsUyNwISkwKipfDK2Z916+eeO+OQ=; b=vQvZv5oomOy2qJuM0h8SP0Zl/+Ec/v2BjZckp/3s3Fztxmitg6dKJQCa4dFXUTREPO ++WToS20I1EP0ZmBvw2Z/QQ5UfVle2jrwGtOPLMH2hqMZ2mfIsNuU5CEqQZshQdMhMgm OgxlAlLzk84S/sXGL0CNMpcqPGjhgBTWKK3u30o+2bVlBc94/GY3tA+OSA1M665sCYv3 ggTiePawU2Ju3Vw45bD4DY3Kd+AWpDVzqYl/Job88uDXtAnuRe4HFIQ+pjh1kulHsRX2 CNawBNDttF6kGpgO1eYpY55LsK2v1dZLp7dZ6lBnO4R3IOGFzf7KBxHBxWaxOXhgpjeu opQQ==
X-Gm-Message-State: AOJu0YwNldu6XeoMvQkAWdTUIe6cQtUQLPEZIGzxULWVjLrXKPOig/Nk sWY2Kfb317Im1ErcFporpu+RK+WmlLOHUb6jFdJNvfWTF41yeO/IWwlJDh5QaFMlqjoOe7qJd43 AenUlLlVZe0p7QY0zIEyr6aKRi6uOjww=
X-Google-Smtp-Source: AGHT+IHziKBVEwnsvJBKcCnaHEECAZt0huwSRRE1B00AErHu0Grjao3yS4QQSudaO2CKE5j+quEh3XdbQAPQpsfmJtk=
X-Received: by 2002:a05:6e02:1a06:b0:3a0:b0dc:abfe with SMTP id e9e14a558f8ab-3a3f409f362mr18933215ab.17.1729248656860; Fri, 18 Oct 2024 03:50:56 -0700 (PDT)
MIME-Version: 1.0
From: Sergey Lyapustin <s.lyapustin@gmail.com>
Date: Fri, 18 Oct 2024 12:50:44 +0200
Message-ID: <CAP8kAUBTg==MGNTN2nKd=9HW-jAVsRrx16nZRPdd07-Y0X9+mg@mail.gmail.com>
To: vcon@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ebaf790624be1367"
Message-ID-Hash: QGL2CA4ROOR3V7SYMPMUYN6HS7JR3F6W
X-Message-ID-Hash: QGL2CA4ROOR3V7SYMPMUYN6HS7JR3F6W
X-MailFrom: s.lyapustin@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Vcon] Clarification on Using vCon Format for Threaded Messages
List-Id: container for conversation data <vcon.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/vcon/guamo0DFt3IjD0qn0o8VO1WoudI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/vcon>
List-Help: <mailto:vcon-request@ietf.org?subject=help>
List-Owner: <mailto:vcon-owner@ietf.org>
List-Post: <mailto:vcon@ietf.org>
List-Subscribe: <mailto:vcon-join@ietf.org>
List-Unsubscribe: <mailto:vcon-leave@ietf.org>
Good day, I’m planning to use the vCon format to share messages from team communication platforms (such as Slack and Teams) for analysis, primarily using LLMs and vector file search to gain insights based on the conversations. I would appreciate any feedback on whether I’m using the vCon format correctly or if there is a better approach. For example, I need to export the Slack channel history from the past few days, which includes a mix of individual messages and threaded conversations. To represent this, I created dialogs for each individual message in the channel and connected them to threads using the vCon group attribute: "group": [ { "uuid": "thread-001", "dialogs": [1, 2, 3], "subject": "Project Update Thread", "parent": 0 } ] Is this the right way to implement this according to the vCon specifications, or am I missing something? Let me know if this version aligns with what you had in mind! here is the full vCon example: https://gist.github.com/slyapustin/679391cd69f0ea46a45994bfa3ebb92b -- Lyapustin Sergey
- [Vcon] Clarification on Using vCon Format for Thr… Sergey Lyapustin