Short answer
The static Manifest contains exactly 37 ordered 1200-by-1200 Canvases. Each Canvas has one AnnotationPage and one painting Annotation whose target is that Canvas and whose body is a stable image/svg+xml resource. The SVG cards contain deterministic embedded glyph outlines derived from a hash-pinned Noto Sans TC source under the SIL Open Font License; they contain no script, foreignObject, event handlers, external font or app promotion. Bilingual language maps expose the symbol, Unicode notation, Hanyu Pinyin, broad IPA, category and example metadata. A separate IIIF Collection references the Manifest, while seeAlso links expose the canonical CSV, Croissant and SKOS machine data and rendering points to a deterministic ZIP. The resource publishes CC BY 4.0 rights, required attribution, exact SHA-256 checksums and app-independent package metadata. It validates with the IIIF Presentation Validator pinned to a public source commit. No service block is present: this static resource does not claim a IIIF Image API, deep zoom, Content Search API, external collection membership, IIIF certification or institutional ingest.
Open collection.json or manifest.json in a Presentation API 3 compatible viewer, confirm that all 37 Canvases load in order, and verify the published SHA-256 values before local reuse. A viewer must support ordinary SVG image bodies; deployments that require tiled deep zoom should add their own separately operated IIIF Image service rather than inferring one from this Manifest.
What to look for before choosing
- Exactly 37 ordered Canvases covering the complete Bopomofo inventory
- One painting Annotation and one safe static SVG Image per Canvas
- Bilingual labels plus Unicode, Pinyin, broad IPA, category and example metadata
- IIIF Collection, Manifest, deterministic ZIP and exact SHA-256 checksums
- No Image API, deep-zoom, certification or external-ingest claim
A practical decision process
- Open the bilingual guide and download collection.json, manifest.json or the deterministic ZIP.
- Run the pinned IIIF Presentation Validator against manifest.json before repository ingest.
- Confirm that the Manifest has 37 ordered Canvases and no service property.
- Verify checksums-sha256.txt before mirroring the SVG images or ZIP.
- Test one SVG body in the target viewer and add a separate Image API only if deep zoom is required.
Quick comparison
| Need | What to check | Why it matters |
|---|---|---|
| Presentation interoperability | A Presentation API 3.0.0 Manifest with 37 ordered Canvas resources | Compatible viewers can present the complete symbol sequence without custom JSON |
| Portable visual rendering | Each painting Annotation targets its Canvas and references a 1200-by-1200 SVG Image | The glyph remains sharp without depending on a proprietary app or remote font |
| Discovery and verification | Collection, seeAlso, rendering, ResourceSync and SHA-256 links remain separate | Repositories can discover, validate and mirror the files without treating IIIF as a harvesting protocol |