Editable Schema Types

[thelmick-unicon]

Goal: Define boundaries (data model type, the type of data being updated, etc.) for when uploads are allowed or not allowed to change schemas.

Context: LIF includes multiple schema types (Base LIF, Org LIF, Partner LIF, Source Schemas), and we need to determine if all of them should be editable via schema upload.

Question: Which schema types should be editable via schema upload, and which should be treated as read-only?

• Should Partner LIF data models be editable by an end user, or should only that Partner be able to edit the data model as their Org LIF and then export it for other adopters to import as a Partner LIF?
• If edits are allowed in Partner LIFs, how should associated changes in Org LIF be handled?
• Are there any types of edits that should be allowed in read-only data models?

[thelmick-unicon]

AI Summary of feedback from 2/13/2026 Wallet Users Community Call:

From Duane Brown

• Strongly suggested maintaining a pure, read-only version of standard schemas (e.g., Ed-Fi v5).
• Recommended allowing organizations to:
  • Create a copy of the standard schema
  • Edit the copy
  • Preserve the original steward-provided schema unchanged
• Emphasized the importance of:
  • Being able to distinguish between the official standard and local edits
  • Comparing differences between the original and modified versions
  • Maintaining a clear “source of truth” reference

From Duncan Cox

• Supported a similar approach from a skills framework perspective:
  • Preserve canonical references
  • Maintain traceability to the original source
  • Allow local adaptation while retaining pointer to source
• Noted that retaining original relationships and provenance has been helpful in their skill framework implementations.

Underlying theme:

• Maintain canonical, read-only standards.
• Allow editable copies.
• Preserve provenance and traceability.
• Make differences observable.