> For the complete documentation index, see [llms.txt](https://www.conserver.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.conserver.io/vcon-library.md). # vCon Library (Python) Where to start with the Python vCon library, version 0.10.0 on core-04. ## vCon Python Library > **Current version:** `vcon` **0.10.0** · `pip install vcon` · [GitHub: vcon-dev/vcon-lib](https://github.com/vcon-dev/vcon-lib) · Targets [`draft-ietf-vcon-vcon-core-04`](https://datatracker.ietf.org/doc/draft-ietf-vcon-vcon-core/), syntax `"0.4.0"` · Python 3.12 or later. ### About the library The `vcon` package builds, reads, validates, signs and serializes vCons in Python. A vCon is a JSON container for one conversation: its parties, dialogs (text, audio, video, images), attachments, and analysis such as transcripts or sentiment. The library covers the core-04 object model and two extensions, [Lawful Basis](/extensions/lawful-basis.md) and [WTF transcription](/extensions/wtf-transcription.md). ### Features * Create vCons and add parties, dialogs, attachments, analysis and tags * Content hashes in the spec form (`sha512-`) * Sign and verify with JWS * Lawful basis attachments and permission checks * WTF transcription helpers, provider adapters (Whisper, Deepgram, AssemblyAI) and SRT or WebVTT export * Validate objects, files and JSON strings * Generate UUID8 identifiers ### Pages in this section * [Quickstart](/vcon-library/quickstart.md): install, build a vCon, release notes * [Library API reference](/vcon-library/library-api-reference.md): classes, methods, constants * [Guide for LLMs](/vcon-library/vcon-library-guide-for-llms.md): a compact reference for models that write code against the library Field rules live in the [field reference](/vcons/field-reference.md). ### IETF vCon Working Group The vCon (Virtual Conversation) format is being developed as an open standard through the Internet Engineering Task Force (IETF). The vCon Working Group is focused on creating a standardized format for representing digital conversations across various platforms and use cases. #### Participating in the Working Group 1. **Join the Mailing List**: Subscribe to the vCon working group mailing list at 2. **Review Documents**: * Working group documents and drafts can be found at: * The current Internet-Draft can be found at: 3. **Attend Meetings**: * The working group meets virtually during IETF meetings * Meeting schedules and connection details are announced on the mailing list * Past meeting materials and recordings are available on the IETF datatracker 4. **Contribute**: * Submit comments and suggestions on the mailing list * Propose changes through GitHub pull requests * Participate in working group discussions * Help with implementations and interoperability testing For more information about the IETF standardization process and how to participate, visit: --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.conserver.io/vcon-library.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.