Repository navigation
No change to the format or to conformance: archives and implementations that conform to 1.2.0 conform to 1.2.1, and producers may keep writing spec.version 1.2.0. This release adds fixtures, examples and tools, and moves files.
Added
examples/implementers.md(non-normative): a conformance guide for app developers adding.mdzsupport — the Section 14 requirements grouped by role (opening, creating, saving changes, rendering) as required / recommended / optional checklists, a test plan (samples,mdz validate, which fixture checks apply to which role, and a prompt for having an AI coding assistant write the fixture tests), common mistakes, how to tell MDZip apart from other formats that use.mdz, and the criteria for being listed on mdzip.org.- Fixtures for test
T-018(ZIP-bomb limits, Section 13.1):limit-forged-size.mdz(an entry that expands past its declared size),limit-high-ratio.mdz(about 1029:1) andlimit-overlapping-entries.mdz(300 entries sharing one stream to declare 4.7 GiB), each under 80 KB and generated bytools/build-zip-fixtures.py, with expected outcomes and reference limits inresource-limit-cases.json. No change to the format. - Section 16.5 (non-normative):
ERR_LIMIT_EXCEEDEDfor an archive or entry that exceeds a consumer's resource limits. examples/samples/: five valid sample archives with their source folders —hello,field-guide(multi-file document, images, every manifest field),team-notes(project mode),hand-zipped(no manifest,README.mdset aside),keep-on-save(unknown files and manifest fields to preserve). Built reproducibly bytools/build-examples.py. No change to the format.
Changed
- Repository layout (no change to the format): the shared fixtures moved from
examples/fixtures/to a top-levelfixtures/, with the folders the archives are built from infixtures/src/. The test catalog fromtests/README.mdis now infixtures/README.md.examples/now holds non-normative templates and guidance, including the design rationale that was inreference/README.md(nowexamples/rationale.md). Inhostile-content-cases.json,round-trip-expectations.jsonandarchive-cases.json, the informationalsource/archivepaths follow the new layout.tools/sync-fixtures.mjsreads either layout, so syncing fromv1.2.0and earlier tags still works.