Migration Guide

Overview

This guide helps you migrate existing vCon implementation code to be spec-compliant. Use the search-and-replace patterns below to quickly fix common issues.


πŸ”§ Search and Replace Patterns

Pattern 1: Fix schema_version β†’ schema

TypeScript/JavaScript Files:

# Search for
schema_version

# Replace with
schema

Files to update:

  • src/types/vcon.ts

  • src/tools/*.ts

  • src/db/queries.ts

  • Any interface definitions

  • Any object literals

Example changes:


Pattern 2: Make vendor required

Find optional vendor:

Update tool schemas:


Pattern 3: Fix body type

TypeScript files:

Database queries:


Pattern 4: Add missing Party fields

TypeScript interfaces:

Database schema:


Pattern 5: Add missing Dialog fields

TypeScript interfaces:

Database schema:


Pattern 6: Remove encoding defaults

Database schema:

Migration SQL:


Pattern 7: Add dialog_indices to Analysis

TypeScript interface:

Database:


πŸ”„ Complete Migration Script

Run this bash script to automatically fix most issues:

Make it executable:


πŸ“Š Database Migration

Complete database migration in order:

Verification queries:


πŸ§ͺ Testing After Migration

1. TypeScript Compilation

2. Compliance Tests

3. Database Verification

4. Manual Code Review


πŸ“ Manual Review Checklist

After running automated fixes:

TypeScript Types (src/types/vcon.ts)

Tool Definitions (src/tools/*.ts)

Database Queries (src/db/queries.ts)

Database Schema


🚨 Rollback Plan

If migration fails:


πŸ“ž Support

If you encounter issues:

  1. Check IMPLEMENTATION_CORRECTIONS.md for detailed explanations

  2. Review CLAUDE.md for correct implementations

  3. Consult IETF spec: background_docs/draft-ietf-vcon-vcon-core-00.txt

  4. Run compliance tests to identify specific failures


Last Updated: April 2026 For use with: draft-ietf-vcon-vcon-core-02 (v0.4.0)

Last updated