Proposal: Container Profile (corpus envelope) — spec §, example#205
Draft
perlowja wants to merge 1 commit into
Draft
Proposal: Container Profile (corpus envelope) — spec §, example#205perlowja wants to merge 1 commit into
perlowja wants to merge 1 commit into
Conversation
Re-targets onto develop/v1.0.0 per @zircote (issue modeled-information-format#77, PR modeled-information-format#78) for the v1.0.0 cut. Editorial proposed section in SPECIFICATION.md before the Changelog, plus examples/container-profile.corpus.json and a CHANGELOG [Unreleased] entry. Reference converters ship separately (issue modeled-information-format#77).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft spec PR for issue #77 — adds a Container Profile section: a transport envelope around MIF memory units, so a whole corpus (many memories + the source documents they derive from) moves as one artifact.
records[]withkind: memory (a MIF memory unit, validated, levels apply) | document (e.g. an unmodified DoclingDocument).fact/eventfold into MIF memories via a proposedmemoryCategoryterm — no parallel schema.provenance(W3C-PROV),edit_chain/supersedes,compression_manifest,federation_cursor.examples/container-profile.corpus.json+ CHANGELOG.Draft — section number is editorial, and this is yours to shape/merge. The reference converters (mem0, letta, cognee, graphiti, mempalace) + docling import + validator are staged at perlowja/mif-converters (still happy to transfer into the org the moment public-repo creation is enabled for members, per the #77 thread). Pairs with #77.
Rebased 3-file diff onto
main:SPECIFICATION.md(+ Container Profile §),examples/container-profile.corpus.json,CHANGELOG.md. Example JSON validated well-formed. Standing by on thememoryCategoryplacement decision to align spec + converters.