You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: API_REFERENCE.md
+12-11Lines changed: 12 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# vCon Library API Reference
2
2
3
-
Complete API documentation for the vCon library - a Python implementation of the vCon 0.3.0 specification for Virtual Conversation objects.
3
+
Complete API documentation for the vCon library - a Python implementation of the latest vCon specification for Virtual Conversation objects.
4
4
5
5
## Table of Contents
6
6
@@ -18,7 +18,7 @@ Complete API documentation for the vCon library - a Python implementation of the
18
18
19
19
## Overview
20
20
21
-
The vCon library provides a complete Python implementation of the vCon 0.3.0 specification for representing virtual conversations. It supports all features including parties, dialogs, attachments, analysis, digital signatures, and extensibility.
21
+
The vCon library provides a complete Python implementation of the latest vCon specification for representing virtual conversations. It supports all features including parties, dialogs, attachments, analysis, digital signatures, and extensibility.
22
22
23
23
## Installation
24
24
@@ -40,7 +40,7 @@ The main class for working with vCon objects.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+70Lines changed: 70 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,75 @@
1
1
# Changelog
2
2
3
+
## [0.8.0] - 2025-01-26
4
+
5
+
### 🎉 Major Release: Version Management Simplification
6
+
7
+
This release aligns with the upcoming vCon draft specification by removing mandatory version management and enforcement, making the version field optional while maintaining full backward compatibility.
8
+
9
+
### ✨ Added
10
+
11
+
#### **Flexible Versioning**
12
+
-**Optional Version Field**: The `vcon` field is now optional in vCon objects
13
+
-**Version Preservation**: Existing vCons with version fields continue to work unchanged
14
+
-**Simplified Creation**: New vCons can be created without version fields
15
+
16
+
### 🔄 Changed
17
+
18
+
#### **Version Management Simplification**
19
+
-**Removed `strict_version` Parameter**: Eliminated from all Vcon methods (`__init__`, `build_from_json`, `build_new`, `load`, `load_from_file`, `load_from_url`)
20
+
-**No Automatic Version Assignment**: vCon objects no longer automatically get a version field
21
+
-**No Version Migration**: Removed automatic migration from older versions
22
+
-**Updated Validation**: The `is_valid()` method no longer requires the version field
Copy file name to clipboardExpand all lines: MIGRATION_GUIDE.md
+52-4Lines changed: 52 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,23 @@
1
-
# Migration Guide: New Required Fields
1
+
# Migration Guide: Version Management Changes
2
2
3
-
This guide helps you migrate your existing vCon code to use the new required fields introduced in the latest version.
3
+
This guide helps you migrate your existing vCon code to work with the updated version management system.
4
4
5
5
## Overview
6
6
7
-
The vCon library now supports additional fields as specified in the IETF vCon specification. All new fields are **optional** and **backward compatible**, so existing code will continue to work without changes.
7
+
The vCon library has been updated to align with the latest vCon specification changes. The most significant change is that the **version field is now optional** and version management has been simplified. All changes are **backward compatible**, so existing code will continue to work without changes.
8
+
9
+
## Key Changes
10
+
11
+
### Version Field is Now Optional
12
+
- The `vcon` field is no longer required in vCon objects
13
+
- No automatic version assignment or migration
14
+
- Existing vCons with version fields continue to work unchanged
15
+
- New vCons can be created without version fields
16
+
17
+
### Removed Version Management
18
+
- Removed `strict_version` parameter from all methods
19
+
- No more automatic version migration
20
+
- No more version enforcement or validation
8
21
9
22
## What's New
10
23
@@ -24,7 +37,42 @@ The vCon library now supports additional fields as specified in the IETF vCon sp
24
37
25
38
## Migration Steps
26
39
27
-
### Step 1: Add Extensions (Optional)
40
+
### Step 1: Update Method Calls (Required if using strict_version)
41
+
42
+
If you were using the `strict_version` parameter, you need to remove it:
Copy file name to clipboardExpand all lines: README.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ A Python library for working with vCon (Virtual Conversation) objects according
4
4
5
5
## Overview
6
6
7
-
The vCon library provides a complete implementation of the vCon format for representing conversations and related metadata. It supports all features defined in the vCon 0.3.0 specification including:
7
+
The vCon library provides a complete implementation of the vCon format for representing conversations and related metadata. It supports all features defined in the latest vCon specification including:
8
8
9
9
-**Conversation Management**: Parties, dialogs, attachments, and analysis
0 commit comments